options without - prepended hyphen

[theonlygusti]

How can I create options that don't require a prepended hyphen?

private class CommandTemplate {

  @Parameter

  private List<String> parameters = new ArrayList<>();

  @Parameter(names = "help", help = true)

  private boolean help;

}

Doesn't seem to work, 

[Cédric Beust ♔]

Options need to start with `-` right now (otherwise JCommander can't easily distinguish between an option and a main parameter).

-- 

Cédric

--
You received this message because you are subscribed to the Google Groups "jcommander" group.
To unsubscribe from this group and stop receiving emails from it, send an email to jcommander+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[gbakewell7]

But surely it can just take option/value pairings like: mainCommand
<option> <value> <option arity 2> <value> <value> <option> etc..

[George Bakewell]

But surely it can just take option/value pairings like: mainCommand <option> <value> <option arity 2> <value> <value> <option> etc..

[George Bakewell]

Then what happens if a value starts with `-`? Surely this must be a problem in the current implementation.

On 22 January 2017 at 19:14, Cédric Beust ♔ <ced...@beust.com> wrote:

[Cédric Beust ♔]

It's certainly possible to improve the option detection. Right now, all it does is check if the word parsed starts with a `-`. Instead, it could instead compare it with all the option names declared in your annotations and if all of this fails, then the parameter is a main parameter.

-- 

Cédric

[gbakewell7]

Any chance of this being implemented?

[Cédric Beust ♔]

Not in the near future by me, but you are welcome to send a pull request if you are interested in implementing this yourself.

-- 

Cédric

On Sun, Jan 22, 2017 at 1:41 PM, gbakewell7 <gbake...@gmail.com> wrote:

Any chance of this being implemented?

[theonlygusti]

Could you point me at the relevant code?

On Sunday, 22 January 2017 21:44:52 UTC, Cédric Beust ♔ wrote:

Not in the near future by me, but you are welcome to send a pull request if you are interested in implementing this yourself.

-- 

Cédric

On Sun, Jan 22, 2017 at 1:41 PM, gbakewell7 <gbake...@gmail.com> wrote:

Any chance of this being implemented?

--
You received this message because you are subscribed to the Google Groups "jcommander" group.

To unsubscribe from this group and stop receiving emails from it, send an email to jcommander+...@googlegroups.com.

[Cédric Beust ♔]

Actually I'm looking into this.

-- 

Cédric

To unsubscribe from this group and stop receiving emails from it, send an email to jcommander+unsubscribe@googlegroups.com.

[Cédric Beust ♔]

I filed this to keep track: https://github.com/cbeust/jcommander/issues/321

-- 

Cédric

[Cédric Beust ♔]

I just deployed a new JCommander to JCenter which no longer requires options to have a prefix. As a consequence, the following test passes:

  public void noDash() {
    class Arguments {
      private int bar;

      @Parameter(names = { "bar", "foo" })
      private void setBar(int value) {
        bar = value;
      }

      @Parameter(names = "otherName")
      private String otherName;
    }

    Arguments a = new Arguments();
    new JCommander(a, "bar", "1");
    Assert.assertEquals(a.bar, 1);
  }

There might be a few edge cases here and there but all the tests are passing so I’m pretty sure there are no regressions.

File issues if you encounter any difficulties.

Thanks!

​

-- 

Cédric

[gbakewell7]

Thank you so much Cédric for being so helpful! It's awesome that
you've managed to update it in such a short time, I haven't actually
tested it yet but I'll be sure to file an issue if I encounter any!
Thanks :)

[Cédric Beust ♔]

This issue was brought up twice in the past few weeks (somebody else mentioned it before you) and it's been nagging me since then because there was no reason why JCommander should have relied on option prefixes in the first place.

And I was glad to see it was as easy to fix as I expected :)

-- 

Cédric

[theonlygusti]

Hey, so I've got a little problem since switching the dependency to 1.7.

I'm trying to create a help option without any prefix:

public class CommandTemplate {

  @Parameter

  private List<String> parameters = new ArrayList<>();

  

  @Parameter(names = "help", help = true)

  private boolean help;

}

public static void main(String[] args) {

  CommandTemplate template = new CommandTemplate();

  JCommander jcommander = new JCommander(template);

  jcommander.setProgramName("prog");

  jcommander.parse(args);

  

  if (template.help) {

    jcommander.usage();

  }

}

It doesn't work,

cannot find symbol

symbol:   method help()

On Tuesday, 24 January 2017 21:24:33 UTC, Cédric Beust ♔ wrote:

This issue was brought up twice in the past few weeks (somebody else mentioned it before you) and it's been nagging me since then because there was no reason why JCommander should have relied on option prefixes in the first place.

And I was glad to see it was as easy to fix as I expected :)

-- 

Cédric

On Tue, Jan 24, 2017 at 12:55 PM, gbakewell7 <gbake...@gmail.com> wrote:

Thank you so much Cédric for being so helpful! It's awesome that
you've managed to update it in such a short time, I haven't actually
tested it yet but I'll be sure to file an issue if I encounter any!
Thanks :)

--
You received this message because you are subscribed to the Google Groups "jcommander" group.

To unsubscribe from this group and stop receiving emails from it, send an email to jcommander+...@googlegroups.com.

[theonlygusti]

[ERROR] ~/com/prog/Commander.java:[41,40] cannot find symbol

[ERROR] symbol:   method help()

[ERROR] location: @interface com.beust.jcommander.Parameter

On Tuesday, 24 January 2017 21:24:33 UTC, Cédric Beust ♔ wrote:

This issue was brought up twice in the past few weeks (somebody else mentioned it before you) and it's been nagging me since then because there was no reason why JCommander should have relied on option prefixes in the first place.

And I was glad to see it was as easy to fix as I expected :)

-- 

Cédric

On Tue, Jan 24, 2017 at 12:55 PM, gbakewell7 <gbake...@gmail.com> wrote:

Thank you so much Cédric for being so helpful! It's awesome that
you've managed to update it in such a short time, I haven't actually
tested it yet but I'll be sure to file an issue if I encounter any!
Thanks :)

--
You received this message because you are subscribed to the Google Groups "jcommander" group.

To unsubscribe from this group and stop receiving emails from it, send an email to jcommander+...@googlegroups.com.

[Cédric Beust ♔]

Seems to work for me. I pasted your code verbatim and when I run it:

Usage: prog [options]
  Options:
    help

The compilation error appears to be in your code?

  static class CommandTemplate {
    @Parameter
    private List<String> parameters = new ArrayList<>();

    @Parameter(names = "help", help = true)
    private boolean help;
  }

  @Test(enabled = false)
  public static void main(String[] args) {
    CommandTemplate template = new CommandTemplate();
    JCommander jcommander = new JCommander(template);
    jcommander.setProgramName("prog");
    jcommander.parse("help");

    if (template.help) {
      jcommander.usage();
    }
  }

​

-- 

Cédric

To unsubscribe from this group and stop receiving emails from it, send an email to jcommander+unsubscribe@googlegroups.com.

[theonlygusti]

Well, for some reason it won't work for me and the error being thrown is on this exact line of code:

@Parameter(names = "help", help = true)

I have no idea why it would work for you and not for me, but here's the lines I've added to my pom.xml relevant to this issue:

    <dependency>

      <groupId>com.beust</groupId>

      <artifactId>jcommander</artifactId>

      <version>1.7</version>

    </dependency>

    <repository>

      <id>jcenter</id>

      <url>https://jcenter.bintray.com/</url>

    </repository>

[Cédric Beust ♔]

The latest version is 1.61. 1.7 is a very old version.

-- 

Cédric

To unsubscribe from this group and stop receiving emails from it, send an email to jcommander+unsubscribe@googlegroups.com.