Re: [eclipselink-dev] Changes for MavenCentral...

[Eric Gwin <eric.gwin@xxxxxxxxxx>]

Update: After another round of discussions, it appears that everyone who weighed in on the subject is good with the plan, except:
   javax.persistence 2.1 is pre-release (though currently built as 2.0.106 for OSGi).
   It is not really a release jar, so should be published in Maven as 2.1-SNAPSHOT, not Release 2.0.106.

Therefore, the plan for javax.persistence changed as follows:
- The jar will retain the current OSGi versioning scheme, but be published as 2.1-SNAPSHOT.
- When EclipseLink releases a Milestone, javax.persistence will also be released as a Milestone.
   (EclipseLink 2.5.0-M7 promotion will also create javax.persistence 2.1-M7)

Also, though this really isn't a change, it does become a requirement:
- The release build for javax.persistence will need to occur before the release of EclipseLink 2.5 (because the
 EclipseLink build.type will be tied to javax.persistence as well, and that linkage will need to be changed prior to EclipseLink's release).

-Eric

On 01/02/2013 6:03 PM, Eric Gwin wrote:

All,

After some discussion offline it is obvious that my emails on this topic were not clear, so I've attached a spreadsheet in the hope that 'a picture can speak 1000 words'. I hope it will better explain the changes, scope and how things will work.

Eric

_______________________________________________
eclipselink-dev mailing list
eclipselink-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/eclipselink-dev