Home » Eclipse Projects » Plugin Development Environment (PDE) » classpath in exported and imported plugin
classpath in exported and imported plugin [message #603222] |
Fri, 13 November 2009 07:55 |
KJ Messages: 8 Registered: November 2009 |
Junior Member |
|
|
Hi,
I created a plugin which I exported using the export as a plugin wizard. When I now import this plugin into another workspace using the import wizard again, the .classpath file of the created project does not contain an entry for the jar the export-wizards creates (pluginABC_2.0.9.jar). In the new workspace, I want to create a new fragment which extends the imported plugin. When I remove and add the generated jar (pluginABC_2.0.9.jar) by using the manifest editor, the classpath entry is added nicely though and everything works fine. However, I would like the classpath to be generated correctly after every export / import.
I expect this to be an configuration issue, I just don't see which one. What am I doing wrong?
Cheers,
KJ
My MANIFEST.MF:
Manifest-Version: 1.0
Bundle-ManifestVersion: 2
Bundle-Name: PluginABC
Bundle-SymbolicName: PluginABC;singleton:=true
Bundle-Version: 2.0.9
Bundle-Activator: pluginabc.Activator
Require-Bundle: org.eclipse.ui,
org.eclipse.core.runtime,
org.eclipse.ui.views;bundle-version="3.3.0",
org.eclipse.gef;bundle-version="3.4.1",
de.byteholder.geoclipse;bundle-version="0.1.4",
de.byteholder.geoclipse.gpx;bundle-version="0.0.2",
de.byteholder.geoclipse.libraries;bundle-version="0.1.4",
de.byteholder.geoclipse.map;bundle-version="0.0.2",
de.byteholder.geoclipse.tilefactory.osm;bundle-version="0.1.4 ",
de.byteholder.geoclipse.tilefactory.osm.cycle;bundle-version = "0.1.4",
de.byteholder.geoclipse.tilefactory.osm.tile.at.home;bundle- version= "0.1.4",
de.byteholder.gpx;bundle-version="0.1.4"
Bundle-ActivationPolicy: lazy
Bundle-RequiredExecutionEnvironment: JavaSE-1.6
Bundle-ClassPath:
jar/geotransform.jar,
jar/sax2r2.jar,
jar/yguard.jar,
.
Export-Package:
...
...
...
build.properties:
bin.includes = icons/,\
META-INF/,\
.,\
jar/,\
build.properties,\
PluginABC.product,\
plugin.xml,\
.project
bin.excludes = jar/xerces.jar
source.. = src/,\
<more source folders (yeah, kinda ugly)>
|
|
| |
Re: classpath in exported and imported plugin [message #603592 is a reply to message #603222] |
Wed, 25 November 2009 01:35 |
J. Michael Dean, M.D. Messages: 218 Registered: July 2009 |
Senior Member |
|
|
KJ -
I may misunderstand, but bear with me. I have an RCP with multiple plugins,
and I used to export individual plugins that were "constant", put them in my
plugin folder, etc. However, I think this is the wrong approach.
Instead, leave the plugin pluginABC_2.0.9 inside your workspace. Don't
export it to a jar and stick it in your development environment and then
depend on it as an exported plugin. Instead, let your dependent plugins
simply depend on this plugin project. This costs nothing except a little
disk space, unless there is a reason for the pluginABC to be separately
distributed.
For example, I am working on a project that needs Drools (a Java based rules
engine). I used to create a Drools plugin that contained all the stuff it
needs, and used to put that plugin inside my eclipse plugin folder, and in
targets, etc. Now I simply keep the Drools plugin project in my workspace,
and the other plugins depend on it. Now I never have to worry about it.
Works in all respects.
Hope this is helpful. I am relative newbie because of lack of time, so may
be off the mark.
- Mike
On 11/13/09 12:55 AM, in article hdj3d8$e0p$1@build.eclipse.org, "KJ"
<a1183914@uggsrock.com> wrote:
> Hi,
>
> I created a plugin which I exported using the export as a plugin wizard. When
> I now import this plugin into another workspace using the import wizard again,
> the .classpath file of the created project does not contain an entry for the
> jar the export-wizards creates (pluginABC_2.0.9.jar). In the new workspace, I
> want to create a new fragment which extends the imported plugin. When I remove
> and add the generated jar (pluginABC_2.0.9.jar) by using the manifest editor,
> the classpath entry is added nicely though and everything works fine. However,
> I would like the classpath to be generated correctly after every export /
> import.
>
> I expect this to be an configuration issue, I just don't see which one. What
> am I doing wrong?
>
> Cheers,
> KJ
>
> My MANIFEST.MF:
>
> Manifest-Version: 1.0
> Bundle-ManifestVersion: 2
> Bundle-Name: PluginABC
> Bundle-SymbolicName: PluginABC;singleton:=true
> Bundle-Version: 2.0.9
> Bundle-Activator: pluginabc.Activator
> Require-Bundle: org.eclipse.ui,
> org.eclipse.core.runtime,
> org.eclipse.ui.views;bundle-version="3.3.0",
> org.eclipse.gef;bundle-version="3.4.1",
> de.byteholder.geoclipse;bundle-version="0.1.4",
> de.byteholder.geoclipse.gpx;bundle-version="0.0.2",
> de.byteholder.geoclipse.libraries;bundle-version="0.1.4",
> de.byteholder.geoclipse.map;bundle-version="0.0.2",
> de.byteholder.geoclipse.tilefactory.osm;bundle-version="0.1.4 ",
> de.byteholder.geoclipse.tilefactory.osm.cycle;bundle-version = "0.1.4",
> de.byteholder.geoclipse.tilefactory.osm.tile.at.home;bundle- version= "0.1.4",
> de.byteholder.gpx;bundle-version="0.1.4"
> Bundle-ActivationPolicy: lazy
> Bundle-RequiredExecutionEnvironment: JavaSE-1.6
> Bundle-ClassPath:
> jar/geotransform.jar,
> jar/sax2r2.jar,
> jar/yguard.jar,
|
|
|
Goto Forum:
Current Time: Fri Apr 26 19:33:07 GMT 2024
Powered by FUDForum. Page generated in 0.03118 seconds
|