[
https://issues.apache.org/jira/browse/MPOM-63?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14204146#comment-14204146
]
Hudson commented on MPOM-63:
----------------------------
SUCCESS: Integrated in maven-parent #186 (See
[https://builds.apache.org/job/maven-parent/186/])
[MPOM-63] defined m-compiler-p target version to avoid plugin-tools report
limitation (hboutemy: http://svn.apache.org/viewvc/?view=rev&rev=1637749)
* /maven/pom/trunk/maven/pom.xml
> define m-compiler-p target version to avoid plugin-tools report limitation
> --------------------------------------------------------------------------
>
> Key: MPOM-63
> URL: https://issues.apache.org/jira/browse/MPOM-63
> Project: Maven POMs
> Issue Type: Wish
> Components: asf, maven
> Affects Versions: MAVEN-PLUGINS-26, MAVEN-25, ASF-15
> Reporter: Hervé Boutemy
> Assignee: Hervé Boutemy
> Fix For: ASF-16, MAVEN-26, MAVEN-PLUGINS-27
>
>
> we defined m-compiler-p configuration with default properties instead of
> m-compiler-p configuration
> {code:xml}<maven.compiler.source>1.4</maven.compiler.source>
> <maven.compiler.target>1.4</maven.compiler.target>{code}
> this causes plugin report to discover minimum JDK as "Default target for
> maven-compiler-plugin version 3.1", which is not very useful
> it's better to define m-compiler-p configuration to avoid this bug, even if
> configured value is exactly the default value
> {code:xml}<plugin>
> <groupId>org.apache.maven.plugins</groupId>
> <artifactId>maven-compiler-plugin</artifactId>
> <configuration>
> <source>${maven.compiler.source}</source>
> <target>${maven.compiler.target}</target>
> </configuration>
> </plugin>{code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
