The EAP 6.1.0 runtime is marked as tech preview in JBDS 6.0.1 and when you create Seam project with this runtime, the EAP libraries won't be present on its classpath. This fact cause following problems, when you try to create new Seam form or reverse engineer entities from database: "The type javax.validation.ConstraintViolation cannot be resolved. It is indirectly referenced from required .class files" "The project was not built since its build path is incomplete. Cannot find the class file for javax.persistence.EntityManager." I think we should recommend to use latest JBDS 7 release with EAP 6.1.0 runtime or JBDS 6.0.1.GA with EAP 6.0.1 runtime.
Tomas, file an issue for JBDS too.
https://issues.jboss.org/browse/JBIDE-14826 created
Updated doc text.
Burr Sutter <bsutter> made a comment on jira WFK2-88 Do we know of this is successful with JBDS 7? Sounds like the best approach is to make sure all parties know to skip JBDS6+EAP6.1 and use JBDS 7 instead.
Marek Novotny <mnovotny> made a comment on jira WFK2-88 [~burrsutter] yes, we know JBDS 7 works fine as the last sentence in Description mentions it. The main issue is changed EAP 6.1.0 module paths and JBDS 6.x doesn't recognize that new module layout.