&quot;adrian(a)jboss.org&quot; wrote : | It's only referenced by the VFS because the JarStructure is adding it as a | subdeployment. No, that's not the case here. ;-) If you look at the actual JIRA issue, you'll see that Luc has added it to server/some-as-config/lib - as that's how/why conf/jboss-service.xml is able to see it in its classpath - meaning it's referenced via this piece of xml (from jboss-service.xml): | <server> | | <!-- Load all jars from the JBOSS_DIST/server/<config>/lib directory. This | can be restricted to specific jars by specifying them in the archives | attribute. | --> | <classpath codebase="${jboss.server.lib.url:lib}" archives="*"/> | Being added to conf/jboss-service.xml as part of its classpath in SARDeployer::processXMLClasspath. Hence the actual jar is checked/read in some CL impl details, no way to add some flag and ignore it if it's broken. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4182157#... Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...