|Making an RCP of existing projects. [message #494666]
||Mon, 02 November 2009 05:04
Registered: October 2009
I have two projects, say project A and project B. Now, project A depends on project B.
These two projects are currently as plugins. So now how do I make a RCP of them so that they come as an independent deployment package?
Actually, there is an installer that installs this alongwith eclipse, since they are all plugins. So, i need to make sure the installer installs the tool and required functionalities only (using RCP) and not the associating eclipse IDE.
How do I do this?
[Updated on: Mon, 02 November 2009 05:52]
Report message to a moderator
|Re: Making an RCP of existing projects. [message #494687 is a reply to message #494666]
||Mon, 02 November 2009 08:21
| Daniel KrÃ¼gler
Registered: July 2009
> I have two projects, say project A and project B. Now, project A depends
> on project B. These two projects are currently as plugins. So now how do
> I make a RCP of them so that they come as an independent deployment
The information you provide is rather incomplete. How should the
A-plugin be useful without any B available, if it depends on B?
It seems you dont't have to solve a deployment problem, but a more
fundamental problem to reduce dependencies. E.g. to deploy A and B
independently, A should not depend on B in the first place. Without any
background information available, I suggest the following:
Invent interfaces, that decouple A from B. E.g. create a must-have
plugin C, that publishes the interfaces. Both A and B depend on C
but no longer A on B - problem solved.
In fact working with extension points reflects just the same strategy:
A publisher plugin (e.g. C) provides a customization point via an
extension point and any number of plugins (e.g. A or B) can contribute
to that. The publisher plugin is the one, both A and B depend on,
but not vice versa.
HTH & Greetings from Bremen,
Powered by FUDForum
. Page generated in 0.06569 seconds