I update the jbossmc projects to produce a -src.zip artifact that contains just the main java source tree and update the jboss repository to include this: | [starksm@valkyrie build]$ ls -1 /usr/Repository/repository.jboss.com/jboss/microcontainer/snapshot/lib/ | CVS/ | jboss-aop-mc-int-boot.jar | jboss-aop-mc-int-deployer.jar | jboss-aop-mc-int-src.zip | jboss-aop-mc-int.jar | jboss-container-src.zip | jboss-container.jar | jboss-dependency-src.zip | jboss-dependency.jar | jboss-deployers-src.zip | jboss-deployers.jar | jboss-microcontainer-src.zip | jboss-microcontainer.jar | This way I can set the eclipse source attachment for a jar based on the workspace thirdparty location and stop running into conflicts with Kabir who has the mc source elsewhere. The trunk jbossas eclipse project files have been updated to use these source archives for the mc jar source attachments. When you update a snapshot jar make sure you include the corresponding -src.zip as well so the repository stays in synch. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3985969#... Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...