You could be somewhat aided by the procurement feature of Nexus Pro (the commercial edition of the Nexus repo manager): http://www.sonatype.com/books/nexus-book/reference/procure.html
Also, One thing that you might want to have in mind is two have separate repositories for dependencies and plugins. For Maven to be useful, you will need quite a few plugins. These plugins have lots of dependencies which you simply just must allow. If you use Maven 3, plugins and their dependendencies can have separate repos from your projects' dependencies. This does not work in Maven 2.x. /Anders On Mon, Jan 24, 2011 at 00:20, Guo Du <mrdu...@duguo.org> wrote: > In a commercial software development environment, production code will > rely on artifacts which may come from public domain such as maven > central repository. For those artifacts from external, would be > validated with some process such as > checksum/javadoc/sources/license/lawyer, once passed those check, then > deployed to internal maven repository to build into product. Internal > repository is isolated from external repository for various reason. > > A typical work flow will be: > 1. Developer enable the access to external repository. > 2. Developer add new dependencies as artifacts/plugins which available > from external repository. > 3. Developer test the new pom setup and it works on local machine > 4. Developer in some how figure out all (hundreds) new dependencies > need added to internal repository > 5. Developer/Administrator/Lawyer valid the new dependencies such as > javadoc/sources/license > 6. Developer/Administrator deploy new dependencies to internal repository > 7. Developer check in projects pom and it will works on continuous > integration server which only have access to internal repository. > > Any question on the work flow? > Is this work flow could be easily supported? (with open > source/commercial repository manager) > > Thanks! > > -Guo > > --------------------------------------------------------------------- > To unsubscribe, e-mail: users-unsubscr...@maven.apache.org > For additional commands, e-mail: users-h...@maven.apache.org > >
