vendredi avr. 30, 2010

Staying up-to-speed with GlassFish 3.0.1 developments

With the GlassFish roadmap for the Open Source Edition published and development going full swing for its 3.0.1 release, you may be interested to track development progress as it happens (lots of bugs being fixed). In the case of this blog entry, "as it happens" means following the "promoted" builds which have gone through more testing than the nightly builds and certainly more than the continuous integration builds. Of course you can also build from source.

GlassFish Open Source Edition promoted builds are available from and pushed out every week or so. You can get the latest one (3.0.1-b15 as of this writing) and install the web or the full profile version. Once installed, a typical promoted build has everything wired in so that you can easily update to a more recent build using the command-line of the graphical update tool.

IPS (aka pkg(5)) is the GlassFish packaging system used since version 3 that makes updates trivial. Promoted builds come with several pre-configured repositories ("authorities" in IPS terms) including a "" one where promoted versions are posted. Before you can upgrade you need to make this repository the default one with this magic command:

% bin/pkg set-authority -P

This allows for a mere "% pkg image-update" to upgrade your install to the latest promoted bits. The graphical alternative would be to use the updatetool (from the top-level bin/ directory of your GlassFish install) or to click in the notification window (screenshot above).

Here's a log for the upgrade of build 14 (which is what NetBeans 6.9 beta ships with) to the latest promoted build 15 bits (as you can see it takes significantly less than the 70MB full download) :

$ bin/pkg image-update
DOWNLOAD           PKGS       FILES     XFER (MB)
Completed         34/34     203/203     27.3/27.3

PHASE                 ACTIONS
Removal Phase           28/28
Install Phase           26/26
Update Phase          270/270

Here are a few additional notes :
• At any given moment "% pkg list" with show "U" status in the "UFIX" column for available updates.
• Remember you can also browse any IPS repository, for the 3.0.1 promoted builds (the URLs are easily obtained with a "% pkg authority" command).
• If you installed using the ZIP archive, you'll need to install the IPS tools (done automagically on the first invocation of pkg or updatetool).
• If you don't mind moving from a stable version to these recent promoted (an thus unstable by definition) bits, you can even apply the steps above (set as default and update the image) to a final version of GlassFish v3 to have it be upgraded to a development build of 3.0.1.

There is no promoted build for the moment for the 3.1 branch, but the above information should be equally applicable to that release once they do show up (most likely here)

vendredi août 21, 2009

Updating GlassFish v3 Preview to a more recent promoted build

This blog has moved to
Follow the link for the most up-to-date version of this blog entry.

GlassFish v3 Preview is build #47(d) and came out right before JavaOne (May 2009). On the way to v3 final, the team is releasing promoted builds every week. We're now down to build 60, so you can imagine how much has changed and what you're missing out on if you're still on build 47. of course you can download the promoted build and re-install GlassFish, but this entry is all about using the IPS package management tools that ship with GlassFish v3 (in the top-level glassfish bin/ directory) to upgrade an existing install.

If you don't mind living on the bleeding edge (promoted builds are less stable than the "Preview" release by definition) you can change your default authority (IPS repository) from a one (whose content hasn't changed since May) to a authority which hosts promoted builds :

% pkg set-authority --enable -P -O

This defines a new authority as the preferred (-P) source for GlassFish packages.
Optionally you can also disable the stable authority :

% pkg set-authority --disable

In any case, updating to the latest promoted build is a simple as issuing this command (or using the updatetool UI) :

% pkg image-update

If you were to set back to being the preferred repository, that would not roll you back to build 47d (v3 Preview) but it would stop offering you to update every week to the newly promoted build. Finally, note that you cannot disable a preferred authority and that to list all authorities, including those that are disabled, you'll need to use the "pkg -a publisher" command.


This blog has moved

Alexis Moussine-Pouchkine's Weblog

GlassFish - Stay Connected


« juin 2016

No bookmarks in folder


No bookmarks in folder