"alesj" wrote : "adrian(a)jboss.org" wrote : I should also mention that most of these tests are using the AssembledDirectory | | so I can (re-)use the test support classes directly without having to do a packaging step. | | | | Maybe the issue is there? | As you already know, Assembled stuff is pretty slow - I remember your comments when we first used it in Deployers tests. | If you just recently changed this (applying its usage), than this is definitely the culprit. | If you used this before, then I'm out of ideas. :-) But that was building the stuff since the api required you to scan the whole file system with a filter instead of being able to say exactly what you wanted to include. e.g. if I want to include classes in classes/org/foo/bar I has to pass "classes" with a filter "org/foo/bar/*" which scans everything in classes. The runtime stuff shouldn't be slow, i.e. just looking at the constructed tree for the indirections. P.S. The AssembledDirectory also needs some remove() or clear() methods. There is one on AssembledDirectoryHandler but that is a private api. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=4251612#... Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&a...