[
https://issues.apache.org/jira/browse/MINVOKER-194?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14732421#comment-14732421
]
Hervé Boutemy commented on MINVOKER-194:
----------------------------------------
I executed the MPIR IT with -X enabled and found a difference in invoker
invocation between Maven 3.2.5:
{noformat}[DEBUG] Executing: /bin/sh -c cd
/tmp/maven-project-info-reports-plugin/target/it/java-version &&
/local/maven/apache-maven-3.2.5/bin/mvn -B -X -D
maven.repo.local=/tmp/maven-project-info-reports-plugin/target/local-repo -s
/tmp/maven-project-info-reports-plugin/target/it/interpolated-settings.xml
org.apache.maven.plugins:maven-project-info-reports-plugin:2.8.1-SNAPSHOT:summary
help:effective-pom -Doutput=effective-poms.xml{noformat}
and Maven 3.3.3:
{noformat}[DEBUG] Executing: /bin/sh -c cd
/tmp/maven-project-info-reports-plugin/target/it/java-version &&
/local/apache-maven-3.3.3/bin/mvn -B -X -D
maven.repo.local=/tmp/maven-project-info-reports-plugin/target/local-repo -s
/tmp/maven-project-info-reports-plugin/target/it/interpolated-settings.xml -D
maven.compiler.source=1.5 -D maven.compiler.target=1.5
org.apache.maven.plugins:maven-project-info-reports-plugin:2.8.1-SNAPSHOT:summary
help:effective-pom -Doutput=effective-poms.xml{noformat}
I don't know why these {{-D maven.compiler.source=1.5 -D
maven.compiler.target=1.5}} options are added, but with these, model
interpolation http://maven.apache.org/ref/3-LATEST/maven-model-builder/ prefers
CLI over POM properties, then the result is consistent with the options
now we need to understand why these options are defined with Maven 3.3.x only
> wrong maven.compiler.source value in pom interpolation when run with Maven
> 3.3.x
> --------------------------------------------------------------------------------
>
> Key: MINVOKER-194
> URL: https://issues.apache.org/jira/browse/MINVOKER-194
> Project: Maven Invoker Plugin
> Issue Type: Bug
> Affects Versions: 1.8, 2.0.0
> Reporter: Hervé Boutemy
>
> when working on MPIR, I found that java-version IT failed when build run with
> with Maven 3.3.x, but not when run with Maven 3.2.x or less
> I found that
> {code:xml} <properties>
> <maven.compiler.source>1.3</maven.compiler.source>
> <maven.compiler.target>${maven.compiler.source}</maven.compiler.target>
> </properties>{code}
> is interpolated to
> {code:xml} <properties>
> <maven.compiler.source>1.3</maven.compiler.source>
> <maven.compiler.target>1.5</maven.compiler.target>
> </properties>{code}
> when the IT is run with Maven 3.3.x
> but when the IT project is not run through invoker, there is no such
> interpolation value issue, so I suppose m-invoker-p has some role when used
> in conjunction with Maven 3.3.x
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
