db-jdo-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Michelle Caisse (JIRA)" <j...@apache.org>
Subject [jira] [Resolved] (JDO-632) Select new build/project tool
Date Fri, 17 Jun 2011 16:42:47 GMT

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

Michelle Caisse resolved JDO-632.
---------------------------------

    Resolution: Won't Fix

For the moment, we have selected maven 2. If someone wants to provide a suggestion and ratiionale
for changing, they can open a new issue.

> 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.
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Mime
View raw message