JBEE-15 - Break all EE apis into separately versioned subprojects

[shelly.mcgowan]

I've started working on JBEE-15 to implement versioning changes to the JAVA EE API set intending to equate the version of the artifact to the specification version.   Discussions on the proposal can be seen in the referenced JIRA. Using JTA APIs as an example, the structure would be:

org/jboss/javaee/javax/transaction/transaction-api_1.1_spec/1.0-SNAPSHOT/transaction-api_1.1_spec-1.0-SNAPSHOT.jar

which would be consumed using:

     <dependency>
      <groupId>org.jboss.javaee.javax.transaction</groupId>
      <artifactId>transaction-api_1.1_spec</artifactId>
      <version>1.0-SNAPSHOT</version>
     </dependency>

I'd like to publish a release for JBoss AS 6.0.0.M2 but want to see if there are there other suggestions to above to be considered for project consumption before doing so?

[sebersole]

I just wanted to point out the need (for Hibernate's needs anyway) to at least have this available targeting JDK 1.4.  Someone on IRC (David Llyod perhaps) mentioned that the 1.6 runtime was able to load classes faster if they are compiled targetting 1.6 and suggested compiling for all the JDKs.

[ropalka]

How about the OSGi support?
IMHO this effort should cover it as well
and all our JBEE artifacts should be OSGi compliant.

[thomas.diesler]

In OSGi it is the java package that is versioned, not the artefact (i.e. bundle) that provides it.

In order to have multiple versions of the same API available at runtime, the artefactId must of be distinct.

So AFAICS, what has been suggested above is ok from the OSGi perspective - except the missing OSGi manifest entries of course

Please note, that geronimo is already using API bundles and not jars. They do what I suggested above (i.e. version the package, give the bundles distinct names)

http://svn.apache.org/repos/asf/geronimo/specs/trunk/geronimo-jaxb_2.1_spec/pom.xml