2010/9/20 Perez Ronen <[email protected]> > Hi All, > > I am in a process of pushing Maven in my organization and I have a > methodology question. > Up until now (before Maven), in most R&D teams, the development was broken > into builds. If, for example we have a module called "my-module" with > version 4.7.1.0, each build produced a jar will the following method: > My-module-4.7.1.0-01 (for build number 1) > My-module-4.7.1.0-02 (for build number 2) > And so on... > > Now, when the module is built with Maven, each time the team deploy the > module to Maven repository (release type), there is a new release version. > I think, the better way is to use SNAPSHOT version during development, so > that all artifacts are under the same version umbrella. The problem is that > the teams want to have a significant artifact for each build, something that > says: this artifact is of build number 6... > > > 1) Do you agree with me that the SNAPSHOT way is better? >
During development, definitely. Since this is a core maven feature : snapshot are designed to be updated, although releases aren't and so on. Snapshots are dev versions by definition. > 2) Can you give your reasons of why this is better? > Well, with maven, when you deploy to your maven repository manager, you'll see SNAPSHOT suffices are replaced by timestamps, so you actually have a real usable war/jar/pom for each build. Knowing what you need precisely is more dependent of your company organization. -- Baptiste <Batmat> MATHUS - http://batmat.net Sauvez un arbre, Mangez un castor !
