Eclipse Community Forums - RDF feed
https://www.eclipse.org/forums/
Eclipse Community ForumsDeveloping plugins with library dependency
https://www.eclipse.org/forums/index.php/mv/msg/172713/549622/#msg_549622
I have following scenario:
We are developing a JEE application with an RCP client application. The RCP plugin uses a business delegate library to communicate with the server, to cache some data and to do some other fancy things. This business delegate library is not an Eclipse plugin but the Eclipse plugin depend on this business delegate.
In the development environment the Eclipse Workbench consists of a Plugin project 'rcp.client' for the RCP plugin and a plain Java Project 'business_delegate' for the business delegate. Unfortunately I have not found any way to tell Eclipse that it should bundle the business delegate as a library in the plugin. Currently I am exporting the business delegate as a jar to a lib directory in the 'rcp.client' using the Eclipse Export functionality.
This is sad since whenever I want to start my RCP application from within Eclipse I have to export the business delegate.
Is there any way to tell Eclipse that the 'rcp.client' project depends on the 'business_delegate' project and that it should include it?
Best regards,
Thomas]]>Thomas2010-07-27T11:57:00-00:00Re: Developing plugins with library dependency
https://www.eclipse.org/forums/index.php/mv/msg/172713/549766/#msg_549766
> the 'business_delegate' project and that it should include it?
>
Convert the business_delegate project a plugin project that has the jar file
on its runtime classpath.
In the business_delegate project, export the packages that need to be used
by the rcp.client project.
In the rcp.client project import the required packages.
I assume you are using a feature to build the application, so the
business_delegate plugin needs to be added to the feature so it is included
in the exported application.
Namaste, Bruce]]>Bruce Kelly2010-07-27T20:57:11-00:00Re: Developing plugins with library dependency
https://www.eclipse.org/forums/index.php/mv/msg/172713/550083/#msg_550083
thanks for your help.
Your tip solves my problem with the 'business_deletgate' java project. But in that case I have to change the directory layout of the 'business_delegate' project which would break the Maven build and the m2eclipse plugin integration with Eclipse. I've already tried it that way. Beside that it is perfectly ok that the 'business_delegate' is bundled as a jar file in the 'rcp.client' project since it is just a java project without any dependencies on Eclipse. In fact there must not be any dependencies to Eclipse since the 'business_delegate' is used by other (non-eclipse) clients too. I was just wondering whether there is a way to configure Eclipse to add a depending project to the classpath of the plugin so that when starting the plugin with an 'Eclipse Application' run configuration the depending project is added to the classpath of the plugin.
Best regards,
Thomas]]>Thomas2010-07-29T05:52:41-00:00Re: Developing plugins with library dependency
https://www.eclipse.org/forums/index.php/mv/msg/172713/606361/#msg_606361
thanks for your help.
Your tip solves my problem with the 'business_deletgate' java project. But in that case I have to change the directory layout of the 'business_delegate' project which would break the Maven build and the m2eclipse plugin integration with Eclipse. I've already tried it that way. Beside that it is perfectly ok that the 'business_delegate' is bundled as a jar file in the 'rcp.client' project since it is just a java project without any dependencies on Eclipse. In fact there must not be any dependencies to Eclipse since the 'business_delegate' is used by other (non-eclipse) clients too. I was just wondering whether there is a way to configure Eclipse to add a depending project to the classpath of the plugin so that when starting the plugin with an 'Eclipse Application' run configuration the depending project is added to the classpath of the plugin.
Best regards,
Thomas]]>Thomas2010-07-29T05:52:42-00:00