[jira] [Commented] (MNG-6069) Migrate to non deprecated parts of Commons CLI

["Hudson (Jira)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/MNG-6069?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17069807#comment-17069807 ] 

Hudson commented on MNG-6069:
-----------------------------

Build failed in Jenkins: Maven TLP » maven-studies » maven-metrics #4

See https://builds.apache.org/job/maven-box/job/maven-studies/job/maven-metrics/4/

> Migrate to non deprecated parts of Commons CLI
> ----------------------------------------------
>
>                 Key: MNG-6069
>                 URL: https://issues.apache.org/jira/browse/MNG-6069
>             Project: Maven
>          Issue Type: Improvement
>          Components: Embedding
>    Affects Versions: 3.3.9, 3.5.0-alpha-1, 3.5.0-beta-1, 3.5.0
>            Reporter: Karl Heinz Marbaise
>            Assignee: Sylwester Lachiewicz
>            Priority: Minor
>             Fix For: 3.6.2
>
>          Time Spent: 0.5h
>  Remaining Estimate: 0h
>
> At the moment all parts of {{OptionBuilder...}} are marked deprecated in {{CLIManager}}. They should be migrated to:
> {code:java}
> Option.builder( HELP ).longOpt( "help" ).desc( "Display help information" ).build()
> {code}
> Ensure that the following command succeeds: {{mvn -X -D x=1 -D y=2 test}} ( watch out for the space after {{-D}} )
>  
> For now, leave {{GnuParser}}. Despite the upgrade advice in the {{GnuParser}} Javadoc ("since 1.3, use the {{DefaultParser}} instead"), it behaves differently (see [this Stack Overflow answer|https://stackoverflow.com/questions/34549044/why-are-detected-cli-options-different-when-using-defaultparser-instead-of-gnupa] for possible reasons).



--
This message was sent by Atlassian Jira
(v8.3.4#803005)