Line | |
---|
1 | Importing Expeditee into Eclipse
|
---|
2 | ---------------------------------
|
---|
3 | New -> Other -> Java Project from Existing Ant Buildfile
|
---|
4 | Set the build file as Expeditees build.xml
|
---|
5 | Change the project name as required
|
---|
6 | Done
|
---|
7 |
|
---|
8 | Convert to Eclipse Plugin
|
---|
9 | --------------------------
|
---|
10 | Plugins 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 |
|
---|
12 | Right click on your Expeditee project in the package explorer.
|
---|
13 | Configure Menu -> Convert to Plug-in Projects..
|
---|
14 | Open up your MANIFEST.MF file in eclipse (Inside META-INF folder)
|
---|
15 | Goto the 'Runtime' tab.
|
---|
16 | In the 'Classpath' area remove all entries except the expeditee jar file
|
---|
17 | Open up your buildpath for the project.
|
---|
18 | Right Click project -> Build Path -> Configure build path
|
---|
19 | Remove all .jar entries from the libraries tab.
|
---|
20 | Go back to the class path area of the runtime tab in MANIFEST.MF
|
---|
21 | Select 'Add...' and proceed to add all the jars listed in releases\jars and releases\jars\ext
|
---|
22 |
|
---|
23 | You should now be able to run your eclipse plugin/rcp that depends on Expeditee
|
---|
24 |
|
---|
25 | A note on new jar files
|
---|
26 | -----------------------
|
---|
27 | If 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).
|
---|
28 | Failure 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 |
|
---|
30 | To add the new jar file: open MANIFEST.MF
|
---|
31 | Go 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.