[ https://issues.jboss.org/browse/JBDS-2802?page=com.atlassian.jira.plugin.... ] Joshua Wilson commented on JBDS-2802: ------------------------------------- [~nickboldt] and [~mlabuda] please allow me to introduce myself. My name is Joshua and I am [~marius.bogoevici] replacement. I am working as the Snowdrop lead, integrating Spring with JBoss. I have been working to update the Spring Archetype and several [Spring Quickstarts|https://github.com/jboss-developer/jboss-wfk-quickstarts]. I am trying to resolve the errors that I am finding in JDBS/Eclipse. I think I can explain some of what you have seen or at least try to bring clarity in reproducing the errors. I would say that the Quickstarts provide some good test "examples" for you too. ERRORs: The error in jboss-deployment-structure.xml is based on the xsd being improperly written. There are several Jira's written on it but WFLY-943 best describes it and the solution. So this is one we just need to live with for now. (If you don't build with Eclipse then most of the errors don't appear, but what fun is that. So in order to see the following errors you need to Build.) The "Build path is incomplete. Cannot find class file for org/aspect/weave" error only appears in the JBDS version with the Spring IDE installed. If you switch to an Eclipse install that has both JBoss and Spring IDE installed and then build, these errors go away. From what I have found is might have to do with the AspectJ Compiler and AspectJ Development Tools not being installed in the JDBS version of the Spring IDE. The "Build path is incomplete. Cannot find class file for javax/servlet/ServletContext" error appears to me to be an m2e issue though I am not entirely sure. I do know that if I "Add External JARs" to the "Java Build Path" and select the modules/system/layers/base/javax/servlet/api/main/jboss-servlet-api_3.0_spec-1.0.2.Final-redhat-1.jar it fixes this error. I do think this is just a work around. The reason that I think this is an m2e issue is that any project with this error builds fine on the CLI because the jar is supplied by the BOM. If you look at the Effective Pom tab of the pom.xml you will find the servlet jar present. Alternatively this can be fixed by adding the servlet jar listed in the BOM that you find in the Effective Pom tab. But that means editing the actual project to fix an IDE based error. If there is anything else I can do to help, please let me know. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira