How to install Eclipse

Engines, Libraries and Tools
#1

  1. Download 32-bit “Eclipse for Java”.

  2. Copy any plugins into the “dropins” folder (eg Practically Macro).

  3. Set the VM and VM settings in eclipse.ini, eg:


-startup
plugins/org.eclipse.equinox.launcher_1.3.0.v20140415-2008.jar
-vm
C:/System/Java/jdk1.8.0_11/jre/bin/server/jvm.dll
--launcher.library
plugins/org.eclipse.equinox.launcher.win32.win32.x86_1.1.200.v20140603-1326
-product
org.eclipse.epp.package.java.product
--launcher.defaultAction
openFile
--launcher.XXMaxPermSize
256M
-showsplash
org.eclipse.platform
--launcher.XXMaxPermSize
256m
--launcher.defaultAction
openFile
--launcher.appendVmargs
-vmargs
-server
-Dosgi.requiredJavaVersion=1.6
-Xms128m
-Xmx512m
-XX:MaxGCPauseMillis=100
-XX:+UseConcMarkSweepGC
-XX:+AggressiveOpts
-XX:InlineSmallCode=2000
-XX:MaxInlineSize=70

Note “–launcher.library” changes each Eclipse update.

  1. Run:

rm -rf readme
rm -rf *.html

rm -rf features/org.eclipse.cvs*
rm -rf features/org.eclipse.egit*
rm -rf features/org.eclipse.epp*
rm -rf features/org.eclipse.jgit*
rm -rf features/org.eclipse.m2e*
rm -rf features/org.eclipse.mylyn*
rm -rf features/org.eclipse.wb*
rm -rf features/org.eclipse.wst*

rm -rf plugins/org.eclipse.aether*
rm -rf plugins/org.eclipse.cvs*
rm -rf plugins/org.eclipse.egit*
rm -rf plugins/org.eclipse.epp*
rm -rf plugins/org.eclipse.gef*
rm -rf plugins/org.eclipse.help.ui*
rm -rf plugins/org.eclipse.jgit*
rm -rf plugins/org.eclipse.m2e*
rm -rf plugins/org.eclipse.mylyn*
rm -rf plugins/org.eclipse.team.cvs*
rm -rf plugins/org.eclipse.wb*
rm -rf plugins/org.eclipse.wst*
rm -rf plugins/org.eclipse.xsd*

Smoking “org.eclipse.help.ui” lets you map the easy to hit F1 key to something useful.

  1. Enjoy your nice, fast Eclipse without a bunch of junk. Don’t muck it up by installing the Android tools. I recommend the ADT Bundle for that, so Google’s nasty, buggy stuff can stay separate from your nice Eclipse.
#2

Well. You should rename this to “how to install a downstripped Eclipse”. Also (if I understand this correctly) removing git and maven support might not be everybodies cup of tea…

#3

Or:

  • visit the Eclipse website downloads section: https://www.eclipse.org/downloads/
  • download your preferred Eclipse version
  • follow installer instructions
  • done, happy coding
#4

I should not rename this.

Git and Maven support are atrocities.

#5

Well, I dont use eclipse and hate it with a passion, so I can’t say if the support is that bad. Seing maven support as superfluous for game dev might be true. But a good SCM support should not qualify as bloat or junk…

#6

Maven can be ok for large projects/teams, but just adds more layers and gets in the way for my modest solo projects. It’s neat that Eclipse can automatically download and use dependencies via Maven, but this isn’t a problem that needing solving for me. I can easily do without having something unnecessary in the build chain that is doing all kinds of things behind the scenes. JARs in a directory is infinitely simpler.

Git doesn’t have explicit rename or move, so there isn’t a need for IDE SCM integration like there was for SVN. The Eclipse Git plugin adds junk to the UI and generally annoys me. SmartGit is a separate, dedicated SCM tool and is much better than the Eclipse plugin or even other dedicated tools.

For similar reasons, I don’t pretend Eclipse is the file system – I have the file system for that, and it does a better job. I don’t even use the Package Explorer view because a Java project really isn’t hierarchical (packages are easier navigated as a flat list).

Maybe you hate Eclipse because it came with a bunch of junk?