"max.andersen(a)jboss.com" wrote : | Scanning for all .xml is very arbitrary and if the API is built for each deployer to say which files should trigger deployment why don't we get the right deployers to implement the specific rules instead of having a global one ? (or did I misunderstand how it is structured today?) | With the JBDEPLOY-210 fix this is now trivial to do - JarStructure already in-callbacks all FileMatchers. And currently only FileMatcher impls are parsing deployers - exactly what we need. So, this, your wanted feature, will be part of next Deployers release. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4249882#... Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&a...