I need some suggestions for Enterprise build process using Maven. We are currently developing a Java project using Maven. We version controll our project source. Our Continuous integration system syncs the source and uses maven assembly to build a jar with dependencies. This work flow works fine.
Now my manager is uncomfortable with the fact that we don't VC the dependency jars. He is afraid that the entire build workflow will be disrupted if the public repo is down. Of course we could setup an internal repo as an dependency proxy. But my manager is reluctant to do so because we have limited engineer resources for the repo admin. The best solution is to use the company-backed VCS for the dependencies. But I haven't found a good way to incorporate both our VCS and Maven. Can anyone give me some suggestions on this? Thanks. -- View this message in context: http://www.nabble.com/Version-Control-Maven-Dependencies-tp23823014p23823014.html Sent from the Maven - Users mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
