Fwd: Please review: changes to push new versions to maven repository

[Craig L Russell]

FYI. The official JPA jars that pass the TCK will be put into the maven repo shortly.

Craig

Begin forwarded message:

From: "Lance J. Andersen" <[EMAIL PROTECTED]>
Date: February 9, 2007 10:26:21 AM PST
To: [EMAIL PROTECTED]

Reply-To: [EMAIL PROTECTED]

Hi Wonseok,









Regards
Lance

Wonseok Kim wrote:

Subject: Re: Please review: changes to push new versions to maven repository Great question and this is something Marina and i discussed yesterday. The issue is that the jars in the maven repository are from june 2006. One of the issues is that signatures had some errors which have since been addressed. Where the 1.0b version came from is this is the version of the JPA TCK which has recorded the corrected signatures per the specification. For Toplink Essentials, the versioning aligns with the Glassfish build that the jar originated from. If you(or anyone else) has a better suggestion WRT versioning, let us know. We just need to release a new set of jars to the maven repository ASAP.

Hi Marina,
I'm curious about the version policy, indeed.

persistence-api:
What does it mean by "1.0b"? does "b" mean a patch version?

toplink-essentials:




Also I have following questions in my mind.

- If not, should the SJSAS version be used for maven repository?

Regards,
-Wonseok

On 2/9/07, Marina Vatkina < [EMAIL PROTECTED]> wrote:
I made the following changes to create jars with a new version:


Index: build.properties
===================================================================
RCS file: /cvs/glassfish/persistence-api/build.properties,v
retrieving revision 1.4
diff -r1.4 build.properties
29c29
< release.version=1.0
---
> release.version=1.0b


the p-api to 1.0b in entity-persistence:

Index: build.properties
===================================================================
RCS file: /cvs/glassfish/entity-persistence/build.properties,v
retrieving revision 1.2
diff -r1.2 build.properties
29c29
< release.version=1.0
---
> release.version=2.0-35
Index: toplink-essentials.pom
===================================================================
RCS file: /cvs/glassfish/entity-persistence/toplink- essentials.pom,v
retrieving revision 1.1
diff -r1.1 toplink-essentials.pom
10c10
<       <version>1.0</version>
---
>       <version>1.0b</version>


names look correct:






thanks,
-marina

Does TopLink Essentials have unique version policy ( 2.0?) other than SJSAS version (9.1)? Manifest has version like "9.1 build: b35". Also I don't think trunk build has 2.0 changes (if 9.0 build is 1.0). Then should it be 1.1? I'm not sure. I believe that version policy is important because ugly version scheme could confuse users/developers and it would not be easy to change it later. - Could TopLink Essentials be independent project (separation from GlassFish like Grizzly) in the future? - Does TopLink Essentials require unique version policy than SJSAS version( 9.0, 9.1)? 1. Changed version of the persistence-api related files to 1.0b in persistence-api: 2. Changed version of the toplink related files to 2.0-35 and the dependency on I tested by creating the files without pushing them to the repository. Their persistence-api/build/maven-repo/javax.persistence/jars/ persistence-api-1.0b.jar persistence-api/build/maven-repo/javax.persistence/jars/ persistence-api-1.0b.jar.md5 persistence-api/build/maven-repo/javax.persistence/poms/ persistence- api-1.0b.pom persistence-api/build/maven-repo/javax.persistence/poms/ persistence-api-1.0b.pom.md5 persistence-api/build/maven-repo/javax.persistence/java-sources/ persistence-api-1.0b-sources.jar persistence-api/build/maven-repo/javax.persistence/java-sources/ persistence- api-1.0b-sources.jar.md5 entity-persistence/build/maven-repo/javax.persistence/jars/toplink- essentials-2.0-35.jar entity-persistence/build/maven-repo/javax.persistence/jars/toplink- essentials-2.0-35.jar.md5 entity-persistence/build/maven-repo/javax.persistence/poms/ toplink- essentials-2.0-35.pom entity-persistence/build/maven-repo/javax.persistence/poms/toplink- essentials-2.0-35.pom.md5 entity-persistence/build/maven-repo/javax.persistence/java-sources/ toplink-essentials-2.0-35-sources.jar entity-persistence/build/maven-repo/javax.persistence/java-sources/ toplink-essentials-2.0-35-sources.jar.md5 entity-persistence/build/maven-repo/ oracle.toplink.essentials.agent/jars/toplink-essentials- agent-2.0-35.jar entity-persistence/build/maven-repo/ oracle.toplink.essentials.agent/jars/toplink-essentials- agent-2.0-35.jar.md5 entity-persistence/build/maven-repo/ oracle.toplink.essentials.agent/poms/toplink-essentials- agent-2.0-35.pom entity-persistence/build/maven-repo/ oracle.toplink.essentials.agent/poms/toplink-essentials- agent-2.0-35.pom.md5 entity-persistence/build/maven-repo/ oracle.toplink.essentials.agent/java-sources/toplink-essentials- agent-2.0-35-sources.jar entity-persistence/build/maven-repo/ oracle.toplink.essentials.agent/java-sources/toplink-essentials- agent-2.0-35-sources.jar.md5

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!

smime.p7s
Description: S/MIME cryptographic signature