1. Developer enables the access to internal repository(Nexus or other). 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. Maven and Nexus will automatically load new dependencies that need added to internal repository 5. Developer/Administrator/Lawyer valid the new dependencies such as javadoc/sources/license- needs to be done before 2. Why should the developer waste time using invalid libraries. 6. Maven/Nexus deploys new dependencies to internal repository 7. Developer check in projects (pom and sources) and it will work on continuous integration server
On 23/01/2011 6:20 PM, Guo Du 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: [email protected] For additional commands, e-mail: [email protected]
--------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
