[ https://issues.apache.org/jira/browse/SLING-10186?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17314012#comment-17314012 ]
Eric Norman commented on SLING-10186: ------------------------------------- [~bisch...@jena.de] Thanks for working on this. I would probably lean toward keeping the whitespace between "-D" and "<name>=<value>" as it was in 1.1.16 to avoid any backward compatibility troubles. Or it you want to keep supporting the "-D<name>=<value>" style and make that the new preferred style then perhaps add some new code to also support the older "-D <name>=<value>" style and log a deprecation warning for any usage of that older syntax. > Enhance cli parsing on sling-feature-launcher > --------------------------------------------- > > Key: SLING-10186 > URL: https://issues.apache.org/jira/browse/SLING-10186 > Project: Sling > Issue Type: Improvement > Reporter: Stefan Bischof > Assignee: Robert Munteanu > Priority: Major > Fix For: Feature Model Launcher 1.1.18 > > > extract opts as Constants > add longOpt to Options > fix plural in description > use Builder-pattern to build Options > set numberOfArgs , valueSeparator(',') > accept (but ignore) empty options without ParsingExceptions > using .optionalArg(true) and Optionals > option to set loglevel on verbose Option > update common-cli version > use DefaultParser not deprecated BasicParser > https://github.com/apache/sling-org-apache-sling-feature-launcher/pull/16 -- This message was sent by Atlassian Jira (v8.3.4#803005)