I'm currently trying to understand how to get maven to "behave" correctly when using nightly build artifacts. We have a very large project using clearcase as our scm. We have a "nightly build" repository that we setup as an external maven repository. That way, the developer does not have to build "the world" to work on a small piece... maven will pull down all the nightly build artifacts (as well as external dependencies) into the developer's local repository. However, there are two tenents to this system that I can't figure out.
1. When the nightly build gets new content, maven should go and pull down the new jars. I think SNAPSHOT could help us here, but I don't think without each developer modifying every pom.xml file in the system. 2. If the user builds something in their own view, it takes precedence over anything in the nightly build (even if the nightly build has newer content). What I think I want to try to setup is tell maven there are two local repositories... and the user's local is first in the CLASSPATH, followed by the local "nightly build" which could be setup using sym links to elements depending on the type of view the developer wants (release based or nightly based). External/Remote dependencies are downloaded into in the user's local, as well as any artifacts the developer builds in the view. And since the CLASSPATH has two repositories, if maven can't find an object in the first, it looks to the nightly build. Can a system like this be configured? Or am I looking at modifying maven's code directly for something like this? Thanks for any thoughts you may have! Mark
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
