CODEWITHSUNDEEP
javaeclipseeclipse-plugin
ug_
ug_

Reputation: 11440

Eclipse IDE setup

I am fairly new to Eclipse and have recently setup the IDE using the base installation. I am mostly working on java projects that use a Spring, Maven and of course all the files that come with a website. I installed several plugins to handle color coding for JS, CSS, JSP and tag files. My IDE now slows down quite a bit after about 2 hours of using it. It's really frustrating having to restart it or suffer slow load times when opening or switching files. I want to know what a good base installation of Eclipse that would include things like color coding for basic files used on the web like javascript, css, xml etc...

If these requirements can't be achieved with a default installation, what should I start with as my base and what plugins are some great stable ones to get for what I require?

Upvotes: 1

Views: 245

Answers (2)

Daniel B. Chapman
Daniel B. Chapman

Reputation: 4687

Less of an answer, more of a comment.

Eclipse has some performance issues, especially with a lot of plugins running. The web tools project in particular has issues where it appears to re-parse XML files on a ridiculous frequency which causes some serious slowdown.

However, it is still my IDE of choice for Java Web/EE applications. Some quick fixes are:

  • Upgrade to Eclipse 4--there's no reason not to if you're starting out, it is much faster.
  • Turn off "Automatic building"
  • Install it on a RAM drive/SSD so your file-hits move more quickly (the RAM drive, as a bonus, starts clean)
  • Run it with -clean every once in a while and ditch your local file history
  • Keep a minimum set of files open.

My general problems are when editing JSF/XML files due to the validation running constantly. Turning off automatic building minimized this.

As to Netbeans... Netbeans I find to be very sluggish when dealing with EE projects and less intuitive. This might just be personal preference, but in my experience Eclipse makes building and dealing with web projects less of a headache. Additionally the UI feels far more sluggish than Eclipse when dealing with anything substantial. It is faster in some areas and slower in others--basically a wash in productivity in my books (the last time I seriously used it was late 2011 so there might be some improvements I'm unaware of).

Also, make sure you're setting up your servers so that you're not rebuilding from scratch and you're taking advantage of native "hot-code replacement" while debugging or JRebel if you want to spend a bit of cash. It really makes a difference. Additionally "JBoss tools" off the marketplace might be of interest. Some of those plugins are rather helpful.

Lastly I reboot at my coffee breaks--it really isn't that big a deal in my workflow. It might be a bigger deal in yours.

Upvotes: 3

Tejas Patil
Tejas Patil

Reputation: 6169

Few suggestions:

  • disable "automatically build" in "project"'s menu.
  • use the latest Eclipse
  • use the latest JDK for launching eclipse (edit eclispe.ini)
  • configuring the eclipse.ini (see this question for a complete eclipse.ini). Increase the heap values over there.

Upvotes: 2

Related Questions