hey all... so... in jbtools, we of course have the runtime for an as7... and when a user creates a project, we want to know what jars to add to the classpath in previous versions of jboss we just dumped everything and their brother on the project's cp now we're getting too-many-file-handles-open errors, and we need to be more specific over what jars users should expect on their classpath the modules folder has 251 jars... this is clearly too many. Is there a list somewhere of what are client-facing jars? or can anyone explain in simplest terms how to determine if a user-deployed app can access a jar in the modules folder? * alesj has quit (Ping timeout: 276 seconds) stuartdouglas: ^^^ can you help rawbdor rawdor: Do you just want to compile against the APIs or something else? * galderz (~Adium@redhat/jboss/galderz) has joined #jboss-as7 * ChanServ gives voice to galderz * sgilda (~sgilda@cpe-174-097-221-081.nc.res.rr.com) has joined #jboss-as7 * jtaniguc (~jtaniguc@201.22.148.87) has joined #jboss-as7 * sannegrinovero has quit (Ping timeout: 258 seconds) git [jboss-as] push master 332af6c.. jfclere Fix for AS7-921. jira [AS7-921] Booting AS7 on a system without any network connection throws up an error from ModClusterService [Open (Unresolved) Bug, Major, Jean-Frederic Clere] https://issues.jboss.org/browse/AS7-921 git [jboss-as] push master 461514f.. jfclere Improve error message. git [jboss-as] push master URL: http://github.com/jbossas/jboss-as/compare/9f8aa69...461514f * sannegrinovero (~Sanne@redhat/jboss/sannegrinovero) has joined #jboss-as7 * ChanServ gives voice to sannegrinovero * tdiesler has quit (Quit: Leaving.) * asoldano is now known as asoldano_lunch * emuckenhuber (~emuckenhu@redhat/jboss/emuckenhuber) has joined #jboss-as7 * ChanServ gives voice to emuckenhuber * jtaniguc has quit (Quit: Leaving) * hardy_ has quit (Quit: hardy_) * galderz has quit (Quit: Leaving.) * aslak has quit (Remote host closed the connection) * davidbos has quit (Quit: Leaving.) rawbdor: There is currently no list of user facing jars * davidbos (~Adium@109.76.145.183) has joined #jboss-as7 * aslak (~aslak@redhat/jboss/aslak) has joined #jboss-as7 * ChanServ gives voice to aslak The way you can tell what is available is by opening org.jboss.as.server.deployment.Phase in your IDE and having a look at the DEPENDENCIES section all of the entries in that section correspond to a DeploymentUnitProcessor that adds dependencies to the deployment so if you do a 'Find References' on every element there, and have a look at the modules dependencies they add, you can tell what the deployment sees