On Thu, Aug 26, 2010 at 12:39 PM, Rex Hoffman <[email protected]> wrote: > Baptiste: > > I work in a large organization, where there are differing degrees of > familiarity with maven. > Most devs shy away from the release plugin for several reasons. One > is the use of hudson and nexus. >
I actually wrote those rules because we had a client that couldn't use the release plugin for various reasons, but we wanted to encapsulate the best practices contained in the plugin, so this is totally in line with that. > Brian: > > 1) The snapshot detection rules are similar rules, I'll look at them > fully to see what differences exist. I wanted the error messages > given to the user to be the path to each transitive dependency that > was a snapshot (if the artifact was building a release), rather than > suppling one. > Sure, maybe you can just patch the existing rule to your needs and we can apply it. > 2) One of my rules forces every module of a reactor build to have the > same version number as the parent. Rather than only demanding that is > a snapshot or not. > (http://maven.apache.org/enforcer/enforcer-rules/requireReleaseVersion.html) > > 3) There is an extra rule coupled into the first (which it looks like > I should decouple incase the rest of the rule shouldn't make it in > because it is view as being too similar to > http://maven.apache.org/enforcer/enforcer-rules/requireReleaseDeps.html) > which forces developers to resolve transitive dependency version > number conflicts at build rather than letting maven do it. > All transitive dependency conflicts are displayed when the rules > detects that it has been violated. > > Seems like 2 and 3 are unique enough to make it in as rules? > Yes --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
