You are viewing a plain text version of this content. The canonical link for it is here.
Posted to jdo-dev@db.apache.org by "Matthew T. Adams (JIRA)" <ji...@apache.org> on 2009/05/01 01:03:30 UTC
[jira] Created: (JDO-632) Select new build/project tool
Select new build/project tool
-----------------------------
Key: JDO-632
URL: https://issues.apache.org/jira/browse/JDO-632
Project: JDO
Issue Type: Improvement
Components: api2, core2, enhancer2, fostore2, model2, query2, runtime2, tck2, util2
Reporter: Matthew T. Adams
Priority: Minor
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.
[jira] Commented: (JDO-632) Select new build/project tool
Posted by "Andy Jefferson (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/JDO-632?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12768675#action_12768675 ]
Andy Jefferson commented on JDO-632:
------------------------------------
Since the related JIRA was closed a long time ago, is moving to some other build system really being considered ? and if so why ? and who is going to provide the resource to do this ? presumably Matthew will be doing it. I'd suggest this is closed unless somebody offers their time to do it ... after justifying the benefits of it all, of course.
> Select new build/project tool
> -----------------------------
>
> Key: JDO-632
> URL: https://issues.apache.org/jira/browse/JDO-632
> Project: JDO
> Issue Type: Improvement
> Components: api2, core2, enhancer2, fostore2, model2, query2, runtime2, tck2, util2
> Reporter: Matthew T. Adams
> Priority: Minor
>
> 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.
[jira] Updated: (JDO-632) Select new build/project tool
Posted by "Michael Bouschen (JIRA)" <ji...@apache.org>.
[ 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.