Geek asks and answers

Tycho resolves the wrong version of my own manifest first artifacts

Consider the following scenario: My application has some dependencies on my own POM first artifacts (built using pure Maven) and some dependencies on my own first appearance artifacts (built using Tycho). For the first POM artifacts, Tycho solves the exact version specified in the POM. For the manifest of the first artifacts, Tycho allows locally-built units that may have a higher version.

In my specific case, I pointed out the dependency in pom.xml to manifest the first artifact in version 1.2.0, but I warned, “The following local modules were used to resolve project dependencies” with version 1.3.0.2012xxx.

I already found the following errors and discussions, but I don’t understand why there is a difference in Tycho allowing POM-first and manifest-first dependencies.

+5
source share
2 answers

Dependency-resolution is a two-step process in Tycho:

POM- , POM. POM Tycho ( , ), Tycho . Tycho mvn install, . , ( 2) , .

, ~/.m2/repository/.meta/p2-local-metadata.properties. ( , , . 355367 , 0.16.0.)

, , , POM- Tycho:

  • , Tycho . , - , . POM . (, : .) , Tycho ( mvn install ), Tycho . Tycho , , .

  • POM- ( Maven), Tycho. - POM- , Tycho .

+6

, tycho , CLI tycho.localArtifacts = ignore, , ,

mvn clean install -Dtycho.localArtifacts=ignore

Tycho-Target Eclipse Wiki

0

More articles:


All Articles