"scott.stark(a)jboss.org" wrote : So let's get the first step of never looking to external repositories. Is this something that can be enforced at the project pom level, or does the user settings always allow for an override of the repo? | The central maven repo is defined in the super pom that all poms inherit from. This repository can be disabled or overridden by defining a repository with the id "central" in your pom. I can change the jboss-parent pom so that the central repository is not used when performing a release. I would prefer to still allow the central repository during development builds, because this will allow us to download dependencies using the dependency plugin . The copy-dependencies goal can be used to copy all required dependencies for a project to a location on the file system. For example, a local checkout of the cvs repository. I would like to have a separate thirdparty repository for this, because we might want the behaviour to be different between the jboss releases repo and the thirdparty repo, but for now we can just check in deps to the current repository (repository.jboss.org). Does this sound ok? View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4032898#... Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...