Hi Sander, What's the problem with the standard maven setup? Just don't place the local repository on a network drive, but give each developer it's own local repository... That's what it's for..
Developer A can easily install his new service to his own local repository and run a test build with it as dependency of another module. If the test build turns out to be alright, they can check their code in into scm. Finally, let a CI tool, like continuum, take care of building and deploying the artifacts to the shared repository and/or updating the project website.. These tools always update from scm first before starting a new build.. This way, you don't have to worry about developers deploying unreproducible builds because they did not check in their code into scm.. If you want to split snapshot releases and "real" releases.. define a shared snapshot repository.. I don't see why you would even share the local repository.. If you want isolation of a local development environment, you're better of sticking with the standard maven setup. Good luck.. Jo On 2/24/07, Sander Nieuwenhuizen <[EMAIL PROTECTED]> wrote:
I'm currently busy with migrating ant projects to maven and I stumbled upon the following issue. My team contains of 5 people and we're developing using a component-based architecture. Let's take the following example to illustrate my question. We've got a service project, named CommonServices, and a web project, say MyWebProject. We develop in parallel on separate functionality. Developer A wants to add a new Service (serviceA) to the service project. In the mean time, developer B wants to add a serviceB. The two services aren't dependent on each other. Both developers have ofcourse unit tested their own code and next... they want to finally test it via the web project before checking the service code in to scm. The local repository is set up on a network drive, so each developer is using the exact same repository. How can we setup maven to fully isolate the two development paths? Snapshot jars are installed on the shared repository, which would mean the two developers would interfere with each other. For example, I would like to be able to set up a separate repository with full isolation for each developer. How can I create such an environment? -- View this message in context: http://www.nabble.com/Multiple-developer-dependency-management-tf3284959s177.html#a9137608 Sent from the Maven - Users mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
