| Alternative dependency sets for a common plug-in hierarchy [message #637589] |
Sun, 07 November 2010 11:52  |
 Alex Mising name
Messages: 149
Registered: March 2010 |
Senior Member |
|
|
Hello,
It's been a while since I've been coding on top of the Eclipse platform. Just today, I started on a pet project of mine and decided to give it ago using Eclipse. In order to also learn something new, I'm trying to create a UI that runs on top of both RAP and RCP. My goal is to have a common codebase (to the greatest extent possible) and then a couple of RAP-specific / RCP-specific bundles (for the stuff that simply must be different among the two).
Usually, I'd just add required plug-ins as dependencies. But now I'm in a situation where a bundle depends in an either/or fashion to something else. For example, one of "org.eclipse.ui" or "org.eclipse.rap.ui" needs to be present; but if neither is available then it's a problem. I added both as "optional" dependencies to my bundle, but this is not "perfect" because it would properly resolve even if neither of the two was in the launch configuration.
I'm currently thinking of importing a list of packages rather than depending on plug-ins, which would solve the problem (even though I'd have to define a rather long list of packages instead of just one of two plugins).
I thought however that I'd best ask if there is some "pattern" or general advice on how to go about structuring bundle dependencies for such situations. It seems to me that this is a generic problem and that Eclipse somehow is well-suited to address it, so there must be some dos and don'ts for this.
Kind regards,
Alex
|
|
|
|
Powered by
FUDForum. Page generated in 0.02893 seconds
] 
Search
Help
Register
Login
Home
