Bootstrapping Eclipse on new machines is such a time consuming process, you wind up asking yourself whether you really need each plugin. But there all handy, and help develop consistent habits.
Eclipse bootstrapping problems include:
- Explaining / documenting what needs to happen
- The actual time pasting in the right URLs and downloading
- Version compatibility and dependencies
- Eclipse likes to restart after each one
- The changeover to the Eclipse Marketplace means that some plugins and instructions you find on the web tend to be inconsistent, depending on when they were written.
- The Licenses... over and over and over... yes, yes, yes... I understand that the person installing needs to be aware of it, and have a chance to review them, but there's got to be a better way.
It'd be nice to have "patch file" (either binary or meta) that spells out what I want to add on top of stock Eclipse installation. I'd really like to find (or create) a 1 or 2 step process that sets up Eclipse, plus a favorite batch of plugins:
- subclipse
- m2eclipse
- jetty support like runjettyrun
- android sdk and plugin (or at least just the plugin)
- aspectj
- Web Objects / WOLiops
- python, other langs
- JVM Monitor, maybe EclEmma
- probably a git plugin pretty soon.
Does command line maven help with any of this? It seems like its repository management would fit at least part of the functionality.