Thank you Brian, The way we currently prevent developers from deploying their local builds to the repo are the security permissions. But I have understood, that some kind of a repo-managing system should be used for more flexibility.
Regarding snapshots and the way your QA works it all looks like you have adjusted your team workflow to the features the maven tool provides. And these features are not so flexible to cover all requirements of ISO driven development for instance. For example, need to distinguish and be able to recreate everything that gets officially built. If you say, that in this case we need to do only releases, then we don't need snapshots at all and would loose an option to use different repos for different build types. As I mentioned already, versions-maven-plugin can't update project's version (only dependencies, if I didn't miss something in the online description). Best Regards, Sergey Shcherbakov. -----Original Message----- From: Brian Fox [mailto:[email protected]] Sent: Tuesday, April 07, 2009 11:16 PM To: Maven Users List Cc: Guillaume Goulet; Kevin Coupland; Kyle Blaney Subject: RE: Understanding SNAPSHOTS >1. How to distinguish snapshot build versions correctly? So that one >snapshot build would not overwrite previous one in the repository. You don't, that's not the purpose. If you truly care about a particular snapshot version, then it should have been a release. It's meant only for looking at the latest version of unreleased code. >2. How to set up correctly CI server to perform nightly and release >builds not using maven SCM plug-ins (since our CI system has far richer >functionality in this field). This is a bit trickier but there are some plugins available in Hudson to do this. We don't provide nightly releases, that's too much overhead. With the staging support, we are able to manage this directly from Maven on an intentional release basis...that is we decide when a release is ready and use the release plugin to do this. The CI is only producing snapshots on a constant basis. >3. When a developer starts a build on his own machine which version >should he use? There is always a risk that he will destroy an artifact >in the repository. Not if you setup the permissions correctly, and especially not with staging support. Each build from a developer would go into their own staging repo created on the fly. It's impossible to accidentally release directly to your repo with this setup. >4. How to perform automatic pom project version update? I am not talking >about updating dependency versions to the "latest version". I want to >have a build version passed from the CI server automatically in the pom >file in the repository. At the moment the recommended way is to update >it manually, as I understand. I do it manually, but there are tools like the versions-maven-plugin that can assist you. --------------------------------------------------------------------- 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]
