Jason van Zyl schrieb:
We could even do something like @phase
package,install if you truly think something belongs and has been tested
to run in those phases.
Nice idea, but maybe a dedicated new annotation instead, e.g.
@phase package
@allowed-phases package,install
That would keep the syntax of @phase compatible with 2.x (especially in
the plugin descriptor) and indicates/suggests the default binding, yet
allows to limit the bindings to the supported ones while not being
restricted to merely one phase, eliminating the need for developers to
create almost empty subclasses of a mojo just to declare another phase
binding. If users can present valid use cases for other phases, the mojo
developer could review them and consider their support, possibly
extending the @allowed-phases in a future release. OK, that sounds fair
to me.
Benjamin
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
For additional commands, e-mail: dev-h...@maven.apache.org
