maven-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Dennis Lundberg (JIRA)" <j...@codehaus.org>
Subject [jira] Commented: (MPLUGIN-177) Required JDK incorrectly specified if using default for m-compiler-p
Date Fri, 04 Feb 2011 20:50:22 GMT

    [ http://jira.codehaus.org/browse/MPLUGIN-177?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=254697#action_254697
] 

Dennis Lundberg commented on MPLUGIN-177:
-----------------------------------------

I get the same results with Maven 2.2.1 with Maven Site Plugin 2.2.

> Required JDK incorrectly specified if using default for m-compiler-p
> --------------------------------------------------------------------
>
>                 Key: MPLUGIN-177
>                 URL: http://jira.codehaus.org/browse/MPLUGIN-177
>             Project: Maven 2.x Plugin Tools
>          Issue Type: Bug
>    Affects Versions: 2.6
>         Environment: Maven 3.0.1
> Windows XP and MacOS
> JDK 1.6 (Sun and Mac Java, respectively)
>            Reporter: Anders Hammar
>         Attachments: plugin-info-jdk-issue.zip
>
>
> If not specifying source/target for the m-compiler-p but using the defaults (JDK 1.5
for m-compiler-p:2.3.2), the Plugin's documentation report generated by plugin:report incorrectly
specifies JDK 1.1.
> This was seen with Maven 3.0.1, but might also be an issue with Maven 2.x. Haven't testad
that.
> Attaching a test project where this can be seen (tested with Maven 3.0.1). Execute
> mvn site
> and view the plugin-info.html page.

-- 
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

        

Mime
View raw message