|
|
Re: org.eclipse.swt Dependency issues with RAP 2.0 and Tycho Build [message #1009458 is a reply to message #1008228] |
Fri, 15 February 2013 07:17 |
|
The RAP Runtime feature org.eclipse.rap.feature defines negative p2 requirements [1] to conflicting bundles (e.g. org.eclipse.swt, org.eclipse.ui). For reasons described in bug 385512 it wasn't possible to define the negative p2 requirements from bundle to bundle as planned, but from feature to bundles. This prevents the installation of this feature via p2 into anything that already contains these bundles, e.g. the Eclipse IDE, because in that case the installation of RAP Runtime artifacts would cause unpredictible negative side effects.
But all this applies to the feature level only. For everyone who has a valid use-case to install RAP Runtime *bundles* together with their SWT counterparts, this is not forbidden but needs to be done explicitly - I think this is what you did in your first approach.
F org.eclipse.scout.rt.rap
- F org.eclipse.rap.feature
-- B org.eclipse.rap.rwt exports package org.eclipse.swt (1)
- F org.eclipse.scout.rt
-- Fragment *swt.fragment requiring bundle org.eclipse.swt
--- B org.eclipse.swt exports package org.eclipse.swt (2)
What I don't understand is why you have/need this *swt.fragment in your org.eclipse.scout.rt feature. IMO this always introduces a dependency to the SWT bundles and you'll always end up with two bundles providing the package org.eclipse.swt at compile time. I am not sure if this is handled by Tycho correctly... at least it doesn't seem so. I'd recommend to split this build into the two parts - RAP and SWT, and assemble the bundles/features afterwards.
[1] http://git.eclipse.org/c/rap/org.eclipse.rap.git/tree/features/org.eclipse.rap.feature/p2.inf
--
Twitter: @mknauer23 and @EclipseRAP
Blog: http://eclipsesource.com/blogs/
Professional services for RAP and RCP?
http://eclipsesource.com/services/rap/
|
|
|
Re: org.eclipse.swt Dependency issues with RAP 2.0 and Tycho Build [message #1009502 is a reply to message #1009458] |
Fri, 15 February 2013 08:39 |
|
On my way to the office I thought again about your problem: With the *swt.fragment you get a hard dependency to the org.eclipse.swt bundle, but this bundle cannot coexist with the org.eclipse.rap.feature feature. That explains why your approach in your first message cannot work, it's not a package name clash in that case.
Changing this hard bundle dependency to a package import doesn't work either, because then you'll end up with using the org.eclipse.rap.rwt bundle *only*. From a p2 point of view this would work, but that's probably not what you need during compile time.
--
Twitter: @mknauer23 and @EclipseRAP
Blog: http://eclipsesource.com/blogs/
Professional services for RAP and RCP?
http://eclipsesource.com/services/rap/
|
|
|
|
|
Powered by
FUDForum. Page generated in 0.03840 seconds