|How to Build Geronimo Eclipse Plugin from Source||Apache Geronimo Development Tools Project||How to get daily Geronimo Eclipse Plugin builds|
- Build GEP using Maven. See How to Build Geronimo Eclipse Plugin from Source for details. The projects are now ready to be imported into your Eclipse workspace.
- Launch a clean installation of Eclipse Helios SR1 (See this page for details).
- Follow these steps blow to complete the configuration of Eclipse for GEP development:
Set Java Installed JRE to Java 6
- Select Window->Preferences
- Select Java->Installed JREs.
- Ensure you have a Java 6 JRE selected.
- Select Java->Compiler.
- Ensure you have Compiler compliance level 1.6 selected.
- Doing this avoids about 8 errors like:
The method getServerPluginManager() of type GeronimoServer must override a superclass method
errors, and should be done to match the Java 6 JRE we are using.
- Doing this avoids about 8 errors like:
Set the ClassPath variable
- Select Window->Preferences as ahown in the figure.
- Select Java->Build Path->Classpath Variables. Select New.
- Enter the location of your m2repo. My m2repo is located at C:/m2repo. Select Ok.
- Once done you can see M2_REPO added to your list of ClassPath variables.
Set the target platform
An excerpt from the Eclipse help about Target Platform says "Target Platform refers to the platform against which you are developing and testing your plug-ins. The target platform encompasses the location of the target, the list of plug-ins constituting the target, the target environment and launching arguments."
The following steps need to be performed while configuring the target platform for GEP development.
- Select Window->Preferences.
- On the next screen select Plug-in Development->Target Platform. Browse to <Local_M2_Repo>/eclipse/eclipse. Select Apply.
- Note: menus change in Helios SR1. Use these steps for Helios SR1:
- Click Add... target platform
- Select Directory, click Next
- Put your <M2_REPO>/eclipse/eclipse in location. (You can use Browse...)
- Click Finish
- Give is a name like M2_REPO>/eclipse/eclipse, and click Finish.
- Make sure your new platform is selected.
- Select Ok. This will set up the target platform for our GEP development.
- If you are going to use the free OSGi tooling available from http://www.ibm.com/developerworks/rational/downloads/10/rationaldevtoolsforosgiapplications.html,
then download the plugins from the link on that page (currently http://public.dhe.ibm.com/ibmdl/export/pub/software/rational/OSGiAppTools),
and add them to your target platform by location.
Import the source code in your Eclipse Workspace
Next step is to import the source code for plug-ins to your workspace. This is the code with which you will be playing all the time.
- Right Click under Project Explorer and Select Import->Import...
- On the next window select General->Existing Projects into Workspace. Select Next.
- On the import projects window Browse to <GEP_Source_Home>/trunk. Select Finish.
In case there are some errors try fixing those (consider it as your first step towards working with GEP! ) or else use the Geronimo mailing lists. See How to open a bug for Geronimo Eclipse Plugin for details.
Run and Debug Configurations
Before you can start running and debusing your code, set up your debug and run configurations.
- Select Run->Run Configurations.
- On the Run Configurations window Select Eclipse Application and Select New button on the top left.
- Name the new configuration as GEP_DEVELOPMENT. Also, change the workspace location name from runtime-New_location to runtime-GEP_Development. Select Apply.
- Next select the Arguments tab for your GEP_Development run configuration and set the VM arguments as follows
- Next select the tracing tab and select the top most 4 jars. See figure below. Select Apply and Run.
- This will launch a new Eclipse window which is nothing but Eclipse + <Your_Plugin_Code>. You can modify the code and each time you can launch your Eclipse Configuration to test the modifications in code.
- TO Debug the code change to Debug Perspective in eclipse and Select Run->Debug Configurations. Select Debug.