automation - Boostrapping new Eclipse machines with all the Plugins -
bootstrapping eclipse on new machines such time consuming process, wind asking whether need each plugin. there handy, , develop consistent habits.
eclipse bootstrapping problems include:
- explaining / documenting needs happen
- the actual time pasting in right urls , downloading
- version compatibility , dependencies
- eclipse likes restart after each one
- the changeover eclipse marketplace means plugins , instructions find on web tend inconsistent, depending on when written.
- the licenses... on , on , over... yes, yes, yes... understand person installing needs aware of it, , have chance review them, there's got better way.
it'd nice have "patch file" (either binary or meta) spells out want add on top of stock eclipse installation. i'd find (or create) 1 or 2 step process sets eclipse, plus favorite batch of plugins:
- subclipse
- m2eclipse
- jetty support runjettyrun
- android sdk , plugin (or @ least plugin)
- aspectj
- web objects / woliops
- python, other langs
- jvm monitor, maybe eclemma
- probably git plugin pretty soon.
does command line maven of this? seems repository management fit @ least part of functionality.
solution 1 search more advanced eclipse distributions. example, sts (spring tool suite) comes with
- aspectj
- egit
- m2e
- (and of course) spring ide
Comments
Post a Comment