Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [cross-project-issues-dev] Java 6 will be used for aggregation process

The change to Java 6 fixed the pack200 issue with the last build. I didn't check byte by byte,  but the file counts/sizes were roughly correct, (as pasted below), so I don't think changed anything (else) so I did not promote the final build to staging, so as to not invalidate the build of EPP packages. Gyrex should still test the staging site well, to confirm their jars are really there ... but, I think with current settings, that is the default behavior (if pack.gz fails, to get the regular jar).

I have disabled the aggregation build, for now, so if anyone does find a blocking problem that requires a respin, you'll need to ask for it here on this list.

But, at least we'll know the build scripts do work. BTW, just because the build now uses Java 6, that does not mean anyone has to react to that change. In fact, I'd advise everyone to not react at all ... to stick with Java 5, until you find some reason to change it . The main reason for this change was just so those without an established build can more easily get started, since this java 5 vs java 6 pack200 issue bytes us all ... once.
Comments welcome in 340267 - Use Java 6 to run aggregation process.

Test early, test often.


= = = = = = = =
Using Java 5, causing some errors related to pack.gz files
Type                Count         size (disk used)

Features:              719          18M
Plugin jar files:     3272         776M
Plugin pack.gz files: 2354         242M

After fix to use Java 6, so no pack200 issues
Type                Count         size (disk used)

Features:              719          18M
Plugin jar files:     3272         778M
Plugin pack.gz files: 2411         243M

From:        David M Williams/Raleigh/IBM@IBMUS
To:        cross-project-issues-dev@xxxxxxxxxxx
Date:        03/17/2011 12:40 AM
Subject:        [cross-project-issues-dev] Indigo M6 staging repository is done
Sent by:        cross-project-issues-dev-bounces@xxxxxxxxxxx

Please see/test the staging repo at

The final EPP packages can be created from that staging repo.

But .... there was a small issue with the last run.  The gyrex contribution, apparently, uses Java 6 to do the pack200 step, so our aggregation build could not unpack some of their pack.gz files  ... those that don't contain .class files. It is a long story ... but I've long said after Helios SR2 was released, we should move to Java 6 for our aggregation builds, to avoid this problem-which-is-not-a-problem for Indigo. See

Bug 340267 - Use Java 6 to run aggregation process.

So ... unless I hear otherwise (quickly) I think I'll try to make the Java 6 change now, and see if we get a green run. But
1) I'm sure there's lots that could go wrong, just trying to change the build scripts to use Java 6, not to mention just rebuilding, so it is not certain that this path will succeed, and
2) even if it does succeed, I do not plan to promote the results to "staging" ... they should be exactly the same, except for a few additional pack.gz files. So, I want to make sure our current staging and EPP packages match, without risking some accidental small change.

Lastly, remember, we've said before that the M6 repo will have to be "fresh", just M6 (not also M5) since there are some features changing and some even "moving backwards" in version numbering. (I'll tuck the M5 version away in a special place ... in case someone has an emergency need at EclipseCon ... but, the plan for Friday is to switch /releases/indigo to be M6.

Much thanks. Let us know if questions/problems.


cross-project-issues-dev mailing list

Back to the top