rfscholte commented on a change in pull request #463:
URL: https://github.com/apache/maven/pull/463#discussion_r606263973



##########
File path: maven-embedder/src/main/java/org/apache/maven/cli/CLIManager.java
##########
@@ -121,11 +121,11 @@ public CLIManager()
         options.addOption( Option.builder( Character.toString( QUIET ) 
).longOpt( "quiet" ).desc( "Quiet output - only show errors" ).build() );
         options.addOption( Option.builder( Character.toString( DEBUG ) 
).longOpt( "debug" ).desc( "Produce execution debug output" ).build() );
         options.addOption( Option.builder( Character.toString( ERRORS ) 
).longOpt( "errors" ).desc( "Produce execution error messages" ).build() );
-        options.addOption( Option.builder( Character.toString( NON_RECURSIVE ) 
).longOpt( "non-recursive" ).desc( "Do not recurse into sub-projects" ).build() 
);
+        options.addOption( Option.builder( Character.toString( NON_RECURSIVE ) 
).longOpt( "non-recursive" ).desc( "Do not recurse into sub-projects. When used 
together with -pl, do not recurse into sub-projects of selected aggregators" 
).build() );
         options.addOption( Option.builder( Character.toString( 
UPDATE_SNAPSHOTS ) ).longOpt( "update-snapshots" ).desc( "Forces a check for 
missing releases and updated snapshots on remote repositories" ).build() );
-        options.addOption( Option.builder( Character.toString( 
ACTIVATE_PROFILES ) ).longOpt( "activate-profiles" ).desc( "Comma-delimited 
list of profiles to activate" ).hasArg().build() );
+        options.addOption( Option.builder( Character.toString( 
ACTIVATE_PROFILES ) ).longOpt( "activate-profiles" ).desc( "Comma-delimited 
list of profiles to activate. Prefixing a profile with ! excludes it, and ? 
marks it as optional" ).hasArg().build() );

Review comment:
       This is my concern too. The (default) help output should be compact, it 
used to fit on 1 page. 
   With the new jansi we're probably gaining some space due to the width 
calculation.




-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

For queries about this service, please contact Infrastructure at:
us...@infra.apache.org


Reply via email to