It reports that it is a issue in DefaultParser but the same issue can be
seen in Basic Parser which is a depreciated class. Should it be considered
as a issue?
Thank You
line parameters. I came up with a functional solution that
seemed to be pretty flexible. So I extracted the code into a separate
repository [1] and enhanced it.
It is now in a shape that it supports a lot of the features typical to a
CLI library. The functional programming (FP) approach is probably
Hi,
I have downloaded and edited Commons CLI. It works fine after some
configuring in Eclipse. Building from the command line, however, fails,
both with Ant and with Maven.
Ok, that is not entirely true: ant dist works in that it produces a jar,
but:
junit-present:
[echo
Emmanuel Bourg a écrit :
I'm going to convert the Avalon CLI test case to the Commons CLI API to
see what features are missing. I'll see if these features can be
implemented in CLI. So maybe we'll have a "common" API at last.
I completed the conversion of the Avalon
Emmanuel Bourg wrote:
> Emmanuel Bourg a écrit :
>
>> I'm going to convert the Avalon CLI test case to the Commons CLI API to
>> see what features are missing. I'll see if these features can be
>> implemented in CLI. So maybe we'll have a "common"
thing for the
short options, if the argument is optional it must be grouped with the
option (-O1 and not -O 1).
So Avalon CLI is right. The catch now if we implement this is to decide
how multiple optional arguments are handled. I guess this would make the
value separator mandatory:
--fo
la, I needed some limited functionality to process
>
> command line parameters. I came up with a functional solution that
>
> seemed to be pretty flexible. So I extracted the code into a separate
>
> repository [1] and enhanced it.
>
>
>
> It is now in a shape tha
repository [1] and enhanced it.
>
> It is now in a shape that it supports a lot of the features typical to a
> CLI library. The functional programming (FP) approach is probably
> somewhat special: you define extractors using a DSL, which are actually
> monads and thus can be ni
pports a lot of the features typical to a
> CLI library. The functional programming (FP) approach is probably
> somewhat special: you define extractors using a DSL, which are actually
> monads and thus can be nicely transformed and composed to more complex
> structures. The end product
tracted the code into a separate
>> repository [1] and enhanced it.
>>
>> It is now in a shape that it supports a lot of the features typical to a
>> CLI library. The functional programming (FP) approach is probably
>> somewhat special: you define extractors using a DSL,
+1, think it makes sense to widen the community/ecosystem to JVM languages
(which actually use java libs a lot) with their "idoms" and types support.
I also think it applies to Java BTW we should support in version >= 1.5
with annotation support which is used in 90% of cli libs toda
I'm preparing the release for CLI 1.2, I have uploaded the files and the
site on people.apache.org. If this looks good I'll roll out a formal RC1.
http://people.apache.org/~ebourg/cli-1.2
http://people.apache.org/~ebourg/cli-1.2/site
The plan is to let the RC run at least one mo
Hi Hendrik,
Hendrik Maryns wrote:
> Hi,
>
> I have downloaded and edited Commons CLI. It works fine after some
> configuring in Eclipse. Building from the command line,
> however, fails,
> both with Ant and with Maven.
>
> Ok, that is not entirely true: ant dist works
Jörg Schaible schreef:
> Hi Hendrik,
>
> Hendrik Maryns wrote:
>> Hi,
>>
>> I have downloaded and edited Commons CLI. It works fine after some
>> configuring in Eclipse. Building from the command line,
>> however, fails,
>> both with Ant and wi
Jörg Schaible schrieb:
Hi Hendrik,
Hendrik Maryns wrote:
Hi,
I have downloaded and edited Commons CLI. It works fine after some
configuring in Eclipse. Building from the command line,
however, fails,
both with Ant and with Maven.
Ok, that is not entirely true: ant dist works in that it
Simon Kitching schreef:
> Jörg Schaible schrieb:
>> Hi Hendrik,
>>
>> Hendrik Maryns wrote:
>>
>>> Hi,
>>>
>>> I have downloaded and edited Commons CLI. It works fine after some
>>> configuring in Eclipse. Building from the com
On Fri, 17 Oct 2008, Hendrik Maryns <[EMAIL PROTECTED]> wrote:
>> ant -diagnostics
> --- Ant diagnostics report ---
> Apache Ant version 1.7.0 compiled on June 7 2008
>
> ---
> Implementation Version
> ---
>
Hendrik Maryns a écrit :
I guess I’ll update the README file for a starters, and I hope some
other CLI developers are reading this, so that this can be fixed.
Done, I removed the old Maven 1 files and updated the README. I fixed
also some test errors with Maven 2.
Emmanuel Bourg
Stefan Bodewig schreef:
> On Fri, 17 Oct 2008, Hendrik Maryns <[EMAIL PROTECTED]> wrote:
>
>>> ant -diagnostics
>> --- Ant diagnostics report ---
>> Apache Ant version 1.7.0 compiled on June 7 2008
>>
>> ---
>> Implementation Version
>>
Emmanuel Bourg schreef:
> Hendrik Maryns a écrit :
>
>> I guess I’ll update the README file for a starters, and I hope some
>> other CLI developers are reading this, so that this can be fixed.
>
> Done, I removed the old Maven 1 files and updated the README. I fixed
>
Hi,
I’d like to have feedback for CLI-277 [1], especially whether it will affect
BC. Clirr is happy with this changes, to I suppose it is fine to merge this?
Thank you,
Benedikt
[1] https://github.com/apache/commons-cli/pull/13
<https://github.com/apache/commons-cli/pull/13>
On Jun 14, 2017 4:28 AM, "Benedikt Ritter" wrote:
I’d like to have feedback for CLI-277 [1], especially whether it will
affect BC. Clirr is happy with this changes, to I suppose it is fine to
merge this?
[1] https://github.com/apache/commons-cli/pull/13 <
https://github.com/apach
Hi cli dev team,
I recently upgraded to the commons-cli version 1.3.1 where the BasicParser is
deprecated. So if I sue the DefaultParser instead, my following sample code
would not work -
public static void main(String[] args) throws Exception {
Options options = getOptions
e pretty flexible. So I extracted the code into a separate
> > repository [1] and enhanced it.
> >
> > It is now in a shape that it supports a lot of the features typical to a
> > CLI library. The functional programming (FP) approach is probably
> > somewhat specia
In the DefaultParser class, we are using handleOption method which is defined
as following
privatevoidhandleOption(Optionoption)throwsParseException{
// check the previous option before handling the next one
checkRequiredArgs();
option=(Option)option.clone();
updateRequiredOptions(option);
c
Hi all guys,
I have been experimenting a new set of CLI APIs outside the ASF,
taking the best from existing CLI and some other non-ASF libraries,
mainly Cédric's JCommander[1], the purposes are:
* using fluent APIs;
* simplify the Options building;
* reducing the number of involved compo
On Wed, Jul 30, 2008 at 6:09 PM, Emmanuel Bourg <[EMAIL PROTECTED]> wrote:
> I'm preparing the release for CLI 1.2, I have uploaded the files and the
> site on people.apache.org. If this looks good I'll roll out a formal RC1.
I think its worth highlighting to people that the
10 AM
To: Jakarta Commons Developers List
Subject: [cli] CLI 1.2 Release preparation
I'm preparing the release for CLI 1.2, I have uploaded the files and the
site on people.apache.org. If this looks good I'll roll out a formal RC1.
http://people.apache.org/~ebourg/cli-1.2
http://people.apac
ache.org/~ebourg/cli-1.2/site/release_1_2.html
http://people.apache.org/~ebourg/cli-1.2/site/changes-report.html
I tend to avoid the verbatim bug lists, I don't find them very descriptive.
Emmanuel Bourg
-
To unsubscribe, e
Niall Pemberton a écrit :
I think its worth highlighting to people that the OptionValidator
class has changed from public to package scope:
http://people.apache.org/~ebourg/cli-1.2/site-1.2/clirr-report.html
Looking at why you did this, seems OK to me:
http://svn.apache.org/viewvc?view
Niall Pemberton wrote:
On Wed, Jul 30, 2008 at 6:09 PM, Emmanuel Bourg <[EMAIL PROTECTED]> wrote:
I'm preparing the release for CLI 1.2, I have uploaded the files and the
site on people.apache.org. If this looks good I'll roll out a formal RC1.
I think its worth highlightin
Dennis Lundberg a écrit :
I'm using Maven 2.0.8, Sun 1.4.2 JDK on Windows XP Pro.
What are you using?
I have Maven 2.0.9, Sun JDK 1.4.2_17 and Windows XP SP3
Emmanuel Bourg
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For ad
Emmanuel Bourg wrote:
Dennis Lundberg a écrit :
I'm using Maven 2.0.8, Sun 1.4.2 JDK on Windows XP Pro.
What are you using?
I have Maven 2.0.9, Sun JDK 1.4.2_17 and Windows XP SP3
Thanks, I tried with 2.0.9 as well, and it works for me...
I'm running this command:
mvn clean assembly:ass
Dennis Lundberg a écrit :
Thanks, I tried with 2.0.9 as well, and it works for me...
I'm running this command:
mvn clean assembly:assembly
and the path in the source zip/tar has the correct version.
mvn assembly:assembly works for me too, but the binary package is
incomplete (no javadoc)
Emmanuel Bourg wrote:
Dennis Lundberg a écrit :
Thanks, I tried with 2.0.9 as well, and it works for me...
I'm running this command:
mvn clean assembly:assembly
and the path in the source zip/tar has the correct version.
mvn assembly:assembly works for me too, but the binary package is
I saw from the following blog[1] that Hadoop is using CLI
2.0-SNAPSHOT, but they're considering rolling back (HADOOP-3676[2])
because of the uncertainty wrt CLI 2.0. Seems the most recent
discussion was inconclusive:
http://markmail.org/message/ssh3mgwngpr4m5jz
I guess the lack of decisi
Hello all,
we have this [1] bug report from the Groovy project. Apparently, [cli] will
remove the quotes from the following command line:
-f "test"
This goes back to CLI-22 and CLI-185. I have no idea what the problem of
the original reporter was, but my feeling is, that we shoul
Oops -I missed that the method was already generic. Need bigger tablet/more
coffee / bigger caffeine tablet
On Jun 14, 2017 8:46 AM, "Simon Spero" wrote:
On Jun 14, 2017 4:28 AM, "Benedikt Ritter" wrote:
I’d like to have feedback for CLI-277 [1], especially whether it will
ot; wrote:
>
> On Jun 14, 2017 4:28 AM, "Benedikt Ritter" wrote:
>
> I’d like to have feedback for CLI-277 [1], especially whether it will
> affect BC. Clirr is happy with this changes, to I suppose it is fine to
> merge this?
>
> [1] https://github.com/apache/commons
Hi,
Two similar but different approaches for solving
https://issues.apache.org/jira/browse/CLI-224 have been posted. I was
hoping to encourage some discussion on which approach (if any) is
preferred?
In particular, if either patch is worth pursuing, I can foresee some
other useful work to
Hello,
It would be helpful to understand the upshot of this if you could express
your explanation as a failing unit test.
TY,
Gary
On Sat, Aug 12, 2023, 1:44 AM Sruteesh Kumar
wrote:
> In the DefaultParser class, we are using handleOption method which is
> defined as following
>
> privatevoidh
Hi Gary, the unit test is already provided as a comment in the JIRA issue
CLI-317. Go through the following link for the same
https://issues.apache.org/jira/projects/CLI/issues/CLI-317?filter=allopenissues
--- Original Message ---
On Sunday, August 13th, 2023 at 5:51 PM, Gary Gregory
Hi,
Please see my comment in the ticket.
Gary
On Sun, Aug 13, 2023, 9:04 AM Sruteesh Kumar
wrote:
>
> Hi Gary, the unit test is already provided as a comment in the JIRA issue
> CLI-317. Go through the following link for the same
>
>
> https://issues.apache.org/jira/proje
> Hi Gary, the unit test is already provided as a
> comment in the JIRA issue > CLI-317. Go through the following link for the
> same > > >
> https://issues.apache.org/jira/projects/CLI/issues/CLI-317?filter=allopenissues
> > > > --- Original Message ---
am, Gary Gregory wrote:
>
> > Hi, Please see my comment in the ticket. Gary On Sun, Aug 13, 2023, 9:04
> AM Sruteesh Kumar wrote: > > Hi Gary, the unit test is already provided as
> a comment in the JIRA issue > CLI-317. Go through the following link for
> the same > &g
Hi Simone,
I don't know how others make use of CLI, what I'm going to discuss is only
my personal point of view.
I have to do with the command line stuff one time per project (more or
less), and I have to admit that the CLI api (even though is a good one) is
every time hard to appl
ill far away in terms
> of learning curve.
UH... Seriously? Being fluent-APIs should be at least easier of
current [cli] APIs...
Thanks for the feedbacks!
-Simo
http://people.apache.org/~simonetripodi/
http://simonetripodi.livejournal.com/
http://twitter.com/simone
On Sat, 2008-07-12 at 16:02 +0100, Niall Pemberton wrote:
> I saw from the following blog[1] that Hadoop is using CLI
> 2.0-SNAPSHOT, but they're considering rolling back (HADOOP-3676[2])
> because of the uncertainty wrt CLI 2.0. Seems the most recent
> discussion was inconc
On Sat, Jul 12, 2008 at 9:12 AM, Russel Winder
<[EMAIL PROTECTED]> wrote:
> On Sat, 2008-07-12 at 16:02 +0100, Niall Pemberton wrote:
>> I saw from the following blog[1] that Hadoop is using CLI
>> 2.0-SNAPSHOT, but they're considering rolling back (HADOOP-3676[2])
>
On Sat, 2008-07-12 at 15:34 -0700, Henri Yandell wrote:
> Looks like a 1.2 is ready to release. At least there are no open
> issues related to 1.x.
CLI-147 is still open and marked as to be fixed in 1.2.0.
CLI-137 has been marked as fixed, but I am not convinced it is -- but I
am basing t
Henri Yandell schrieb:
On Sat, Jul 12, 2008 at 9:12 AM, Russel Winder
<[EMAIL PROTECTED]> wrote:
On Sat, 2008-07-12 at 16:02 +0100, Niall Pemberton wrote:
I saw from the following blog[1] that Hadoop is using CLI
2.0-SNAPSHOT, but they're considering rolling back (HADOOP-3676[2])
t; > > I saw from the following blog[1] that Hadoop is using CLI
> > > > 2.0-SNAPSHOT, but they're considering rolling back (HADOOP-3676[2])
> > > > because of the uncertainty wrt CLI 2.0. Seems the most recent
> > > > discussion was inconclusive:
>
Tobias Bocanegra wrote:
On 7/13/08, Oliver Heger <[EMAIL PROTECTED]> wrote:
Henri Yandell schrieb:
On Sat, Jul 12, 2008 at 9:12 AM, Russel Winder
<[EMAIL PROTECTED]> wrote:
On Sat, 2008-07-12 at 16:02 +0100, Niall Pemberton wrote:
I saw from the following blog[1] that Hadoop
Russel Winder wrote:
On Sat, 2008-07-12 at 16:02 +0100, Niall Pemberton wrote:
I saw from the following blog[1] that Hadoop is using CLI
2.0-SNAPSHOT, but they're considering rolling back (HADOOP-3676[2])
because of the uncertainty wrt CLI 2.0. Seems the most recent
discussion was inconcl
Henri Yandell a écrit :
Looks like a 1.2 is ready to release. At least there are no open
issues related to 1.x.
I agree, at this point we need more feedback on the changes applied
recently from the main projects using CLI. The documentation
improvements would be great but that should not
og[1] that Hadoop is using CLI
2.0-SNAPSHOT, but they're considering rolling back (HADOOP-3676[2])
because of the uncertainty wrt CLI 2.0. Seems the most recent
discussion was inconclusive:
http://markmail.org/message/ssh3mgwngpr4m5jz
I guess the lack of decision on 2.0 is/was caused by lack of pe
On Thu, 2008-07-17 at 19:43 +0200, Emmanuel Bourg wrote:
> I wouldn't push for a 2.0 release in the current state, I'm not
> convinced by the design of the new API. It seems more reasonable to
> stabilize the 1.x branch before considering a major refactoring with CLI2.
Given that there is no rus
llowing blog[1] that Hadoop is using CLI
2.0-SNAPSHOT, but they're considering rolling back (HADOOP-3676[2])
because of the uncertainty wrt CLI 2.0. Seems the most recent
discussion was inconclusive:
http://markmail.org/message/ssh3mgwngpr4m5jz
I guess the lack of decision on 2.0 is/was caused by
if the option is "hasArgs" (if it is "hasArg" then
the argument isn't broken on the separator). Changing hasArgs() to
hasArg() in ApplicationTest.java demonstrates this problem
I checked ApplicationTest.testAnt() from the CLI 1.0 tag and the
behavior is the same. The tes
Russel Winder a écrit :
As far as I can see changing from 1.0 to 1.2-SNAPSHOT does not cause any
problem for the Groovy build and test. However, it seems that no unit
tests were added for the problems raised by 1.1 so I cannot present
evidence that 1.2 solves the problems. What I can say is th
Emmanuel,
Is there a way of triggering the CLI 1.2 release process? Given that
there are significant changes over 1.1 and the idea of a 1.3 is not
rejected, I think moving to a 1.2 release sooner rather than later would
be useful. The only threat I can see is if 1.2 has the same blocking
errors
I'll start preparing a release soon. The current state is good enough
for a release, the remaining issues can be postponed to CLI 1.3.
I'd like to release a "long lived" release candidate (at least 2-3
weeks) before pushing the final release. This will let some time to the
Emmanuel,
On Fri, 2008-07-25 at 14:41 +0200, Emmanuel Bourg wrote:
> I'll start preparing a release soon. The current state is good enough
> for a release, the remaining issues can be postponed to CLI 1.3.
I agree, but I don't think I qualify for a vote :-)
> I'd like
Hello,
yesterday i was doing some work with commons-cli and stumbled across
getParsedOptionValue in the CommandLine class.
Being new to this library i was very confused to always get a null value
instead of some string. The problem was that i didn't set the type in my
Option objects.
I
Last year there was a lot of effort trying to get Commons CLI into a fit
state for a 1.2 release -- much credit to Emmanuel Bourg.
However, having got the Subversion 1.x branch of Commons CLI into a fit
state for a 1.2 release, nothing seems to have happened. This is a
great shame -- 1.2
Hi All:
In my old code, I use [cli]. In my new code I use JCommander (also under
the Apache 2 license).
[cli] really feels antiquated.
I'd the community's thoughts on moving to a cli2 that uses annotations, or
possibly asking JCommander to join us here.
Gary
--
E-Mail: garydgreg...
Currently the main package name for Commons CLI 2.x is:
org.apache.commons.cli2
Is there actually a need for a change of package name from:
org.apache.commons.cli
If it is allowed I would propose that the 2.x line just uses the same
package name as the 1.x line.
--
Russel
Hello Pooja,
2016-01-21 6:54 GMT+01:00 Chitnis, Pooja :
> Hi cli dev team,
>
> I recently upgraded to the commons-cli version 1.3.1 where the BasicParser
> is deprecated. So if I sue the DefaultParser instead, my following sample
> code would not work -
>
> public static vo
Hi,
Apache Mahout is moving to fully a Maven-based build/release process
and they're having problems with the commons-cli 2.0 dependency which
I believe they get through Hadoop. To solve the dependency issue,
Mahout has deployed that snapshot to Maven central as
org.apache.mahout.commons:co
Hi Wolfgang,
It's great that the bugfix release has driven some interest onto the
lists for improving the library. Validation sounds very useful - is it
something that you think Commons Validator would be useful for, or do
the use cases not quite match?
Brian and others... any thoughts?
Can someone tell me if it is ok to use long option with a single dash .
Author: bayard
Date: Wed Jul 25 13:45:20 2007
New Revision: 559598
URL: http://svn.apache.org/viewvc?view=rev&rev=559598
Log:
Really this is 1.x, not 1.0.x as we just released 1.1 from here
Added:
jakarta/commons/proper/cli/branches/cli-1.x/
- copied from r559597, jakarta/com
Just an observation. I am working on the Rat tool. Part of that is that
we want to harmonize the UIs (CLI, Ant, and Maven) so that there are
congruent options across the UIs.
The Option definition in commons-cli v1.8.0 is sufficiently complex that we
can define the options in the CLI interface
ing to fully a Maven-based build/release process
> and they're having problems with the commons-cli 2.0 dependency which
> I believe they get through Hadoop. To solve the dependency issue,
> Mahout has deployed that snapshot to Maven central as
> org.apache.mahout.commons:commons-cli
Hi Jukka,
Hi,
Apache Mahout is moving to fully a Maven-based build/release process
and they're having problems with the commons-cli 2.0 dependency which
I believe they get through Hadoop. To solve the dependency issue,
Mahout has deployed that snapshot to Maven centr
Validation sounds very useful - is it
something that you think Commons Validator would be useful for, or do
the use cases not quite match?
Brian and others... any thoughts?
CLI future wise, I think we're looking at:
* CLI 1.2. Consider whether a bugfix release is required. Make small
changes, n
Hi Wolfgang,
I agree that the framework should have better support for groups and mutually
exclusive options. This is a feature I've often had to do in a pre or post
processing step.
I've thought about writing a CLI library which would accept a EBNF option
grammar, much like
Brian A. Egge wrote:
> Hi Wolfgang,
>
> I agree that the framework should have better support for groups and mutually
> exclusive options. This is a feature I've often had to do in a pre or post
> processing step.
>
> I've thought about writing a CLI library w
Hi,
I would like to know the current status for CLI 2.0. Is there anyone working
on it? How far does it from for becoming a release? I am considering using it
and even working on it.
Thanks.
Nicholas
Dear Apaches,
First time post to Apache mailing lists, I've read all the necessary
documentation and hoping I've got this all right! If not, feel free to let
me know.
Currently working on several related projects that make heavy use of the
CLI library. However, to speed development, a
Hi All,
I intend to create a release candidate for CLI 1.5 soon. This will be the
last Java 7 release IMO and I plan on this being a simple kinde of release,
no big new feature. Feel free to look at Jira.
Beyond that, the snapshot POM can go to Java 8.
I am not sure if CLI has a future without
Is there a good reason not to support kabob-format in CLI?
I can see that we have to strip the '-' nad '--' off the front but after
that tis seems like anything before a space should be valid.
--
LinkedIn: http://www.linkedin.com/in/claudewarren
Hi Manuel,
I would suggest to set the dafult type to String beause thats exactly what i
was expacting. I would have provided a patch but i was not sure where to
implement it (either as a fallback in CommandLine.getParsedOptionValue or in
the Option constructor).
That's a good suggestion, coul
Hi all guys,
any objection if I provide help on fixing checkstyle/findbugs/compiler warnings?
Thanks in advance,
Simo
http://people.apache.org/~simonetripodi/
http://www.99soft.org/
-
To unsubscribe, e-mail: dev-unsubscr...@commo
I'm trying to use OptionGroup to mutually exclude arguments, and it seems
to be broken. I've setup --ip-address & --hostname as options in a single
group, then provide both on the "command line" and would expect the parser
to throw an AlreadySelectedException, but it doesn't... it happily parses
bo
Hello everybody,
I'm wondering if there are any plans to release Commons CLI 1.3? 1.2 was
release a long time ago and some people (like the Groovy Team) are
waiting for a final 1.3 Release because of the bugs fixed in 1.3 Snapshot.
Kind regards,
Pascal Schum
Hi,
well, I did not work much on cli, but lately I have cleanup up together
with sebb the trunk, and I think it is in a state that could be released
soon:
* there are no open major issues (most issues are related to cli2)
* no findbugs & checkstyle warnings anymore
* trunk contains lot
Hi guys,
There seems to be a bit of work regarding JIRAs maintenance to do...
Like: Major Bug (https://issues.apache.org/jira/browse/CLI-232) that seems
to be fixed and should / could probably be moved to testing or resolved...
I'm happy to do the work If I can ... =)
Any ideas on wha
Hi Russel,
see my comments below
Cheers,
Siegfried Goeschl
Russel Winder wrote:
> Last year there was a lot of effort trying to get Commons CLI into a fit
> state for a 1.2 release -- much credit to Emmanuel Bourg.
>
> However, having got the Subversion 1.x branch of Commons CL
Siegfried Goeschl schrieb:
Hi Russel,
see my comments below
Cheers,
Siegfried Goeschl
Russel Winder wrote:
Last year there was a lot of effort trying to get Commons CLI into a fit
state for a 1.2 release -- much credit to Emmanuel Bourg.
However, having got the Subversion 1.x branch of
On Mon, Jan 12, 2009 at 5:37 AM, Russel Winder
wrote:
> Last year there was a lot of effort trying to get Commons CLI into a fit
> state for a 1.2 release -- much credit to Emmanuel Bourg.
>
> However, having got the Subversion 1.x branch of Commons CLI into a fit
> state fo
JIRA, there are issues in v1.3 that I think we should cover:
>
> * https://issues.apache.org/jira/browse/CLI-162 is a bug so should be
> considered for 1.2.
I guess this really depends on whether someone can find and fix the bug
in the next few days? The problem with moving this t
On Wed, 2009-01-14 at 09:30 +, Russel Winder wrote:
> > * https://issues.apache.org/jira/browse/CLI-170 is something I'd like
> > to get in. I've attached a patch for people's opinions and put in 1.2
> > for now.
>
> I have pulled the commits and w
Hi folks,
looking at my workload I will be able to cut an RC plus patch work
starting in February - would this be okay for you?
Cheers,
Siegfried Goeschl
Russel Winder wrote:
> On Wed, 2009-01-14 at 09:30 +, Russel Winder wrote:
>
>
>>> * https://issues.apache.org/jira
On Wed, Jan 14, 2009 at 3:36 AM, Russel Winder
wrote:
> On Wed, 2009-01-14 at 09:30 +, Russel Winder wrote:
>
>> > * https://issues.apache.org/jira/browse/CLI-170 is something I'd like
>> > to get in. I've attached a patch for people's opinions and put i
Henri,
On Sat, 2009-01-17 at 01:33 -0800, Henri Yandell wrote:
> Thanks Russel. I've committed that and also committed a 'fix' to
> CLI-162 to change the OutOfMemoryError to a RuntimeException. I'm
> going to skip on CLI-161 - having the OutOfMemoryError felt bad.
Hi there,
i would like to know if there are any plan to get an 2.0 of CLI out of
the door in the near futuere ?
Kind regards
Karl Heinz Marbaise
--
SoftwareEntwicklung Beratung SchulungTel.: +49 (0) 2405 / 415 893
Dipl.Ing.(FH) Karl Heinz MarbaiseICQ#: 135949029
Hauptstrasse 177
How are you looking for this Siegfried?
I'd like to encourage any opportunity for someone else to do a
release, but I can do it if it's not looking like things are freeing
up for you.
CLI at least is on Maven2 etc and easy to do, while Collections has me
wincing at needing to figure o
se-prepare" step ... ;-)
Let's see if I can spend an hour or two on commons-cli over the weekend ...
Thanks for your help,
Siegfried Goeschl
Henri Yandell wrote:
> How are you looking for this Siegfried?
>
> I'd like to encourage any opportunity for someone else to
;d like to encourage any opportunity for someone else to do a
> release, but I can do it if it's not looking like things are freeing
> up for you.
>
> CLI at least is on Maven2 etc and easy to do, while Collections has me
> wincing at needing to figure out whether it's Ant, Maven or
1 - 100 of 947 matches
Mail list logo
