[jbosstools-issues] [JBoss JIRA] (JBIDE-11233) Dependencies' versions missing when creating Richfaces Project with EAP 6.0.0.ER3

[ https://issues.jboss.org/browse/JBIDE-11233?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen commented on JBIDE-11233: --------------------------------------------- hmm - shouldn't those get included when using the javae6 BOM the other archetypes and most quickstarts uses ? i.e.: <javaee6.web.spec.version>2.0.0.Final</javaee6.web.spec.version> <!-- Alternatively, comment out the above line, and un-comment the line below to use version 3.0.0.Beta1-redhat-1 which is a release certified to work with JBoss EAP 6. It requires you have access to the JBoss EAP 6 maven repository. --> <!-- <javaee6.web.spec.version>3.0.0.Beta1-redhat-1</javaee6.web.spec.version> --> </properties> <dependencyManagement> <dependencies> <!-- JBoss distributes a complete set of Java EE 6 APIs including a Bill of Materials (BOM). A BOM specifies the versions of a "stack" (or a collection) of artifacts. We use this here so that we always get the correct versions of artifacts. Here we use the jboss-javaee-web-6.0 stack (you can read this as the JBoss stack of the Java EE Web Profile 6 APIs) --> <dependency> <groupId>org.jboss.spec</groupId> <artifactId>jboss-javaee-web-6.0</artifactId> <version>${javaee6.web.spec.version}</version> <type>pom</type> <scope>import</scope> </dependency> </dependencies> </dependencyManagement> -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira