Community
Participate
Working Groups
I just realized that the automatic filtering which was done for bug 342637 does not apply for content from target definition files. This means, that when using a target file, the target platform may contain another (typically older) version of the content being built in the reactor. This may lead to surprising results, because the p2 planner (used for dependency resolution, test runtime computation, and product installation) does not necessarily choose the newest version. We should either apply the same approach as in bug 342637, i.e. remove all other versions, or warn/fail if the other versions are used.
(In reply to comment #0) > or warn/fail if the other versions are used. ... as proposed here: bug 347177
This issue is quickly becoming a showstopper for some of our projects. We have a big project that builds 20-30 components and then gathers a couple of products through product files. When I start the big build it fails as it tries to take an old version from the target platform for one of the components that is assembled in the products. When I ran the build only on the subproject of the product files I get the right component packaged in the product. This is very strange behavior.
Given that 0.18.0 will probably be released in the Kepler timeframe, this will have to be postponed to the next release.
Sorry for the late response. This problem has been fixed as a side-effect of this commit [1] and is therefore resolved since 0.14.0 (released on 14.2.2012). I've added a unit test [2] to ensure the intended behaviour. [1] http://git.eclipse.org/c/tycho/org.eclipse.tycho.git/commit/?id=c425a9152ad284aff9391f82e9300af33c02cc16 [2] http://git.eclipse.org/c/tycho/org.eclipse.tycho.git/commit/?id=49e9d11bdcb3137453a5631ce75ce9f14b335474
