I'm logging the bug to track the "problem" explained in the scenario below.
If the gf team didn't publish the b74 packages to the 'dev.glassfish.sun.com'
repository intentionally , then will be closed, of course.
Scenario to reproduce:
- start domain
- start update tool
check the authorities:
- ./bin/pkg authority
PUBLISHER TYPE STATUS URI
dev.glassfish.sun.com (preferred) origin online
contrib.glassfish.org origin online
dev.glassfish.org origin online
The same authorities listed in the update tool.
The build 74 is available:
- click on 'available updates' within UC => you will got 'No updates are available'
- the 'pkg' command will show that gf updates are available as lists packages
from all available publishers.
The gf b74 packages are available on 'http://pkg.glassfish.org/v3/dev/' but not
on 'http://pkg.sun.com/glassfish/v3/dev/' which is preferred publisher.
(FYI, only 2 b74 packages published to this repository :sun-javaee-engine
Consequently, no way to perform update from b73 to b74. To do this, you should
change the authority to the 'http://pkg.glassfish.org/v3/dev/'.