- This topic has 1 reply, 2 voices, and was last updated 20 years, 6 months ago by
.
-
Posts
-
With new milestones of Eclipse 3 coming out every 6 weeks, and MyEclipse updates even more frequently, it would be nice to be able to use the autoatic update features of eclipse to keep on top of upgrades, rather than having to rebuild development environments all the time.
As a lead developer, I maintain a standard development environment for my developers, which is now based on Eclipse 3M3 and My Eclipse 3.6.2. It would be nice if I could go to M4 and the upcoming new version of MyEclipse without having to reinstall everything (plus a bunch of other plugin such as VSS) and then configure all the plugins.
Not sure exactly how this could be achieved though.
I see what you’re going for here and I agree that we should do whatever we can to make installing new releases easier. For all our Eclipse 2.1-based releases, we place them on our update site so you can install them through the standard Install/Update mechanism so this would suite you nicely.
Eclipse 3.0 is currently more difficult, for a number of reasons. First, we also make all our updates available on our update site, but it will really be of limited use right now. It seems that each new release of our 3.x products also support a new version of Eclipse 3.0’s M builds. To get the update, you need the new M-build which means you’ll be doing a complete installation since the M-Builds aren’t upgradable through the standard mechanisms. Adding to the problem is that the update functionality in Eclipse 3.0 is being completely rewritten and is not really usable yet and you see the delimma.
It is specifically for the ability to easily deliver updates, as well as the instability of the 3.0 M-builds, that we still strongly recommend that all production work be done using Eclipse 2.1.1 and MyEclipse 2.6.x.
–Scott
MyEclipse Support
