Java EE 7 maven archetypes for WildFly

[robscottdeed]

Are there any Java EE 7 maven archetypes for WildFly? I can't find any in the JBoss Nexus repository. Any help would be appreciated.

[arungupta]

Is the maven archetype defined at https://blogs.oracle.com/arungupta/entry/java_ee_7_maven_archetype not sufficient ?

[robscottdeed]

Arun, thank you for responding and yes your archetype is usable. JBoss archetypes use a "Bill of Materials" to specify versions for a "stack" of dependencies which include not only JEE APIs but JBoss APIs as well. I could adapt your archetype or the JBoss JEE 6 archetypes but I don't want to reinvent the wheel if they already exist.

[arungupta]

I followed up and found the following link:

https://github.com/jboss/jboss-javaee-specs

Is that what you are looking for ?

[robscottdeed]

Yes, that will work, thank you.

[onlywei]

Hello, I am also looking for a Maven archetype to use with WildFly. I am not sure what to do with these links you have provided, though.

I have Eclipse Kepler with JBoss Tools, and when I select:

New -> Project > JBoss Central -> Java EE EAR Project

I only get an archetype for JBoss AS 7 or EAP 6. It also selects "jboss-bom-enterprise-version" 1.0.4.Final-redhat-4.

I get the feeling that I can use this, but the pom.xml it generates contains a lot of references to the older JBoss version. I would really appreciate any information on how to modify this pom.xml to reference WildFly 8.0.0.Final instead of the older JBoss version.

[ctomc]

We also have sets of BOMs for developing applications:

they can be found here: wildfly/boms · GitHub

[robscottdeed]

Using the Java EE EAR Project as a template you will need to do the following.

1. In the parent POM modify the JBoss version properties for WildFly: version.jboss.maven.plugin : 8.0.0.Final, version.jboss.bom : 8.0.0.Final, version.jboss.as : 8.0.0.Final.
2. Also in the parent POM dependency management you will need to replace the javaee-6.0 BOMs with the WildFly javaee-7.0 equivalents. Replace org.jboss.bom : jboss-javaee-6.0-with-tools : ${version.jboss.bom} : pom [import] with org.wildfly.bom : jboss-javaee-7.0-with-tools : ${version.jboss.bom} : pom [import]. Replace org.jboss.bom : jboss-javaee-6.0-with-hibernate : ${version.jboss.bom} : pom [import] with org.wildfly.bom : jboss-javaee-7.0-with-hibernate : ${version.jboss.bom} : pom [import].
3. In the ejb module POM you will need to modify each of the managed dependencies to use the WildFly javaee-7.0 BOM managed versions. For example replace org.jboss.spec.javax.ejb : jboss-ejb-api_3.1_spec with org.jboss.spec.javax.ejb : jboss-ejb-api_3.2_spec.
4. In the web module POM you will need to modify each of the managed dependencies to use the WildFly javaee-7.0 BOM managed versions. For example replace org.jboss.spec.javax.ws.rs : jboss-jaxrs-api_1.1_spec with org.jboss.resteasy : jaxrs-api.

You may find these links helpful: https://github.com/wildfly/wildfly/blob/master/spec-api/pom.xml, https://github.com/wildfly/boms/tree/master/jboss-javaee-7.0-with-tools, https://github.com/wildfly/boms/tree/master/jboss-javaee-7.0-with-hibernate.

I hope this helps.