The VFSUtils.addManifestLocations logic is not working for nested jars because of how URL(URL context, String spec) behaves. If context is a directory (ending in '/') then spec is a child. If context does not end in a '/' however, spec is resolved as a peer to context. It looks like either this was never working, or we had jars ending in '/'. I think the latter was the case. Anyway, I have this working for one test, but need to go over the other manifest tests as it looks like the nested artifacts used don't have the correct structure for the manifest classpaths trying to be tested. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4123307#... Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...