-
Feature Request
-
Resolution: Obsolete
-
Critical
-
None
-
7.1.0.DR18
-
None
Something akin to EAP7-325 should be applied to the legacy EJB client (3.0.x) as well.
With EJB client 4.x, when using EAP BOM to manage versions, I can have a short dependencies section in pom.xml like this:
<dependency>
<groupId>org.jboss</groupId>
<artifactId>jboss-ejb-client</artifactId>
</dependency>
With the legacy client (currently 3.0.0.Beta7), I have to do this
<dependency>
<groupId>org.jboss</groupId>
<artifactId>jboss-ejb-client-legacy</artifactId>
</dependency>
<dependency>
<groupId>org.jboss.xnio</groupId>
<artifactId>xnio-api</artifactId>
</dependency>
<dependency>
<groupId>org.jboss.xnio</groupId>
<artifactId>xnio-nio</artifactId>
</dependency>
<dependency>
<groupId>org.jboss.ejb3</groupId>
<artifactId>jboss-ejb3-ext-api</artifactId>
</dependency>
<dependency>
<groupId>org.jboss.spec.javax.transaction</groupId>
<artifactId>jboss-transaction-api_1.2_spec</artifactId>
</dependency>
<dependency>
<groupId>org.jboss.spec.javax.ejb</groupId>
<artifactId>jboss-ejb-api_3.2_spec</artifactId>
</dependency>
<dependency>
<groupId>org.jboss.marshalling</groupId>
<artifactId>jboss-marshalling-river</artifactId>
</dependency>
- blocks
-
-
- Closed
-
- relates to
-
-
- Closed
-
