Hello! What is common way to handle broken builds with Maven2, Release Plugin, Subversion and Maven Repository such as Artifactory or Archiva?
The versioning policy with m2 is defined like : <major><minor><maintenance> - <qualifer> As a consequence, a possible build version sequence could as following: 2.3-alpha-1 2.3-beta-1 2.3-beta-2 2.3-beta-3 2.3-rc-1 2.3 => goes on production 2.3.1 => bugfix release 2.3.2 => bugfix release What shall I do if a build brakes, e.g. 2.3-beta-2? * I can't increment the version to beta-3, because this release is planned with another deadline and content. * A version like 2.3-beta-2.1 doesn't work with current the Implementation of Maven versioning scheme : http://svn.apache.org/viewvc/maven/artifact/trunk/src/main/java/org/apache/maven/artifact/versioning/DefaultArtifactVersion.java?view=markup * If I did a rollback with the release plugin, I could rebuild same version. However, the projects depending on this build wouldn't update to the fixed the build, since maven dependency mecanisme doens't check stable releases for new updates, e.g. on mvn install. Thanks for your feedback and sharing our experiences. Kuno
