Let it be implemented as tooling which doesn't affect the core and
people will decide what they like to use.
The enforcer plugin addition goes a long way. A simple tool for
creating a block with the latest releases I am making now for a
client. People can compose these tools as they wish to provide they
stability they desire.
On 19 Sep 07, at 6:17 PM 19 Sep 07, Brett Porter wrote:
Hi,
This is the best summary I can get from the discussion earlier this
month about this proposal:
- in terms of having some way to simplify specifying a group of
plugins: 4 in favour, 3 against, 1 on the fence and 2 that wanted a
compromise (a plugin to automate snippet injection)
- in terms of *requiring* versions to be locked down: the poll was
split 50/50. Some said they would only vote for this if there was
some way of doing the above easily.
So it's pretty much split. It's worth nothing there is general
appeal for mixins in a more well-defined form, and that could be
applied to the first.
I'm not pursuing the original proposal at this stage - however I
will revise in the future.
- Brett
--
Brett Porter - [EMAIL PROTECTED]
Blog: http://www.devzuz.org/blogs/bporter/
Thanks,
Jason
----------------------------------------------------------
Jason van Zyl
Founder and PMC Chair, Apache Maven
jason at sonatype dot com
----------------------------------------------------------
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
