Re: [forge-dev] JBoss Maven Java EE 6
Nope, that's what we are already using. We could upgrade to 3.0.0.Final, or
better yet give the user the choice.
Note that there is still a bug in the specs that require an exclusion to
use with Arquillian (works fine for compilation).
<dependency>
<groupId>org.jboss.spec</groupId>
<artifactId>jboss-javaee-6.0</artifactId>
<version>3.0.0.Final</version>
<type>pom</type>
<scope>provided</scope>
<exclusions>
<exclusion>
<groupId>org.apache.xalan</groupId>
<artifactId>xalan</artifactId>
</exclusion>
</exclusions>
</dependency>
This isn't a problem if you are just using the spec bom to import
dependency versions (scope = import).
-Dan
On Fri, Jun 1, 2012 at 3:13 AM, Ivan St. Ivanov <ivan.st.ivanov(a)gmail.com>wrote:
Hi folks,
Look what I found today:
http://planet.jboss.org/post/jboss_maven_java_ee_6_specification_apis
Is there a change with respect to the current situation with the maven
dependencies? Should we do anything in Forge?
Cheers,
Ivan
_______________________________________________
forge-dev mailing list
forge-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/forge-dev
--
Dan Allen
Principal Software Engineer, Red Hat | Author of Seam in Action
Registered Linux User #231597
http://google.com/profiles/dan.j.allen
http://mojavelinux.com
http://mojavelinux.com/seaminaction
Attachments:
- attachment.html (text/html — 2.4 KB)