Wrong version resolved after tycho update from 3.0.5 to 4.0.4

[marc-ernst]

I'm building osgi plugins using bnd. With 3.0.5 they are resolved fine but with 4.0.4 it takes first the found plug-in from the target platform instead of the one I have build before. I'm using goal "bnd-process" and it's the first module listed in the pom. How can I prevent this without defining and specifying a fixed version number in the plug-in and feature?

[laeubi]

Can you share an example? You are maybe missing a dependency in the pom to your bnd-build item?

[marc-ernst]

No, I've added the dependencies in the feature pom.xml with exact version number. It looks like it searches first in the target platform for the dependency.

[laeubi]

The at best you should provide an integration-test to demonstrate the issue, even though its a bit unusual to build something that's part of the target I think the reason is that pom dependencies are only checked after the target platform is queried but for reactor projects we should probably make an exception from that rule.

[marc-ernst]

TYCHO3349bndfirst.zip

I have created a small reproducer. I'm not sure how to check the results automatically. If you look into the p2 repository after building with "mvn -Dtycho-version=4.0.4 install" you will find the plugin org.freemarker_2.3.22.v20160210-1233.jar instead of org.freemarker_2.3.32 .

[laeubi]

BTW. tycho 4.0.4 has still this issue with the mvn proxy in settings. You need to remove the protocol and just specify one proxy to properly work with tycho 4.0.4. There was already an open issue but it was resolved because of this workaround.

Have you tried
try out the current tycho snapshot 4.0.5 build? If the proxy issue still persist please reopen the ticket with further information.

[marc-ernst]

--> even though its a bit unusual to build something that's part of the target
we do this because in mvn repository there might be newer versions of this plug-in which contains security/bug fixes.

[marc-ernst]

Running the same reproducer with tycho 3.0.5 will output the correct version org.freemarker_2.3.32 in the repository plug-in folder.

[marc-ernst]

Should I create an issue from this discussion?

[laeubi]

Should I create an issue from this discussion?

Yes that seems a good next step.