Skip to main content

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
[cross-project-issues-dev] Indigo M6 staging repository is done

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.



Back to the top