Community
Participate
Working Groups
Thanks for bringing this up. We have recently cleaned up our repository structure and now use composite sites. Our preferred p2 repository for Helios is now: Mylyn for Eclipse Helios: http://download.eclipse.org/tools/mylyn/update/helios If it's not too late, it would be great if this could be changed in the packages. Either way we will keep the http://download.eclipse.org/tools/mylyn/update/e3.4 site around for backwards compatibility with Galileo. The new structure allows us to manage Mylyn releases based on Eclipse platform streams which is generally what determines the latest compatible Mylyn release and is simpler to understand for users. Steffen
Created attachment 171441 [details] p2.inf Mylyn repo touchpoint instructions I've applied this patch to CVS HEAD. It changes the Mylyn p2 repositories that are activated in the JEE, Java, Javascript packages. Note that I am not sure what happens if someone updates from RC3 to RC4. I assume that the unconfigure/configure work and that the old p2 repositories are unconfigured before the new ones are added, but I haven't tested this.
Thanks! I'll verify when the next package build is available.
(In reply to comment #2) > Thanks! I'll verify when the next package build is available. There is a build running: http://build.eclipse.org/technology/epp/epp_build/36/download/20100608-1800/
I have verified that the expected update site is displayed in the latest Java package and that update site are properly migrated when updating the package from an older build.
(In reply to comment #4) > I have verified that the expected update site is displayed in the latest Java > package and that update site are properly migrated when updating the package > from an older build. I've tested this myself and I was impressed that even the migration did work - okay, it was defined so from the beginning, but I've never tested it before.
Closing as FIXED.
