[ https://issues.apache.org/jira/browse/MNG-6069?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16835848#comment-16835848 ]
Hudson commented on MNG-6069: ----------------------------- Build succeeded in Jenkins: Maven TLP » maven » MNG-6069v2 #2 See https://builds.apache.org/job/maven-box/job/maven/job/MNG-6069v2/2/ > 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: 20m > 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 (v7.6.3#76005)