[
https://issues.apache.org/jira/browse/MNG-7310?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Martin Kanters updated MNG-7310:
--------------------------------
Description:
With the latest Maven master, I'm not able to build a certain multi module
project.
It fails with the following error:
C:\work\apache\demo>mvn validate
[INFO] Scanning for projects...
...
[ERROR] The build could not read 1 project -> [Help 1]
[ERROR]
[ERROR] The project com.example:demo2:0.0.1-SNAPSHOT
(C:\work\apache\demo\demo2\pom.xml) has 1 error
[ERROR] 'build.plugins.plugin.version' for
org.springframework.cloud:spring-cloud-contract-maven-plugin must be a valid
version but is '${project.version}'. @
org.apache.maven:maven-core:4.0.0-alpha-1-SNAPSHOT:default-lifecycle-bindings
The project looks as follows:
parent
– demo (module containing plugin "spring-cloud-contract-maven-plugin")
– demo2 (module)
"demo2" has no dependency on "demo" and the parent of "demo2" is "parent"..
Somehow, the plugin from "demo" leaks into "demo2", which I've verified is the
case during a debug session.
I'm still unsure of a couple of things:
- Does it only happen with the "spring-cloud-contract-maven-plugin" plugin?
- Where does ${project.version} come from? (I've not defined it)
I've done a bisect and tracked it down to the following commit:
[[MNG-5577] Convert maven-core to JSR
330|https://github.com/apache/maven/commit/9567da2bc889a94f5c3b692b4afb310ddbacd6e5]
Subject project is attached. Reproduce with the current master of Maven: mvn
validate.
was:
With the latest Maven master, I'm not able to build a certain multi module
project.
It fails with the following error:
{{C:\work\apache\demo>mvn validate}}
{{ [INFO] Scanning for projects...}}
{{ ...}}
{{ [ERROR] The build could not read 1 project -> [Help 1]}}
{{ [ERROR]}}
{{ [ERROR] The project com.example:demo2:0.0.1-SNAPSHOT
(C:\work\apache\demo\demo2\pom.xml) has 1 error}}
{{ [ERROR] 'build.plugins.plugin.version' for
org.springframework.cloud:spring-cloud-contract-maven-plugin must be a valid
version but is '${project.version}'. @
org.apache.maven:maven-core:4.0.0-alpha-1-SNAPSHOT:default-lifecycle-}}
{{ bindings}}
The project looks as follows:
{{parent}}
{{ – demo (module containing plugin "spring-cloud-contract-maven-plugin")}}
{{ – demo2 (module)}}
"demo2" has no dependency on "demo" and the parent of "demo2" is "parent"..
Somehow, the plugin from "demo" leaks into "demo2", which I've verified is the
case during a debug session.
I'm still unsure of a couple of things:
- Does it only happen with the "spring-cloud-contract-maven-plugin" plugin?
- Where does ${project.version} come from? (I've not defined it)
I've done a bisect and tracked it down to the following commit:
[[MNG-5577] Convert maven-core to JSR
330|https://github.com/apache/maven/commit/9567da2bc889a94f5c3b692b4afb310ddbacd6e5]
Subject project is attached. Reproduce with the current master of Maven: mvn
validate.
> Maven loads plugin from another submodule
> -----------------------------------------
>
> Key: MNG-7310
> URL: https://issues.apache.org/jira/browse/MNG-7310
> Project: Maven
> Issue Type: Bug
> Affects Versions: 4.0.0-alpha-1
> Reporter: Martin Kanters
> Priority: Major
> Attachments: demo-plugins.zip
>
>
> With the latest Maven master, I'm not able to build a certain multi module
> project.
> It fails with the following error:
> C:\work\apache\demo>mvn validate
> [INFO] Scanning for projects...
> ...
> [ERROR] The build could not read 1 project -> [Help 1]
> [ERROR]
> [ERROR] The project com.example:demo2:0.0.1-SNAPSHOT
> (C:\work\apache\demo\demo2\pom.xml) has 1 error
> [ERROR] 'build.plugins.plugin.version' for
> org.springframework.cloud:spring-cloud-contract-maven-plugin must be a valid
> version but is '${project.version}'. @
> org.apache.maven:maven-core:4.0.0-alpha-1-SNAPSHOT:default-lifecycle-bindings
> The project looks as follows:
> parent
> – demo (module containing plugin "spring-cloud-contract-maven-plugin")
> – demo2 (module)
> "demo2" has no dependency on "demo" and the parent of "demo2" is "parent"..
> Somehow, the plugin from "demo" leaks into "demo2", which I've verified is
> the case during a debug session.
> I'm still unsure of a couple of things:
> - Does it only happen with the "spring-cloud-contract-maven-plugin" plugin?
> - Where does ${project.version} come from? (I've not defined it)
> I've done a bisect and tracked it down to the following commit:
> [[MNG-5577] Convert maven-core to JSR
> 330|https://github.com/apache/maven/commit/9567da2bc889a94f5c3b692b4afb310ddbacd6e5]
> Subject project is attached. Reproduce with the current master of Maven: mvn
> validate.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
