You may want to take a look at the enforcer plugin and the rules, many
of the release criteria checks are already implemented as enforcer
rules. If you build something that could consume the enforcer rule
api, that would be pretty handy at least for the validation parts of
the release process.
On
Hi *,
We've been trying to build our internal release tools based on maven-release
infrastructure.
We failed when we tried to add new properties to configuration.
Now we are building maven plugin that will feature a bit extended concept of
ReleasePhase
(added dependencies between phases) and pluga
Done.
-Original Message-
From: Paul Gier [mailto:[EMAIL PROTECTED]
Sent: Tuesday, October 23, 2007 3:54 PM
To: Maven Developers List
Cc: Brian E. Fox
Subject: Re: Maven release plugin question
I tested the plugin without the requiresDependencyResolution parameter,
and it
was still able
2, 2007 5:36 PM
To: Maven Developers List
Subject: Maven release plugin question
Hi All,
Does anyone know why the release plugin requires test scope dependency
resolution? I was looking into this issue:
http://jira.codehaus.org/browse/MRELEASE-285
And I found that if I remove this:
@requiresDepen
Maybe they want to check that no test dependencies are snapshots either?
-Original Message-
From: Paul Gier [mailto:[EMAIL PROTECTED]
Sent: Monday, October 22, 2007 5:36 PM
To: Maven Developers List
Subject: Maven release plugin question
Hi All,
Does anyone know why the release plugin
Hi All,
Does anyone know why the release plugin requires test scope dependency
resolution? I was looking into this issue:
http://jira.codehaus.org/browse/MRELEASE-285
And I found that if I remove this:
@requiresDependencyResolution test
The issue is resolved and all of the unit tests still pa
