[
http://jira.codehaus.org/browse/MPLUGIN-140?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
John Casey updated MPLUGIN-140:
-------------------------------
Fix Version/s: (was: 2.4.4)
2.5
Next release is 2.5, due to large changes in ant support, and addition of
PluginToolsRequest to allow shunting around of extra params in the
future...used this to add encoding, for example.
> Plugin report states wrong JDK requirement
> ------------------------------------------
>
> Key: MPLUGIN-140
> URL: http://jira.codehaus.org/browse/MPLUGIN-140
> Project: Maven 2.x Plugin Tools
> Issue Type: Bug
> Components: Plugin Plugin
> Affects Versions: 2.4.3
> Reporter: Benjamin Bentmann
> Assignee: Benjamin Bentmann
> Priority: Minor
> Fix For: 2.5
>
>
> The JDK auto detection currently checks the Compiler Plugin's target setting
> from {{<build>/<pluginManagement>}} and {{<build>/<plugins>}}, in that order
> with the first one winning. However, the setting from {{<build>/<plugins>}}
> is effectively dominant during a Maven build, i.e.
> {code:xml}
> <build>
> <pluginManagement>
> <plugins>
> <plugin>
> <artifactId>maven-compiler-plugin</artifactId>
> <configuration>
> <target>1.4</target>
> </configuration>
> </plugin>
> </plugins>
> </pluginManagement>
> <plugins>
> <plugin>
> <artifactId>maven-compiler-plugin</artifactId>
> <configuration>
> <target>1.5</target>
> </configuration>
> </plugin>
> </plugins>
> </build>
> {code}
> means JDK requirement is 1.5
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
