db-jdo-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Craig Russell (JIRA)" <j...@apache.org>
Subject [jira] Commented: (JDO-596) Upgrade to maven 2
Date Sun, 03 May 2009 21:24:30 GMT

    [ https://issues.apache.org/jira/browse/JDO-596?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12705447#action_12705447
] 

Craig Russell commented on JDO-596:
-----------------------------------

In my workspace I have a pom.xml parallel to trunk:

<project>
  <modelVersion>4.0.0</modelVersion>
  <groupId>javax.jdo</groupId>
  <artifactId>root</artifactId>
  <version>2.3-SNAPSHOT</version>
  <packaging>pom</packaging>
</project>

I think this is a better solution since in future we can avoid changing poms in each subproject
and simply update the version number in trunk (or in branches/2.3) to have the right version
number.

> Upgrade to maven 2
> ------------------
>
>                 Key: JDO-596
>                 URL: https://issues.apache.org/jira/browse/JDO-596
>             Project: JDO
>          Issue Type: Improvement
>          Components: api2
>            Reporter: Michelle Caisse
>            Assignee: Craig Russell
>            Priority: Minor
>             Fix For: JDO 2 maintenance release 3
>
>         Attachments: jdo-596.patch
>
>
> It would be a good idea to use maven 2. This involves rewriting the custom goals in maven.xml
as Java plugins, among other things.
> This is for the JDO API not for the JDO TCK. We need a separate issue for the corresponding
TCK change. 

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


Mime
View raw message