Java EE 7 Maven Coordinates

Skip to end of metadata
Go to start of metadata

Java EE 7 Maven Coordinates

If you need Java EE Full Platform APIs then use the coordinates described in the first row. The second row provides the same for Web Profile. These are the recommended way even if only one or more technology is used. All of them are available in Maven central.

The complete set of coordinates can be seen at:

Refer to general guidelines on Maven Versioning Rules.

Component Maven
Java EE 7 Full Platform JSR 342 <dependency>
   <groupId>javax</groupId>  
    <artifactId>javaee-api</artifactId>  
    <version>7.0</version>
</dependency>
Java EE 7 Web Profie <dependency> 
   <groupId>javax</groupId>   
    <artifactId>javaee-web-api</artifactId>   
    <version>7.0</version> 
</dependency>
Concurrency Utilities for Java EE (JSR 236) <dependency>
    <groupId>javax.enterprise.concurrent</groupId>
    <artifactId>javax.enterprise.concurrent-api</artifactId>
    <version>1.0</version>       
</dependency>
Java Persistence API 2.1 (JSR 338)
<dependency> 
  <groupId>org.eclipse.persistence</groupId> 
    <artifactId>javax.persistence</artifactId> 
    <version>2.1.0</version></dependency>
Java API for RESTful Web Services 2.0 (JSR 339) <dependency>
    <groupId>javax.ws.rs</groupId>
    <artifactId>javax.ws.rs-api</artifactId>
    <version>2.0</version>
</dependency>
Servlets 3.1 (JSR 340) <dependency>
    <groupId>javax.servlet</groupId>
    <artifactId>javax.servlet-api</artifactId>
    <version>3.1.0</version>
</dependency>
Expression Language 3.0 (JSR 341) <dependency>
    <groupId>javax.el</groupId>
    <artifactId>javax.el-api</artifactId>
    <version>3.0.0</version>
<dependency>
Java Message Service 2.0 (JSR 343) <dependency>
    <groupId>javax.jms</groupId>
    <artifactId>javax.jms-api</artifactId>
    <version>2.0</version>
</dependency>
JavaServer Faces 2.2 (JSR 344) <dependency>
    <groupId>javax.faces</groupId>
    <artifactId>javax.faces-api</artifactId>
    <version>2.2</version>
</dependency>
Enterprise JavaBeans 3.2 (JSR 345) <dependency> 
    <groupId>javax.ejb</groupId> 
    <artifactId>javax.ejb-api</artifactId> 
    <version>3.2</version> 
</dependency>
Context & Dependency Injection 1.1 (JSR 346) <dependency>
    <groupId>javax.enterprise</groupId>
    <artifactId>cdi-api</artifactId>
    <version>1.1</version>
</dependency>
Bean Validation 1.1 (JSR 349) <dependency>
    <groupId>javax.validation</groupId>
    <artifactId>validation-api</artifactId>
    <version>1.1.0.Final</version>
</dependency>
Batch Applications for the Java Platform (JSR 352) <dependency>
    <groupId>javax.batch</groupId>
    <artifactId>javax.batch-api</artifactId>
    <version>1.0</version>
</dependency>
Java API for JSON Processing (JSR 353) <dependency>
    <groupId>javax.json</groupId>
    <artifactId>javax.json-api</artifactId>
    <version>1.0</version>
</dependency>
Java API for WebSocket (JSR 356) <dependency>
    <groupId>javax.websocket</groupId>
    <artifactId>javax.websocket-api</artifactId>
    <version>1.0</version>           
</dependency>
Java Transaction API 1.2 (JSR 907) <dependency> 
    <groupId>javax.transaction</groupId> 
    <artifactId>javax.transaction-api</artifactId> 
    <version>1.2</version>            
</dependency>
Java EE Connector Architecture 1.7  (JSR 322) <dependency>
  <groupId>javax.resource</groupId>
  <artifactId>javax.resource-api</artifactId>
  <version>1.7</version>
</dependency>
Labels:
None
Enter labels to add to this page:
Please wait 
Looking for a label? Just start typing.
  1. Mar 07, 2013

    Can you please also add the coordinates of archetypes required for generating the JEE7 apps?

    Thx

    Vimal

  2. Apr 12, 2013

    For JSON-P maven dependency please note the following:

    1. The org.glassfish : javax.json is RI jar which contains both api+impl. which could be used in testing and Java SE application.
    2. The javax.json:javax.json-api contains only API which is there for compile time only.

Sign up or Log in to add a comment or watch this page.


The individuals who post here are part of the extended Oracle community and they might not be employed or in any way formally affiliated with Oracle. The opinions expressed here are their own, are not necessarily reviewed in advance by anyone but the individual authors, and neither Oracle nor any other party necessarily agrees with them.