Re: cvs commit: avalon-phoenix/src/java/org/apache/avalon/phoenix/frontends CLISetup.java

Steve, vetoes are _not_ how we want to work things out. This is *not* 
productive (see my earlier mail about my view of productivity). Please 
reconsider throwing more annoying vetoes into the party about stuff 
which has not been aptly discussed.

Here's how development works: we interpret were we're moving as a 
project and what we need as a project, and act based on that. If we're 
not sure everyone agrees with those acts, we draft a proposal before 
committing stuff. When we are, we just commit, and things are subject to 
lazy consensus.

If we shouldn't have been sure because there isn't in fact a consensus, 
the thing to do is to bring the actions and commits up for discussion. 
*Not* just throw a veto out without discussion. Vetoes make it more 
difficult to build consensus, and consensus is what we like.

Why don't you retract your veto, take a look at Eung-ju's patch, rework 
it to be fully compliant with the existing phoenix cli options, and 
propose the modified patch as a replacement. Everybody happy.

vetoes -- bleh.

- Leo

Stephen McConnell wrote:
> 
> -1 (veto)
> 
>> donaldp     2003/03/12 05:01:38
>>
>>  Modified:    .        build.xml
>>               src/java/org/apache/avalon/phoenix/frontends CLISetup.java
>>  Removed:     lib/container excalibur-cli-1.0.jar
>>  Log:
>>  Remove away from excalibur-cli which has been axed.