Change group ids for jdo projects from apache-jdo to javax.jdo and org.apache.jdo

• Key: JDO-278
• Type: Improvement
• Status: Resolved
• Resolution: Fixed
• Priority: Major
• Assignee: Craig Russell
• Reporter: Craig Russell
• Component/s: api11, api2, btree, core2, enhancer2, fostore2, query2, ri11, runtime2, tck11, tck2
• Fix Version/s: JDO 2 beta

Description

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.

Comments

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.

[Craig Russell]

Please review. This is ready for checkin.

[Michael Bouschen]

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.

[Craig Russell]

- 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.

[Craig Russell]

Committed revision 369999.