db-jdo-dev mailing list archives

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

    [ 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

        

Mime
View raw message