hi
I would choose a different path - assuming you have a master pom that all
development groups inherit from, you can configure a custom plugin there
that performs the validation, and bind it to one of the predefined phase in
the release plugin's lifecycle. The appropriate phase I think would be
"check-poms"
so, you would add this to your master POM:
<build>
<plugins>
<plugin>
<groupId>myplugingroup</groupId>
<artifactId>custom-release-maven-plugin</artifactId>
<executions>
<execution>
<phase>check-poms</phase>
<goals>
<!-- here you should list your plugin's mojo(s)
you want to run -->
<goal>validate-version-format</goal>
</goals>
</execution>
</executions>
</plugin>
</plugins>
</build>
hope this helps...
Arik.
On 5/2/06, David Jackman <[EMAIL PROTECTED]> wrote:
I've asked this question before long ago but got no real answer.
Hopefully things have settled enough that there is something to say
about doing this sort of thing.
I'd like to essentially build a custom plugin that wraps the goals of an
existing plugin. The specific use case I'm thinking of right now is a
custom release plugin for use within our development group that will
enforce our own internal naming and other standards. So, my plugin will
verify that the version value is of the correct form, then automatically
generate a SCM tag name for that version, then call the release:prepare
goal to actually do the work. There are other example use cases for
other "wrapper" plugins, but this is the easiest to explain.
Is this sort of thing possible for a plugin to do?
..David..
--
______________________________________
Cheers,
Arik Kfir [EMAIL PROTECTED]
Linux user, number 415067 - http://counter.li.org/
http://corleon.dnsalias.org
