122

What is the difference between Eclipse for Java (EE) Developers and Eclipse Classic?

Both are marked as version 3.6.

Which one should I use?

Adeel Ansari
  • 39,541
  • 12
  • 93
  • 133
Tony the Pony
  • 40,327
  • 71
  • 187
  • 281

1 Answers1

38

If you want to build Java EE applications, it's best to use Eclipse IDE for Java EE. It has editors from HTML to JSP/JSF, Javascript. It's rich for webapps development, and provide plugins and tools to develop Java EE applications easily (all bundled).

Eclipse Classic is basically the full featured Eclipse without the Java EE part.

Buhake Sindi
  • 87,898
  • 29
  • 167
  • 228
  • 9
    Tip: In *theory* you should be able to take the regular _Eclipse Classic_ and install all the other components bundled with the _Eclipse IDE for Java EE_. After all, Eclipse is basically built as a big bag of plugins. But in *practice*, I and many other folks have found that to be impossible. If you need the Java EE features (such as integration with Tomcat or other Servlet engines), switch editions rather than concocting your own upgrade path. – Basil Bourque Aug 19 '13 at 00:09
  • @BuhakeSindi On the Eclipse comparison page, they have "included (with source)" for the SE version, while only "included" for the EE. What does that mean? Also, everything I'm able to do now with Eclipse SE, will I be able to do with EE? – Honinbo Shusaku May 11 '14 at 14:55
  • 1
    @Abdul, it means that the package contains the source code (meaning that you not only get the jars/package, but the source code that you can compile to package to). Don't forget that (some?) Eclipse IDE is an Open Source project so some packages can come with source code. – Buhake Sindi May 11 '14 at 19:15