[ 
https://issues.apache.org/jira/browse/MNG-6090?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15923045#comment-15923045
 ] 

Hudson commented on MNG-6090:
-----------------------------

SUCCESS: Integrated in Jenkins build maven-3.x #1568 (See 
[https://builds.apache.org/job/maven-3.x/1568/])
[MNG-6090] CI friendly properties break submodule builds [MNG-6057] 
(khmarbaise: 
[http://git-wip-us.apache.org/repos/asf/?p=maven.git&a=commit&h=51cc76c32625be2f807dcf2ffbeb085984729b57])
* (edit) 
maven-model-builder/src/main/java/org/apache/maven/model/validation/DefaultModelValidator.java
* (edit) 
maven-compat/src/main/java/org/apache/maven/artifact/resolver/DefaultArtifactResolver.java
* (edit) 
maven-model-builder/src/main/java/org/apache/maven/model/building/DefaultModelBuilder.java
* (edit) 
maven-model-builder/src/main/java/org/apache/maven/model/interpolation/AbstractStringBasedModelInterpolator.java


> CI friendly properties break submodule builds
> ---------------------------------------------
>
>                 Key: MNG-6090
>                 URL: https://issues.apache.org/jira/browse/MNG-6090
>             Project: Maven
>          Issue Type: Bug
>          Components: core
>    Affects Versions: 3.3.9
>            Reporter: Harald Wellmann
>            Assignee: Karl Heinz Marbaise
>             Fix For: 3.5.0-alpha-2
>
>
> h3. Scenario
> A multi-module project where the parent version is one of the CI friendly 
> properties, e.g. $\{revision\} as outlined in 
> http://blog.soebes.de/blog/2016/08/08/maven-how-to-create-a-release/.
> There are two submodules submodule1 and submodule2 such that submodule2 
> depends on submodule1.
> h3. Expected behaviour
> Each submodule can be built by itself, e.g.
> {code}
> mvn clean install -Drevision=1.0.0-SNAPSHOT -pl submodule2
> {code}
> or
> {code}
> cd submodule2; mvn clean install -Drevision=1.0.0-SNAPSHOT
> {code}
> h3. Actual behaviour
> This does not work for submodule2 or in general any module that depends on a 
> module from the same reactor.
> Maven cannot resolve the property variable in the referenced parent POM 
> version and fails the build:
> {code}
> [ERROR] Failed to execute goal on project submodule2: Could not resolve 
> dependencies for project com.example:submodule2:jar:1.0.0-SNAPSHOT: Failed to 
> collect dependencies at com.example:submodule1:jar:1.0.0-SNAPSHOT: Failed to 
> read artifact descriptor for com.example:submodule1:jar:1.0.0-SNAPSHOT: Could 
> not find artifact com.exammple:parent:pom:${revision} -> [Help 1]
> {code}
>  
> There is no problem building submodule1 or the entire reactor.
> Same problem observed with a local build from master (3.4.0-SNAPSHOT).



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

Reply via email to