You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Mirko Friedenhagen (JIRA)" <ji...@apache.org> on 2016/09/23 17:40:21 UTC

[jira] [Commented] (MNG-6090) CI friendly properties break submodule builds

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

Mirko Friedenhagen commented on MNG-6090:
-----------------------------------------

Hello [~hwellmann],
* I created a sample project (at https://gitlab.com/mfriedenhagen/mng6090/) and could reproduce the behavior, see:
https://gitlab.com/mfriedenhagen/mng6090/pipelines/4355078. There are two CI jobs which firstly {{install}} all modules and then try to verify s2 alone (called "first all, then only s2").


> 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
>
> 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.4#6332)