[
https://issues.apache.org/jira/browse/MINVOKER-194?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14732442#comment-14732442
]
Hervé Boutemy commented on MINVOKER-194:
----------------------------------------
perhaps a fix in Sisu regarding Map/Properties?
IIRC, there was something like this
then the behaviour would not be a bug but a feature with Maven 3.3 :)
> 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)
