db-jdo-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Michael Bouschen (JIRA)" <j...@apache.org>
Subject [jira] Updated: (JDO-632) Select new build/project tool
Date Fri, 17 Sep 2010 16:50:35 GMT

     [ https://issues.apache.org/jira/browse/JDO-632?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Michael Bouschen updated JDO-632:
---------------------------------

             Assignee: Michelle Caisse
        Fix Version/s: JDO 3 maintenance release 1
    Affects Version/s: JDO 3
          Component/s:     (was: core2)
                           (was: enhancer2)
                           (was: fostore2)
                           (was: query2)
                           (was: runtime2)
                           (was: util2)
                           (was: model2)

> Select new build/project tool
> -----------------------------
>
>                 Key: JDO-632
>                 URL: https://issues.apache.org/jira/browse/JDO-632
>             Project: JDO
>          Issue Type: Improvement
>          Components: api, tck
>    Affects Versions: JDO 3
>            Reporter: Matthew T. Adams
>            Assignee: Michelle Caisse
>            Priority: Minor
>             Fix For: JDO 3 maintenance release 1
>
>
> JDO-596 requests an upgrade to Maven2.  At this point, I would recommend that we evaluate
some other solutions (listed in no particular order):
> * Maven2
> * Ant+Ivy
> * Gant+Ivy
> * Gradle
> We could potentially reap time savings by using a build & test tool that leverages
dynamic languages like Groovy in the TCK.

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