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
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 rig
