Mule : Eclipse Tips
This page last changed on Aug 09, 2006 by alan.cassar.
1. Setting Your Eclipse start up parametersYou can pass a number of command-line parameters to Eclipse to alter the start up behaviour. We recommend the following options-
For example under Windows, right click your eclipse shortcut and select properties and set the Target field to something like - C:\java\eclipsehome\eclipse\eclipse.exe -clean -nosplash -showLocation -vm C:\java\jdk1.5.0_03\bin\javaw.exe -vmargs -Xms128m -Xmx512m -XX:MaxPermSize=128m -Duser.language=en Please understand that these values are only examples - in this case for a very beefy developer machine. Eclipse 3.2 uses a lot less memory than 3.1, so you most likely need a lot less VM heap memory than -Xmx512m. 2. Create an external plugins locationHaving your plug-ins installed outside of your eclipse installation directory means that you can share plug-ins between versions of Eclipse. There is a good blog post by Colin Sampa about how to do this. 3. Importing multiple projectsThe Eclipse import wizard doesn't search for existing projects below 1 directory from its parent. This can be a little annoying, but luckily the Eclipse Tools project at SourceForge has a plug-in that allows you to import all project below a parent directory. You can add the Eclipse-Tools plug-ins in the Eclipse Update Manager using this URL - http://eclipse-tools.sourceforge.net/updates/. Once installed -
4. Recommended resources to ignore for team synchornisationWhen you import Mule projects into your workspace, Eclipse will usually mark with a star (on a black background) resources which you might have modified. Some resources will be modified immediately by Eclipse as soon as you import the projects. This lead Eclipse to mark all projects as changed, giving you hard time to identify which resources you have really changed and which were changed by Eclipse. This problem can be solved easily by telling Eclipse to ignore some type of resources in relation to team synchonisation. This can be done as follows: In the menu bar, choose Window --> Preferences and a new Dialog Box will pop out. On the left hand, choose Team --> Ignored Resources and add all the patters you would like to ignore. Some suggested patters to ignore include: |
![]() |
Document generated by Confluence on Oct 03, 2006 09:23 |