Looks nice!
Some feedback:
* I don't like to prefix interface names with "I", as you do in
ITypeConverter etc. Doing so is common in .Net, but not in Java.
* Why does CommandLine.parse() return List? This is not correctly
documentated in the Javadoc @return tag.
* Maybe CommandLine.usage() coul
I do love the color help output!
Gary
On Apr 15, 2017 6:13 PM, "Remko Popma" wrote:
> JCommander is very, very good. Apart from the dependency thing, some
> differences:
>
> Picocli has:
> - strongly typed positional parameters (in JCommander only options are
> strongly typed, positional parame
JCommander is very, very good. Apart from the dependency thing, some
differences:
Picocli has:
- strongly typed positional parameters (in JCommander only options are
strongly typed, positional parameters are a list of Strings)
- support for POSIX short options (so you can say ` -xvfInputFile`
as w
I use JCommander a lot. Can you explain the difference? Most applications I
work on depend on other jars, so one more is no biggie.
Thank you!
Gary
On Apr 15, 2017 7:25 AM, "Remko Popma" wrote:
> Everyone, I would love your feedback on this:
>
> https://remkop.github.io/picocli/
> https://githu
Sent from my iPhone
> On Apr 16, 2017, at 2:44, Christian Grobmeier wrote:
>
> I agree with Matt.
>
> What I love is the way you use annotations.
I can't claim credit for that idea: that's the "inspired by JCommander/Args4j"
part.
https://github.com/remkop/picocli/wiki/FAQ
> I can't tell
> On Apr 16, 2017, at 0:47, Matt Sicker wrote:
>
> It looks pretty neat! The single source code file idea is an amusing C-like
> distribution mechanism, but it makes sense for this style of library. I'm
> curious how you're making the docs as I've seen that format a lot and think
> it could poss
I agree with Matt.
What I love is the way you use annotations. I can't tell you how I miss
annotations when I work with PHP.
On Sat, Apr 15, 2017, at 17:47, Matt Sicker wrote:
> It looks pretty neat! The single source code file idea is an amusing
> C-like
> distribution mechanism, but it makes
It looks pretty neat! The single source code file idea is an amusing C-like
distribution mechanism, but it makes sense for this style of library. I'm
curious how you're making the docs as I've seen that format a lot and think
it could possibly be useful for log4j-core or one of the other subproject
Everyone, I would love your feedback on this:
https://remkop.github.io/picocli/
https://github.com/remkop/picocli
It is heavily inspired by JCommander and Args4j but has improved
ergonomics, customizable help (with colors) and various other improvements.
I hope this will be useful in the log4j-t
