[jboss-jira] [JBoss JIRA] Resolved: (JBEE-15) Break all EEl apis into separately versioned subprojects

Break all EEl apis into separately versioned subprojects -------------------------------------------------------- Key: JBEE-15 URL: https://jira.jboss.org/browse/JBEE-15 Project: JBoss JavaEE APIs Issue Type: Task Components: Deployment API, EJB API, JACC API, JASPI API, JAXR API, JCA API, JMS API, Persistence API, Servlet API, Transaction API Reporter: Jason T. Greene Assignee: Shelly McGowan Fix For: 1.0.0.CR1 We should break up all modules in the Java EE project to be separately versioned components, in line with the specification they represent. In addition we should version them according to the specification version of the api, and not a version we come up with. This makes it easy for our other projects to know they are consuming the proper version. Hibernate, for example, would like to have a dependency on jta 1.1. It's not immediately clear what we have that implements 1.1. The SVN layout should look like: /projects/javaee/transaction-api/tags/1.1 /projects/javaee/ejb3-api/tags/3.1 etc The maven coordinates should remain the same, as this allows for a project to quickly and easily see what javax apis are available: org.jboss.javaee:transaction-api