maven-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Hervé Boutemy (JIRA) <>
Subject [jira] [Commented] (MINVOKER-194) wrong maven.compiler.source value in pom interpolation when run with Maven 3.3.x
Date Sun, 06 Sep 2015 15:26:45 GMT


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 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}} options
are added, but with these, model interpolation
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:
>             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.source}</>
>   </properties>{code}
> is interpolated to
> {code:xml}  <properties>
>     <maven.compiler.source>1.3</maven.compiler.source>
>     <>1.5</>
>   </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

View raw message