You are right, they don't want a special class loader (IDE & compiler problems etc...). But I still think that 'modifying' artifacts is bad practice (it doesn't way up to the above however). How about an e-ejb3.jar with a Class-Path in the manifest that contains all the artifacts (which should be in the same directory)? That should satisfy both IDEs and applications. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3957750#... Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...