[Fwd: cvs commit: avalon-phoenix/src/java/org/apache/avalon/phoenix/frontends CLISetup.java]

I though the reason for "compatting" excalibur-cli was that we wish to 
support a common cli package, namely commons-cli. If moving away from 
excalibur-cli is just going to result in us importing the exact same 
stuff from another project, what's the point?

cheers,

- Leo

-------- Original Message --------
Subject: cvs commit: 
avalon-phoenix/src/java/org/apache/avalon/phoenix/frontends CLISetup.java
Date: 12 Mar 2003 13:01:38 -0000
From: [email protected]
Reply-To: Avalon Developers List <[email protected]>
Newsgroups: gmane.comp.jakarta.avalon.cvs

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.

<snip/>

    import java.util.List;
   -import org.apache.avalon.excalibur.cli.CLArgsParser;
   -import org.apache.avalon.excalibur.cli.CLOption;
   -import org.apache.avalon.excalibur.cli.CLOptionDescriptor;
   -import org.apache.avalon.excalibur.cli.CLUtil;
    import org.apache.avalon.excalibur.i18n.ResourceManager;
    import org.apache.avalon.excalibur.i18n.Resources;
    import org.apache.avalon.framework.parameters.Parameters;
    import org.apache.avalon.phoenix.interfaces.SystemManager;
   +import org.realityforge.cli.CLArgsParser;
   +import org.realityforge.cli.CLOption;
   +import org.realityforge.cli.CLOptionDescriptor;
   +import org.realityforge.cli.CLUtil;