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 "Craig Russell (JIRA)" <ji...@apache.org> on 2006/01/14 20:37:21 UTC
[jira] Created: (JDO-278) Change group ids for jdo projects from
apache-jdo to javax.jdo and org.apache.jdo
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: api11, api20, btree, core20, enhancer20, fostore20, query20, ri11, runtime20, tck11, tck20
Reporter: Craig Russell
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
Re: [jira] Commented: (JDO-278) Change group ids for jdo projects from
apache-jdo to javax.jdo and org.apache.jdo
Posted by Michelle Caisse <Mi...@Sun.COM>.
Hi Craig,
I tested with a clean install, maven tck20.default, and maven build.
Seems to work just fine.
-- Michelle
Craig Russell (JIRA) wrote:
> [ http://issues.apache.org/jira/browse/JDO-278?page=comments#action_12363017 ]
>
>Craig Russell commented on JDO-278:
>-----------------------------------
>
>Please review. This is ready for checkin.
>
>
>
>
>>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
>>
>>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.
>>
>>
>
>
>
[jira] Commented: (JDO-278) Change group ids for jdo projects from
apache-jdo to javax.jdo and org.apache.jdo
Posted by "Craig Russell (JIRA)" <ji...@apache.org>.
[ http://issues.apache.org/jira/browse/JDO-278?page=comments#action_12363017 ]
Craig Russell commented on JDO-278:
-----------------------------------
Please review. This is ready for checkin.
> 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
>
> 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
[jira] Updated: (JDO-278) Change group ids for jdo projects from
apache-jdo to javax.jdo and org.apache.jdo
Posted by "Craig Russell (JIRA)" <ji...@apache.org>.
[ http://issues.apache.org/jira/browse/JDO-278?page=all ]
Craig Russell updated JDO-278:
------------------------------
Fix Version: JDO 2 beta
> 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
>
> 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
[jira] Commented: (JDO-278) Change group ids for jdo projects from
apache-jdo to javax.jdo and org.apache.jdo
Posted by "Michael Bouschen (JIRA)" <ji...@apache.org>.
[ http://issues.apache.org/jira/browse/JDO-278?page=comments#action_12363038 ]
Michael Bouschen commented on JDO-278:
--------------------------------------
Looks good, just a few comments:
- 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?
- fostore20/project.xml now includes the dependency on runtime20 twice.
- The patch removes the extend clause for ./project.xml from api11/project.xml.
> 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
>
> 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
[jira] Assigned: (JDO-278) Change group ids for jdo projects from
apache-jdo to javax.jdo and org.apache.jdo
Posted by "Craig Russell (JIRA)" <ji...@apache.org>.
[ http://issues.apache.org/jira/browse/JDO-278?page=all ]
Craig Russell reassigned JDO-278:
---------------------------------
Assign To: Craig Russell
> 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
> Attachments: 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
[jira] Updated: (JDO-278) Change group ids for jdo projects from
apache-jdo to javax.jdo and org.apache.jdo
Posted by "Craig Russell (JIRA)" <ji...@apache.org>.
[ http://issues.apache.org/jira/browse/JDO-278?page=all ]
Craig Russell updated JDO-278:
------------------------------
Attachment: groupid.patch
This patch updates the group id to javax.jdo (api11 and api20 projects) or org.apache.jdo (for all other projects) and changes the version to SNAPSHOT for all projects.
> 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
> Attachments: 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
[jira] Updated: (JDO-278) Change group ids for jdo projects from
apache-jdo to javax.jdo and org.apache.jdo
Posted by "Craig Russell (JIRA)" <ji...@apache.org>.
[ 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
[jira] Resolved: (JDO-278) Change group ids for jdo projects from
apache-jdo to javax.jdo and org.apache.jdo
Posted by "Craig Russell (JIRA)" <ji...@apache.org>.
[ http://issues.apache.org/jira/browse/JDO-278?page=all ]
Craig Russell resolved JDO-278:
-------------------------------
Resolution: Fixed
Committed revision 369999.
> 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