StackOverflow2013

Note that there are some explanatory texts on larger screens.

plurals

POHow do you manage your Eclipse installation?
text
Body
copied!<p>How do you manage your Eclipse installation, i.e. the basic installation, plug-ins and workspace settings with regard to consistent updates (including major ones, 3.5 => 3.6) and usage on two or more computers (desktop + notebook).</p> <p>My current setup is to basically managing the installation on several installations in parallel, i.e. manually add new plug-ins I installed on one to the other, and when I haven't used one in a long time to copy the whole directory from one location to the other. For updates I usually run it about once a month to get the latest versions, major updates I do manually by downloading the basic distribution and re-installing all the plug-ins in the matching version for the new major Eclipse version.</p> <p>However, this approach has some drawbacks:</p> <ul> <li>time intensive</li> <li>update inconsistencies (Update sites change location, update doesn't work because of some version inconsistency between plug-ins that requires a lot of manual fixing, etc) (this has gotten better with 3.5 but still bugs me)</li> <li>no "global" update site, I manually have to manage several locations</li> </ul> <p>I tried alternatives like Yoxos for configuration management but there plug-ins were missing and / or not that well tested together as I expected.</p> <p>I took a look at Idea as an IDE, the one thing I really loved was the update management: centralized and 90% of the functionality I'd be using are provided as a core that is tested and updated as one.</p> <p>Thus the question: How do you manage your Eclipse installations and deal with updates? </p> <p>From my experience with other Eclipse users they have at least the same problem with updates, but I haven't heard of a solution yet.</p>

Querying!

Guidance

An individual column

Larger individual text columns get their own page to allow for proper reading.

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload