Skip to main content

Eclipse Indigo without mylyn

Eclipse's new release Indigo (3.7) comes pre installed with Mylyn. And unlike previous installations Mylyn is tightly integrated with Eclipse platform package. The "installed features" does not show it as a separate feature to uninstall. It appears as if it cannot be uninstalled at all.

Especially the Java or JEE Developer version has mylyn, git, cvs, and swt windows builder - which may not be all that useful for everyone. A custom lightweight version can be prepared very easily. Just (re)move some folders/jars from features and plugins, that are not needed.
#cd path-to-eclipse installation
#prep
 mkdir disabled disabled/features disabled/plugins

#remove mylyn
 mv plugins/*mylyn* disabled/plugins/
 mv features/*mylyn* disabled/features/

#remove cvs
 mv features/*cvs* disabled/features/
 mv plugins/*cvs* disabled/plugins/

#remove windows builder
 mv plugins/*.wb.* disabled/plugins/
 mv features/*.wb.* disabled/features/

#if svn is used, git may not be necessary; However, there is little harm keeping it
 mv features/*egit.* disabled/features/
 mv plugins/*jgit* disabled/plugins/
 mv plugins/*egit* disabled/plugins/
Disclaimer: The following commands will move the unnecessary features and plugins to a folder in the eclipse installation folder. Although this should not break the installation, if something unwanted happens or eclipse acts up with errors, restore all features and plugins from disabled folder.


Popular posts from this blog

Appcache manifest file issues/caveats

Application cache (appcache) is a powerful feature in HTML5. However, it does come with baggage. Many (see links below) advocated ferociously against it due to tricky issues it comes with. For someone who is just testing waters, these issues may throw them off grid. Knowing them before hand helps reduce some unpredictable effects.

Being a Vegetarian

I am a Proud Vegetarian. I don't eat Meat or Eggs. People say its hard here in US to be one. I beg to differ. The mere fact that I am hail and healthy these 4 years is a definitive proof. Apart from being bullied and trash talked by The Meat-Eaters, There is really nothing that makes this choice of mine any more than a debatable issue at a lunch or dinner. Other things aside, I am writing this blog having watched a PETA Video. Before you click on the play button, I ask you - If you are a vegetarian : Dont watch it. If you are not : Dare to watch it till the end. If you think going veg is just a fashion, think again . Even if you just want to do it for Fashion . Do it. Go Vegetarian. And Feel better asking the waiter for a Vegetarian Entrée in your next lunch.

classpath*: making your Modular Spring Resources

Spring gives multiple options to load XML resources for building contexts. the reference documentation does explain this feature quite well. However, I am taking my shot at explaining the different practical scenarios ( by order of growing modularisation) For Example, A simplest Spring based web Context Loader can be configured with resources like this <context-param> <param-name>contextConfigLocation</param-name> <param-value>applicationContext.xml</param-value> </context-param> <listener> <listener-class>org.springframework.web.context.ContextLoaderListener</listener-class> </listener> You just need to put applicationContext.xml in WEB-INF/ folder of your webapp. However, Typically an application is n-tiered. You can also have multiple files setup and in relative paths. like <param-value> context-files/applicationContext.xml context-files/dao.xml context-files/service.xml </param-value>