db-jdo-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Craig L Russell (JIRA)" <j...@apache.org>
Subject [jira] [Commented] (JDO-711) Reorganize project sources to abide by maven conventions
Date Fri, 06 Jul 2012 19:45:34 GMT

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

Craig L Russell commented on JDO-711:

I agree it's not critical for 3.1. If it makes it into the release, fine. Let's not hold the
release for this. Similarly for re-parenting the sub-projects.
> Reorganize project sources to abide by maven conventions
> --------------------------------------------------------
>                 Key: JDO-711
>                 URL: https://issues.apache.org/jira/browse/JDO-711
>             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
>            Priority: Trivial
>              Labels: maven, pom
>             Fix For: JDO 3 maintenance release 1 (3.1)
> The current source trees for the JDO projects api & tck don't abide by maven conventions.
 This request is to reorganize the source trees so that they do, reducing required pom metadata
and enabling new developers to easily comprehend the 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