GF4 installer: Using older Update Center bootstrap / java client (regression)

[glassfishrobot]

When running the B84 GF installer I bootstrapped UC from the command line by running the "pkg" wrapper script. It looks old, because it refers to wikis.sun.com:

http://wikis.sun.com/display/updatecenter/UsageMetricsUC2

Also, the Java client appears to be pretty old too because:

1) It is slower than the B56 client. The GF4.0 bootstrap of pkg took over a minute for me, but with UC B56 it took less than 40s.

2) B56 has much improved progress feedback.

So it looks like we are using an old wrapper script for "pkg" (and I assume "updatetool") and the Java client is old too.

FYI, I checked the GF 3.1.2 GF installer, and it appears to be using the B56 version (it has the correct URL and download is fast) – so this looks like a regression.

Affected Versions

[4.0_dev]

[glassfishrobot]

• Issue Imported From: https://github.com/javaee/glassfish/issues/20277
• Original Issue Raised By:@glassfishrobot
• Original Issue Assigned To: @ssevozen
• Original Issue Closed By:@glassfishrobot

[glassfishrobot]

@glassfishrobot Commented @ssevozen said: It looks like this slipped through the cracks during 3.1.2 changes merge, probably because of whole nucleus/appserver pom split going on...

Yes, trunk contains B54 client and bootstrap and should be upgraded to b56.

[glassfishrobot]

@glassfishrobot Commented @ssevozen said:

• What is the impact on the customer of the bug?

This is a regression compared to 3.1.2 release. Performance and user experience for UC client bootstrap is affected due to old bootstrap/Java client version. Also, branding issues since integrated release is not Oracle branded.

• What is the cost/risk of fixing the bug?

Low risk. Two line fix to update pkg and bootstrap jar versions in top level pom.xml. New versions have been tested in the field in 3.1.2 and 3.1.2.2 releases so low regression risk.

• Is there an impact on documentation or message strings?

No.

• Which tests should QA (re)run to verify the fix did not destabilize GlassFish?

Regular installer and UC integration testing will be sufficient.

• Which is the targeted build of 4.0 for this fix?

b85

• If this an integration of a new version of a component from another project, what are the changes that are being brought in? This might be list of Jira issues from that project or a list of revision messages.

Not exactly new integration, but delayed merge of the 3.1.2 branch integration.

[glassfishrobot]

@glassfishrobot Commented tmueller said: Approved for 4.0.

[glassfishrobot]

@glassfishrobot Commented @ssevozen said: Integrated updated client jars.

[glassfishrobot]

@glassfishrobot Commented This issue was imported from java.net JIRA GLASSFISH-20277

[glassfishrobot]

@glassfishrobot Commented Reported by @barchetta

[glassfishrobot]

@glassfishrobot Commented Marked as fixed on Thursday, April 11th 2013, 11:37:57 am