On 3/20/07, Torsten Curdt <[EMAIL PROTECTED]> wrote:
> Having fixed the bugs, it seemed to work fine for JMeter, so I thought
> it might be useful for others, and so it was provided as a patch for
> Commons CLI.
>
> Since JMeter has its own copy, it does not matter to us whether the
> CLI copy is
Having fixed the bugs, it seemed to work fine for JMeter, so I thought
it might be useful for others, and so it was provided as a patch for
Commons CLI.
Since JMeter has its own copy, it does not matter to us whether the
CLI copy is ever released, but it seems a shame as it is working well
for us
On 16/03/07, Torsten Curdt <[EMAIL PROTECTED]> wrote:
On 16.03.2007, at 05:28, Henri Yandell wrote:
> On 3/15/07, Torsten Curdt <[EMAIL PROTECTED]> wrote:
>
>> IMO we should do a cli 1.0.1 bug release and get then get 2.0 out of
>> the door ASAP.
>
> Someone needs to have the energy (and compre
On 16.03.2007, at 05:28, Henri Yandell wrote:
On 3/15/07, Torsten Curdt <[EMAIL PROTECTED]> wrote:
IMO we should do a cli 1.0.1 bug release and get then get 2.0 out of
the door ASAP.
Someone needs to have the energy (and comprehension) to push them out.
I get the CLI 1.x code and can do a
On 3/15/07, Torsten Curdt <[EMAIL PROTECTED]> wrote:
IMO we should do a cli 1.0.1 bug release and get then get 2.0 out of
the door ASAP.
Someone needs to have the energy (and comprehension) to push them out.
I get the CLI 1.x code and can do a 1.1 or 1.0.1 release; no one
really seemed to be
While I wrote the commons book I've already stumble across some
parser bugs. I always ended up using our own parser implementation.
Now I am trying to get this
http://svn.apache.org/viewvc/jakarta/commons/sandbox/jci/trunk/
examples/src/main/java/org/apache/commons/jci/examples/commandline/
