By ckamps on Oct 16, 2008
The Update Center 2 development team just promoted Release Candidate
(RC) 4 of the multi-platform pkg(5) toolkit. This build is near the
last of a series of RC builds that are aligning with the release of the
new GlassFish V3 Prelude application server release. The FishCAT
(GlassFish Community Acceptance Test) effort of V3 Prelude is finding
some issues with the toolkit. There's nothing like having real world
users test the software. In addition to bugs filed based on the
FishCAT program, we've had some new bugs filed and a few last minute
RFEs addressed for the Java API for pkg(5). The GlassFish team has
used this Java API to enable users of their web admin tool to manage
updates and add-ons.
As a side note, the FishCAT
effort has been pretty neat. Even though our toolkit is just one part
of the GlassFish V3 Prelude release, we've had the pleasure of working
with a variety of people around the world that have encountered toolkit
issues. We feel pretty good about our record of jumping on their
reported issues and quickly turning around workarounds and fixes. It
all goes to help the community spirit!
Here are some more key fixes in this build:
- Good ole Windows Vista's User Access Control presented us with a surprise. See Tom's post.
Chris Kasso came to the rescue by creating signed versions of our .exe
wrappers and adding the appropriate manifest setting such that when a
user is running with administrative privileges, the right things will
- We swatted a few more .app bundle issues on Mac OS X 10.4. Due to the flakiness of how .app bundles are handled, Joe has had to implement some detestable workarounds. 10.5 has been much more stable and predictable.
has improved some of the exception handling in the Update Tool GUI.
For example, due to some GlassFish V3 Prelude pre-release package
repository issues, users were seeing some new exception traces
displayed in the GUI. Manpreet and Tom worked out an approach to
present these newly observed exceptions in a more approrpriate manner.
Now the users will better understand that a repository server error
occurred rather than thinking that the Update Tool GUI experienced an
Complete list of issues fixed in this buildGet the bits