+1

On Mon, 2005-09-26 at 09:22 +1000, Brett Porter wrote:
> Hi,
> 
> I polled on this last week. The general feeling was in favour of Maven
> over Commons. Some reservations about maintaining another library, and
> some proposed alternatives.
> 
> Here is what I propose we do:
> - create https://svn.apache.org/repos/asf/maven/jxr/trunk as an
> independant library, as is
> - give access to all maven plugins developers
> - make m2 and m1 plugins use that to avoid duplicated/lost patches
> - utilise the maven dev list for development
> - create a new JIRA project for it
> - investigate replacement technologies in parallel
> - corbetura and clover generated stuff are things to add as alternatives
> to those plugins, not to a general xref plugin due to licenses
> 
> [ ] +1 - I agree with this plan
> [ ] +0 - I will accept this plan, but still prefer an alternate solution
> [ ] -1 - I disagree with this plan
> 
> Vote closes in 72 hours. Majority rules. Votes by committers are binding.
> 
> Cheers,
> Brett
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
> 
> 
-- 
jvz.

Jason van Zyl
jason at maven.org
http://maven.apache.org

People develop abstractions by generalizing from concrete examples.
Every attempt to determine the correct abstraction on paper without
actually developing a running system is doomed to failure. No one
is that smart. A framework is a resuable design, so you develop it by
looking at the things it is supposed to be a design of. The more examples
you look at, the more general your framework will be.

  -- Ralph Johnson & Don Roberts, Patterns for Evolving Frameworks 


---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to