Community
Participate
Working Groups
It looks like the Java M6 package was built against an old platform release (3.7M5).
It looks like all packages are affected by this problem. All packages have been build with content from these two p2 repositories: platform.site=file:///home/data/httpd/download.eclipse.org/eclipse/updates/3.7milestones indigo.site=file:///home/data/httpd/download.eclipse.org/releases/staging/ Is there anything that in the packages that defines a hard dependency to the old M5 version? I am currently investigating.
Could it be related to bug 340016? Looks like the advice there was to use the M6 specific repo: http://download.eclipse.org/eclipse/updates/3.7milestones/S-3.7M6-201103101119
(In reply to comment #2) > Could it be related to bug 340016? Yes, it *is* related to that one. Since EPP input repositories are based on the Simultaneous Release Train repositories, the Platform 3.7milestones repository got included and the artifacts with the highest version number were included in all packages. Unfortunately 'highest' in alphabetical order was in that case not the 'latest' version. > http://download.eclipse.org/eclipse/updates/3.7milestones/S-3.7M6-201103101119 I am rebuilding the packages with this repository at the moment. First build results are looking good when I was looking at a diff between the new build and the old M6 build, but I was not able to download a package so far (not the best internet connection here, still waiting for my download). http://build.eclipse.org/technology/epp/epp_build/indigo/download/20110319-2313/ Since this affects all packages and it looks like a severe problem, I would suggest to release a M6a on Sunday or on Monday if the packages can be tested until then.
New EPP build that should fix this issue is available here: http://build.eclipse.org/technology/epp/epp_build/indigo/download/20110319-2313/
Hi Folks, I understand then that the bug is fixed and every EPP is in place? I'm asking for this because we want to produce a new M6a build to our clients for EclipseCon. Even though we wouldn't probably cause any problem to Indigo aggregator, we prefer to do said build as soon as all EPPs are in place. Everybody will prefer not having any extra unnecessary incovenience ;) BTW, I've noticed that modeling EPP at http://www.eclipse.org/downloads/index-developer.php. May I have some information about this ? Best Regards, Adolfo.
Hi Adolfo, since nearly 24 hours the new M6a packages are being copied to the Eclipse download mirrors. This is part one that we have to keep in mind before releasing anything new, but as I said, they now had 24 hours and we should be on the safe side here. The other thing to keep in mind is the sign-off from the package maintainers. The current state is that the new M6a packages with the fixed Eclipse Platform feature are being tested and I have positive votes from 6 out of 10 package maintainers up to now (see the epp-dev mailing list archive http://dev.eclipse.org/mhonarc/lists/epp-dev/msg01389.html). I expect that we can release EPP M6a within the next few hours, but only those packages with a positive vote from the package maintainer. Many of the package maintainers are on their way to EclipseCon or were preparing tutorials and talks; this and the weekend might be the reason why the test results are a bit late. BTW: That was also the reason why you cannot find the Modeling M6 package on the development tab - I haven't received a mail from them so far.
Markus, Thank you very much for the information. In the end, my project lead finally proposed to do an I-build for EclipseCon rather than a new stable one. So, no extra noise from our side ;) Cheers, Adolfo.
Since we released M6a today, I am closing this bug.
