Hi, Am 19.03.2013 18:04, schrieb Markus Knauer:
one possible reason could be that the RAP Runtime contributions live in their own validationSet - you can see this if you are opening the simrel.b3aggr with the b3 editor. That's required because the RAP features cannot co-exist with the SWT counterparts from the Eclipse Platform.
I do not depend/include the RAP features. But some of our bundles have direct dependencies on RAP 2.x bundles. No issues reported so far using the train aggregation even though they are in a different validation set.
However, a while ago I intentionally changed our sim-rel contribution to not include the RAP dependencies but on depend on them from a bundle level. This solved a lot sim-rel update issues for us. But the cost is that in the sim-rel train repo we have features without including necessary dependencies. That's ok from a p2 installation perspective because they will be fetched automatically. It's just weird when using in a target platform.
-Gunnar -- Gunnar Wagenknecht [email protected] http://wagenknecht.org/ _______________________________________________ rap-dev mailing list [email protected] https://dev.eclipse.org/mailman/listinfo/rap-dev
