db-jdo-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Craig Russell (JIRA)" <j...@apache.org>
Subject [jira] Updated: (JDO-278) Change group ids for jdo projects from apache-jdo to javax.jdo and org.apache.jdo
Date Tue, 17 Jan 2006 22:49:42 GMT
     [ http://issues.apache.org/jira/browse/JDO-278?page=all ]

Craig Russell updated JDO-278:
------------------------------

    Attachment: groupid.patch

- All the default goals in the maven.xml files now call jar:install instead of jar:install-snapshot.
What is the impact of this change? 

What this does is to omit the creation of the timestamp-named versions of the jar files and
pom files that are stored in the local repository. I think that this is appropriate for now,
until we have a need for nightly distributions on the distribution site. We can easily change
this when we have the requirement.

- fostore20/project.xml now includes the dependency on runtime20 twice. 

Fixed (the duplicate dependency was removed) with the latest patch.

- The patch removes the extend clause for ./project.xml from api11/project.xml.

Fixed (added back the dependency on ../project.xml) with the latest patch.


> Change group ids for jdo projects from apache-jdo to javax.jdo and org.apache.jdo
> ---------------------------------------------------------------------------------
>
>          Key: JDO-278
>          URL: http://issues.apache.org/jira/browse/JDO-278
>      Project: JDO
>         Type: Improvement
>   Components: tck20, api20, tck11, api11, ri11, btree, core20, enhancer20, fostore20,
query20, runtime20
>     Reporter: Craig Russell
>     Assignee: Craig Russell
>      Fix For: JDO 2 beta
>  Attachments: groupid.patch, groupid.patch
>
> The proposed new standard for naming group ids seems to be to use the package name of
the jar contents as the group id where there is a single package prefix.
> This change would be done prior to the beta release.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira


Mime
View raw message