Hi Craig,
I agree that we should have different artifact names and build them with
different svn workspaces.
JDK 5 is the current version and JDK 6 is about to be released. So would
it make sense to use the current projects for the JDK 5 version and
create new projects for the older versions JDK 1.3/1.4. Is 'legacy' the
right term for this support and is it an idea to used this in the
artifactId? Then we could have the following:
project name artifactId => jar file name
---------------------------------------------------------------
api2 jdo2-api => jdo2-api-2.1.jar
tck2 jdo2-tck => jdo2-tck-2.1.jar
api2-legacy jdo2-legacy-api => jdo2-legacy-api-2.1.jar
tck2-legacy jdo2-legacy-tck => jdo2-legacy-tck-2.1.jar
I'm using api2 instead of api20, because it might have been an error to
put the version number 2.0 into the project name. This is already
covered by the version number 2.0 in the jar file: jdo2-api-2.0.jar.
Regards Michael
Some more ideas:
project name, artifactId ==> jar file name
api21, jdo21-api ==> jdo21-api-2.1.jar
tck21, jdo21-tck ==> jdo21-tck-2.1.jar
api215, jdo21-api5 ==> jdo21-api5-2.1.jar
tck215, jdo21-tck5 ==> jdo21-tck5.2.1.jar
Craig
On Nov 4, 2006, at 1:37 PM, Craig L Russell wrote:
api205 jdo2-api5 ==> jdo2-api5-2.1.jar
api25 jdo25-api ==> jdo25-api-2.1.jar
api2-5 jdo2-5-api ==> jdo2-5-api-2.1.jar
api2-1.5 jdo2-1.5-api ==> jdo2-1.5-api-2.1.jar
Craig Russell
Architect, Sun Java Enterprise System http://java.sun.com/products/jdo
408 276-5638 mailto:[EMAIL PROTECTED]
P.S. A good JDO? O, Gasp!
--
Michael Bouschen [EMAIL PROTECTED] Engineering GmbH
mailto:[EMAIL PROTECTED] http://www.tech.spree.de/
Tel.:++49/30/235 520-33 Buelowstr. 66
Fax.:++49/30/2175 2012 D-10783 Berlin
