You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@geronimo.apache.org by "David Jencks (JIRA)" <ji...@apache.org> on 2010/05/08 20:12:47 UTC
[jira] Created: (GERONIMO-5290) Upgrade to maven 3
Upgrade to maven 3
------------------
Key: GERONIMO-5290
URL: https://issues.apache.org/jira/browse/GERONIMO-5290
Project: Geronimo
Issue Type: Bug
Security Level: public (Regular issues)
Components: buildsystem
Affects Versions: 3.0
Reporter: David Jencks
Assignee: David Jencks
Fix For: 3.0
Maven 3 already provides a lot more useful info than maven 2 and is obviously the future. To get maven 3 to work we need to:
- fix a couple of problems with the car-maven-plugin's access to internal maven data structures which sometimes contain information in a different state of resolution or expansion
- upgrade gmaven to a recent release (which involves changing some package names in some plugins)
Maven 3 also provides a lot of deprecation warnings so we should also change ${version} to ${project.version} etc.
These changes are compatible with maven 2.2.1
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Closed: (GERONIMO-5290) Upgrade to maven 3
Posted by "David Jencks (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/GERONIMO-5290?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
David Jencks closed GERONIMO-5290.
----------------------------------
Resolution: Fixed
Most deprecations maven3 reported fixed in rev 942493. These are:
${version} replaced by ${project.version}
${artifactId} replaced by ${project.artifactId}
${groupId} replaced by ${project.groupId}
provide a version for the geronimo-property-plugin
rev 942494 reverts an accidentally committed jetty version change.
> Upgrade to maven 3
> ------------------
>
> Key: GERONIMO-5290
> URL: https://issues.apache.org/jira/browse/GERONIMO-5290
> Project: Geronimo
> Issue Type: Bug
> Security Level: public(Regular issues)
> Components: buildsystem
> Affects Versions: 3.0
> Reporter: David Jencks
> Assignee: David Jencks
> Fix For: 3.0
>
>
> Maven 3 already provides a lot more useful info than maven 2 and is obviously the future. To get maven 3 to work we need to:
> - fix a couple of problems with the car-maven-plugin's access to internal maven data structures which sometimes contain information in a different state of resolution or expansion
> - upgrade gmaven to a recent release (which involves changing some package names in some plugins)
> Maven 3 also provides a lot of deprecation warnings so we should also change ${version} to ${project.version} etc.
> These changes are compatible with maven 2.2.1
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (GERONIMO-5290) Upgrade to maven 3
Posted by "David Jencks (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/GERONIMO-5290?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12865494#action_12865494 ]
David Jencks commented on GERONIMO-5290:
----------------------------------------
gmaven support upgrade in rev 942433 (gmaven) and rev 942434 (gossip)
car-maven-plugin changes to maven data structure access in rev 942436
> Upgrade to maven 3
> ------------------
>
> Key: GERONIMO-5290
> URL: https://issues.apache.org/jira/browse/GERONIMO-5290
> Project: Geronimo
> Issue Type: Bug
> Security Level: public(Regular issues)
> Components: buildsystem
> Affects Versions: 3.0
> Reporter: David Jencks
> Assignee: David Jencks
> Fix For: 3.0
>
>
> Maven 3 already provides a lot more useful info than maven 2 and is obviously the future. To get maven 3 to work we need to:
> - fix a couple of problems with the car-maven-plugin's access to internal maven data structures which sometimes contain information in a different state of resolution or expansion
> - upgrade gmaven to a recent release (which involves changing some package names in some plugins)
> Maven 3 also provides a lot of deprecation warnings so we should also change ${version} to ${project.version} etc.
> These changes are compatible with maven 2.2.1
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.