source: trunk/README-Eclipse-Plugin.txt@ 991

Last change on this file since 991 was 991, checked in by bln4, 8 years ago
File size: 1.6 KB
Line 
1Importing Expeditee into Eclipse
2---------------------------------
3New -> Other -> Java Project from Existing Ant Buildfile
4Set the build file as Expeditees build.xml
5Change the project name as required
6Done
7
8Convert to Eclipse Plugin
9--------------------------
10Plugins cannot have dependant projects that are not plugins themselves. Therefore if you writing a eclipse plugin or RCP application that involes Expeditee you will need to convert Expeditee to a plugin project.
11
12Right click on your Expeditee project in the package explorer.
13Configure Menu -> Convert to Plug-in Projects..
14Open up your MANIFEST.MF file in eclipse (Inside META-INF folder)
15Goto the 'Runtime' tab.
16In the 'Classpath' area remove all entries except the expeditee jar file
17Open up your buildpath for the project.
18Right Click project -> Build Path -> Configure build path
19Remove all .jar entries from the libraries tab.
20Go back to the class path area of the runtime tab in MANIFEST.MF
21Select 'Add...' and proceed to add all the jars listed in releases\jars and releases\jars\ext
22
23You should now be able to run your eclipse plugin/rcp that depends on Expeditee
24
25A note on new jar files
26-----------------------
27If a new jar file is added to expeditees libraries then you are going to have to tell the MANIFEST.MF file about it (as well as your project classpath).
28Failure to do this will cause a runtime exception when the jar file is asscessed; because the plugin doesn't think you should have access.
29
30To add the new jar file: open MANIFEST.MF
31Go to the 'Runtime' tab and add it as a required jar on the classpath area.
Note: See TracBrowser for help on using the repository browser.