You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@tuscany.apache.org by "Daniel Kulp (JIRA)" <tu...@ws.apache.org> on 2006/03/23 22:25:19 UTC
[jira] Created: (TUSCANY-132) Change source compliance level for
plugin to 1.4
Change source compliance level for plugin to 1.4
------------------------------------------------
Key: TUSCANY-132
URL: http://issues.apache.org/jira/browse/TUSCANY-132
Project: Tuscany
Type: Improvement
Components: Java SCA Tools
Reporter: Daniel Kulp
Priority: Minor
Attachments: pom.xml
Just an update to the plugin/pom.xml to set the souce compliance level for compiling to 1.4 instead of 1.5. This is actually important cause if you use and 1.5 features (like generics or annotations) in ANY file in a maven 2 plugin module, the build may (but not always) fail. The javadoc parser that maven 2 uses to extract the mojo configuration parameters is not capable of recognizing 1.5 constructs and will barf with a parse exception if it doesn't understand what it sees.
See: http://jira.codehaus.org/browse/MPLUGIN-1
This also has a sideaffect of cleaning up all eclipse warnings for the plugin module.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
[jira] Closed: (TUSCANY-132) Change source compliance level for
plugin to 1.4
Posted by "Jean-Sebastien Delfino (JIRA)" <tu...@ws.apache.org>.
[ http://issues.apache.org/jira/browse/TUSCANY-132?page=all ]
Jean-Sebastien Delfino closed TUSCANY-132:
------------------------------------------
> Change source compliance level for plugin to 1.4
> ------------------------------------------------
>
> Key: TUSCANY-132
> URL: http://issues.apache.org/jira/browse/TUSCANY-132
> Project: Tuscany
> Type: Improvement
> Components: Java SCA Tools
> Reporter: Daniel Kulp
> Assignee: Jean-Sebastien Delfino
> Priority: Minor
> Attachments: pom.xml
>
> Just an update to the plugin/pom.xml to set the souce compliance level for compiling to 1.4 instead of 1.5. This is actually important cause if you use and 1.5 features (like generics or annotations) in ANY file in a maven 2 plugin module, the build may (but not always) fail. The javadoc parser that maven 2 uses to extract the mojo configuration parameters is not capable of recognizing 1.5 constructs and will barf with a parse exception if it doesn't understand what it sees.
> See: http://jira.codehaus.org/browse/MPLUGIN-1
> This also has a sideaffect of cleaning up all eclipse warnings for the plugin module.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
[jira] Resolved: (TUSCANY-132) Change source compliance level for
plugin to 1.4
Posted by "Jean-Sebastien Delfino (JIRA)" <tu...@ws.apache.org>.
[ http://issues.apache.org/jira/browse/TUSCANY-132?page=all ]
Jean-Sebastien Delfino resolved TUSCANY-132:
--------------------------------------------
Resolution: Fixed
Applied your patch. Thank you.
> Change source compliance level for plugin to 1.4
> ------------------------------------------------
>
> Key: TUSCANY-132
> URL: http://issues.apache.org/jira/browse/TUSCANY-132
> Project: Tuscany
> Type: Improvement
> Components: Java SCA Tools
> Reporter: Daniel Kulp
> Assignee: Jean-Sebastien Delfino
> Priority: Minor
> Attachments: pom.xml
>
> Just an update to the plugin/pom.xml to set the souce compliance level for compiling to 1.4 instead of 1.5. This is actually important cause if you use and 1.5 features (like generics or annotations) in ANY file in a maven 2 plugin module, the build may (but not always) fail. The javadoc parser that maven 2 uses to extract the mojo configuration parameters is not capable of recognizing 1.5 constructs and will barf with a parse exception if it doesn't understand what it sees.
> See: http://jira.codehaus.org/browse/MPLUGIN-1
> This also has a sideaffect of cleaning up all eclipse warnings for the plugin module.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
[jira] Updated: (TUSCANY-132) Change source compliance level for
plugin to 1.4
Posted by "Daniel Kulp (JIRA)" <tu...@ws.apache.org>.
[ http://issues.apache.org/jira/browse/TUSCANY-132?page=all ]
Daniel Kulp updated TUSCANY-132:
--------------------------------
Attachment: pom.xml
> Change source compliance level for plugin to 1.4
> ------------------------------------------------
>
> Key: TUSCANY-132
> URL: http://issues.apache.org/jira/browse/TUSCANY-132
> Project: Tuscany
> Type: Improvement
> Components: Java SCA Tools
> Reporter: Daniel Kulp
> Priority: Minor
> Attachments: pom.xml
>
> Just an update to the plugin/pom.xml to set the souce compliance level for compiling to 1.4 instead of 1.5. This is actually important cause if you use and 1.5 features (like generics or annotations) in ANY file in a maven 2 plugin module, the build may (but not always) fail. The javadoc parser that maven 2 uses to extract the mojo configuration parameters is not capable of recognizing 1.5 constructs and will barf with a parse exception if it doesn't understand what it sees.
> See: http://jira.codehaus.org/browse/MPLUGIN-1
> This also has a sideaffect of cleaning up all eclipse warnings for the plugin module.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
[jira] Assigned: (TUSCANY-132) Change source compliance level for
plugin to 1.4
Posted by "Jean-Sebastien Delfino (JIRA)" <tu...@ws.apache.org>.
[ http://issues.apache.org/jira/browse/TUSCANY-132?page=all ]
Jean-Sebastien Delfino reassigned TUSCANY-132:
----------------------------------------------
Assign To: Jean-Sebastien Delfino
> Change source compliance level for plugin to 1.4
> ------------------------------------------------
>
> Key: TUSCANY-132
> URL: http://issues.apache.org/jira/browse/TUSCANY-132
> Project: Tuscany
> Type: Improvement
> Components: Java SCA Tools
> Reporter: Daniel Kulp
> Assignee: Jean-Sebastien Delfino
> Priority: Minor
> Attachments: pom.xml
>
> Just an update to the plugin/pom.xml to set the souce compliance level for compiling to 1.4 instead of 1.5. This is actually important cause if you use and 1.5 features (like generics or annotations) in ANY file in a maven 2 plugin module, the build may (but not always) fail. The javadoc parser that maven 2 uses to extract the mojo configuration parameters is not capable of recognizing 1.5 constructs and will barf with a parse exception if it doesn't understand what it sees.
> See: http://jira.codehaus.org/browse/MPLUGIN-1
> This also has a sideaffect of cleaning up all eclipse warnings for the plugin module.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira