| problem with a plug-in depending on another project [message #290737] |
Wed, 31 August 2005 07:27  |
Eclipse User |
|
|
|
Originally posted by: guillaume.india.gmail.com
Hello
I had a plug-in that I decided to split up into different projects in
eclipse. I have now a plug-in that depends on another project from the
same workspace. The plug-in works until I have actions who use objects
from the depending project.
I tried to export the depending project in the buid path configuration of
the plug-in project but it does not work.
Is there a way to make it work?
thanks for your help
guillaume
|
|
|
| Re: problem with a plug-in depending on another project [message #290743 is a reply to message #290737] |
Wed, 31 August 2005 08:54  |
| Eclipse User |
|
|
|
Originally posted by: thhal.mailblocks.com
guillaume wrote:
> Hello
>
> I had a plug-in that I decided to split up into different projects in
> eclipse. I have now a plug-in that depends on another project from the
> same workspace.
A plugin must have dependencies to other plugins (entered using the
manifest editor), a mere project dependency will not suffice. You can
compile using it but you can't run unless you package the plugin so that
it contain a jar from the non-plugin project.
> The plug-in works until I have actions who use objects
> from the depending project.
> I tried to export the depending project in the buid path configuration
> of the plug-in project but it does not work.
> Is there a way to make it work?
>
The simplest way is to make both projects plugins and change the project
dependency to a plugin dependency.
If you for some reason don't want to convert one of the projects to a
plugin, then you can use a jar packager and then bundle that jar as a
runtime dependency in the plugin.
Regards,
Thomas Hallgren
|
|
|
Powered by
FUDForum. Page generated in 0.02890 seconds
] 
Search
Help
Register
Login
Home
