Cannot compile with picocli-shell-jline3 dependency using Maven

[sualeh]

Since the change to Fix gradle warnings, Maven compilation of any project with picocli-shell-jline3 as a dependency is broken, since the artifact published to The Central Repository has a changed the scope of transitive dependencies to jline - see the following changes to scope in the published pom.xml:

    <dependency>
      <groupId>org.jline</groupId>
      <artifactId>jline</artifactId>
      <version>3.17.1</version>
      <scope>runtime</scope>
    </dependency>

whereas in former versions of picocli it was

    <dependency>
      <groupId>org.jline</groupId>
      <artifactId>jline</artifactId>
      <version>3.16.0</version>
      <scope>compile</scope>
    </dependency>

In order words, the change in how the Gradle dependency is defined has broken the Maven scope, and compilation fails.

[sualeh]

@deining - copying you for information too.

[remkop]

@sualeh Thank you for raising this!

Will applications be able to work around this by explicitly adding this dependency to their POM?

    <dependency>
      <groupId>org.jline</groupId>
      <artifactId>jline</artifactId>
      <version>3.16.0</version>
      <scope>compile</scope>
    </dependency>

If so, we can try to fix this in the next release, but in the meantime add a note for this to the documentation.

[sualeh]

Here is the way I suggest:

    <dependency>
      <groupId>info.picocli</groupId>
      <artifactId>picocli-shell-jline3</artifactId>
      <version>4.6.0</version>
      <exclusions>
        <exclusion>
          <groupId>org.jline</groupId>
          <artifactId>jline</artifactId>
        </exclusion>
      </exclusions>
    </dependency>
    <dependency>
      <groupId>org.jline</groupId>
      <artifactId>jline</artifactId>
      <version>3.17.1</version>
    </dependency>

[dejan2609]

Related issue #1294 is reported by @remal (I will try to expand my PR asap).

[sualeh]

@remkop - may I request a point release with this fix?

[remkop]

Yes will do.

[remkop]

Thanks again for raising this!
This is fixed in the 4.6.1 release.

[deining]

@deining - copying you for information too.

Sorry for messing up things here. A huge thanks to everyone involved in ironing this fault out so quickly.

[remkop]

@deining No worries at all! 😉
I now finally sat down to learn the difference between api and implementation. So thank you! 😄
And I also think it is pretty cool how a whole bunch of people got together to help fix things so quickly. 🙏 Truly grateful!

[dejan2609]

Don't mention it @deining ! No man is able to be a jack off all trades.. and besides that: you gave us a chance to return something to the community ☺️

@remkop feel free to ping me in case of some Gradle related issues 😉