Review request: 8003562: Provide a command-line tool to find static dependencies

Mandy Chung mandy.chung at
Tue Dec 18 04:15:56 UTC 2012

On 12/17/12 8:13 AM, Ulf Zibis wrote:
> Am 17.12.2012 16:23, schrieb Alan Bateman:
>> I mostly agree with your argument that this is a new tool and that we 
>> should be consistent with GNU-style options. So what was the final 
>> bid is, is it --classpath or --class-path?

I propose --class-path so that it makes it easier to determine 
-classpath is not supported
>> I guess it wouldn't do any harm to silently supporting -cp and 
>> -classpath as folks used to java* tools will probably use them 
>> without thinking.
How important to carry the same option -cp and -classpath on j* tools?  
I do think developers can well adapt to a slight different option when 
using a new tool.  I'm inclined not to mix these styles.  In addition, 
I'd like to see how jdeps will be used after the initial push and people 
finds --class-path hard to move to.

> Thanks for supporting my arguments about "silent familarity" to old 
> style, Alan.
> As --class(-)path is a frequent and important option, I additionally 
> think, we should have an official short form. If '-cp' doesn't conform 
> with GNU-style, what about '-C' ?

I considered '-C' and it might be confused with 'jar -C' and 'tar -C' 
option to change the directory.  I think '-c' may be okay and it can 
avoid such confusion and closer to '-cp'.   Are you okay with that?

I'd like to send a new webrev tomorrow and finalize the review this week.


More information about the core-libs-dev mailing list