[weld-issues] [JBoss JIRA] Commented: (WELD-835) Make sure all examples have instructions for importing and deploying via JBoss Tools.

[ https://issues.jboss.org/browse/WELD-835?page=com.atlassian.jira.plugin.s... ] Dan Allen commented on WELD-835: -------------------------------- Good news. I just discovered this week that by upgrading to hibernate-jpamodelgen 1.1.1.Final none of that Maven plugin configuration trickery is necessary. I guess the Hibernate team figured out how to generate the files into the place that makes all the build environments happy. You can see the simpler build logic in the latest org.jboss.weld.archetypes:jboss-javaee6-webapp (1.0.1.Beta2), available in Maven central or browsable in SVN (http://anonsvn.jboss.org/repos/weld/archetypes/javaee6-webapp/tags/1.0.1....). I consider this archetype to be our "gold standard" Maven project setup for Java EE webapps, atm. I include the following instructions in the readme to workaround a quirk in Eclipse when importing the project generated this way. Additional configuration is required to get Eclipse to generate the JPA metamodel. The archetype includes the necessary Eclipse config files in your project. To enable this feature, right click on the project and select: Properties > Java Compiler > Annotation Processing Check "Enable annotation processing" then click OK and OK again when your are prompted to run a project build. This configuration is described in further detail in the Hibernate JPA documentation: - http://docs.jboss.org/hibernate/stable/jpamodelgen/reference/en-US/html_s... -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira