db-jdo-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Matthew T. Adams (Commented) (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (JDO-707) Refactor JDO parent & child poms
Date Fri, 09 Mar 2012 18:01:00 GMT

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

Matthew T. Adams commented on JDO-707:

The improvement comes when we release the 3.1 artifacts to Maven Central.  When I released
3.0.1, I had to manually copy information from the parent pom into the JDO API pom.  In 3.1,
when we release, we should release not only artifact jdo-api, but also parent-pom.  Then,
there will not have to be any manual copying from the parent pom into the jdo-api pom.
> Refactor JDO parent & child poms
> --------------------------------
>                 Key: JDO-707
>                 URL: https://issues.apache.org/jira/browse/JDO-707
>             Project: JDO
>          Issue Type: Improvement
>          Components: api, tck
>    Affects Versions: JDO 3 maintenance release 1 (3.1)
>            Reporter: Matthew T. Adams
>            Assignee: Matthew T. Adams
>              Labels: parent, pom
>             Fix For: JDO 3 maintenance release 1 (3.1)
>         Attachments: JDO-707-1.patch
> Create a parent-pom module, make modules api, exectck & tck inherit from it, then
create a simple multimodule root pom which can be used to build all projects.

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira


View raw message