I couldn't think of a situation where you would be looking at the jar outside of its jboss directory. If other projects are using jboss common for example, they could specify the dependency in their pom.xml and the jar gets downloaded into their local repository, and they never see it. If we are packaging up jboss common with the app server for example, there is a maven assembly plugin that can be used to package a project with its dependencies, so you would never have to worry about the actual name of the jboss common jar file. One situation where it probably would be useful to have the full name jboss-common-core.jar is for external non-maven projects that want to just extract the jars into their lib directory. But for this case we could produce a different name for the file (including the groupId) for non maven distribution. View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4010111#... Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...