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 (Created) (JIRA)" <ji...@apache.org> on 2012/03/16 18:09:39 UTC
[jira] [Created] (JDO-711) Reorganize project sources to abide by
maven conventions
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
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
[jira] [Commented] (JDO-711) Reorganize project sources to abide by
maven conventions
Posted by "Matthew T. Adams (Commented) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/JDO-711?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13258353#comment-13258353 ]
Matthew T. Adams commented on JDO-711:
--------------------------------------
No objections after a month, so I will upload patch for review in prep for commit as part of 3.1.
> 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
[jira] [Commented] (JDO-711) Reorganize project sources to abide by
maven conventions
Posted by "Matthew T. Adams (Commented) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/JDO-711?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13231396#comment-13231396 ]
Matthew T. Adams commented on JDO-711:
--------------------------------------
Anyone object to my doing this for 3.1 since we're going all maven 2 with this release?
> 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
>
> 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
[jira] [Commented] (JDO-711) Reorganize project sources to abide by
maven conventions
Posted by "Craig L Russell (JIRA)" <ji...@apache.org>.
[ 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
[jira] [Updated] (JDO-711) Reorganize project sources to abide by
maven conventions
Posted by "Michael Bouschen (Updated) (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/JDO-711?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Michael Bouschen updated JDO-711:
---------------------------------
Fix Version/s: JDO 3 maintenance release 1 (3.1)
> 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
[jira] [Commented] (JDO-711) Reorganize project sources to abide by
maven conventions
Posted by "Andy Jefferson (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/JDO-711?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13408221#comment-13408221 ]
Andy Jefferson commented on JDO-711:
------------------------------------
Really don't see why this is considered as needed for JDO 3.1.
So Apache JDO doesn't use Maven(2) defaults (it uses what Maven1 required more or less), but then that is why Maven allows the project to set the location of source and tests (and it was Maven that actually changed its "standard" when they introduced Maven2 anyway). DataNucleus does the same also FWIW and I've no plans to do such a change; it doesn't stop people engaging with a project. Projects are able to have their own conventions. Much more important things to be doing IMHO ... like typesafe queries for example, something that would add real value to users.
> 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
[jira] [Closed] (JDO-711) Reorganize project sources to abide by
maven conventions
Posted by "Matthew T. Adams (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/JDO-711?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Matthew T. Adams closed JDO-711.
--------------------------------
Resolution: Won't Fix
Not worth it.
> 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
For more information on JIRA, see: http://www.atlassian.com/software/jira