title: Eclipse build path / JBoss AS7 Class Loading Exceptions question
body: <p>I'm migrating a JBoss AS5 app to AS7.  I was running into NoClassDefFoundErrors due to AS7's redesigned modular class loading design.  I was following the JBoss developer guide on how to resolve class loading exceptions <a href="https://docs.jboss.org/author/display/AS7/Developer+Guide#DeveloperGuide-Resolveclassloadingexceptionsandothererrors" rel="nofollow">https://docs.jboss.org/author/display/AS7/Developer+Guide#DeveloperGuide-Resolveclassloadingexceptionsandothererrors</a> , which has you doing things such as adding modules as dependencies in your app's MANIFEST.MF file, but I had a lot of trouble with this.  None of my attempts to resolve my class loading errors using MANIFEST.MF or manually copying jars to my app's WEB-INF/lib/ directory seemed to work.</p>
  
  <p>In Eclipse, I tried right clicking on my project and manually adding classes specified by my class loading errors to my project's JAVA BUILD PATH.  I was able to eliminate all of the class loading errors using this method.  My question is - how is Eclipse storing the build path information and making it available to my maven build?  Is it creating a MANIFEST.MF or jboss-deployment-structure.xml somewhere on the file system using the JAVA BUILD PATH information?  I'd like to find whatever file Eclipse is using to store JAVA BUILD PATH so that I can deploy my application without having to manually add dependencies via Eclipse to my JAVA BUILD PATH.  Thanks.</p>