| Making another project into a plugin [message #448862] |
Fri, 05 May 2006 17:39  |
Eclipse User |
|
|
|
I have just started RCP development, so I apologize if my question is a bit naive.... In my current Eclipse development environment, I have a project called (lets say) "Common Framework". This is a bunch of classes that provide persistence, error handling, etc. In my new RCP application, I need to reference classes in this Common Framework project.
Reading the Eclipse RCP book, it seems that making my new RCP application dependant on a new plugin (from an external JAR file) that represents this Common Framework would be a good way to solve this. However, as far as I can tell, it only works if I have an existing JAR file already exported. The challenge is that, during development, I am constantly adding new capabilities to the framework project - in this scenario, I would need to export to a JAR every time I made a change to the framework - which is obviously tedious and prone to forgetfulness.
Is there a way I can make my RCP application reference the workspace "project" during the development cycle, yet still deploy using the plugin-dependancy model when I am finished development. I was thinking that maybe some trickery in the MANIFEST might let me be able to do it, but I would see if anyone else has a similar situation. Many thanks.
--
Craig
|
|
|
| Re: Making another project into a plugin [message #448863 is a reply to message #448862] |
Fri, 05 May 2006 17:58  |
| Eclipse User |
|
|
|
Originally posted by: cfieber.gmail.com
I'd recommend converting your "Common Framework" project to a plugin
project (right click, PDE Tools -> Convert projects to plugin
projects...). This will let you dev with it open in your workspace
along with your other plugins, manage its manifest, etc.
As a plugin project, it still appears as a java project to other
non-plugin related projects, so it won't (shouldn't ;) mess up your
abiilty to use it with standard Java projects.
Craig Edwards wrote:
> I have just started RCP development, so I apologize if my question is a
> bit naive.... In my current Eclipse development environment, I have a
> project called (lets say) "Common Framework". This is a bunch of
> classes that provide persistence, error handling, etc. In my new RCP
> application, I need to reference classes in this Common Framework project.
> Reading the Eclipse RCP book, it seems that making my new RCP
> application dependant on a new plugin (from an external JAR file) that
> represents this Common Framework would be a good way to solve this.
> However, as far as I can tell, it only works if I have an existing JAR
> file already exported. The challenge is that, during development, I am
> constantly adding new capabilities to the framework project - in this
> scenario, I would need to export to a JAR every time I made a change to
> the framework - which is obviously tedious and prone to forgetfulness.
>
> Is there a way I can make my RCP application reference the workspace
> "project" during the development cycle, yet still deploy using the
> plugin-dependancy model when I am finished development. I was thinking
> that maybe some trickery in the MANIFEST might let me be able to do it,
> but I would see if anyone else has a similar situation. Many thanks.
>
> --
> Craig
|
|
|
|
|
|
|
Powered by
FUDForum. Page generated in 0.03805 seconds
Home