On 13/05/2018 2:40 AM, Thomas Stüfe wrote:
Thank you Volker!
@David: I agree with Volker. I'm all for proper processes where they
are necessary, but in this case we are moving in undefined territory.
CSR request is needed when "Adding, removing, or changing a command line
option". [1] The lack of documented behaviour just makes the
compatibility argument easier to make.
Thanks,
David
[1] https://wiki.openjdk.java.net/display/csr/CSR+FAQs
..Thomas
On Sat, May 12, 2018 at 12:38 PM, Volker Simonis
<[email protected]> wrote:
Hi Thomas,
I think the request sounds reasonable and the change looks good.
@David: why should this require a CSR request? I don’t see that the behavior
for bad command line flags is specified somewhere. So we’re changing an
undocumented behavior into o more meaningful undocumented behavior.
Regards,
Volker
David Holmes <[email protected]> schrieb am Sa. 12. Mai 2018 um 11:52:
Hi Thomas,
Without commenting on the suggestion, this will need a CSR request.
Cheers,
David
On 12/05/2018 6:08 PM, Thomas Stüfe wrote:
Hi,
may I have reviews for this very small improvement?
Bug: https://bugs.openjdk.java.net/browse/JDK-8203014
Webrev:
http://cr.openjdk.java.net/~stuefe/webrevs/8203014-jcmd-list-commands-if-no-command-given/webrev.00/webrev/
When jcmd is invoked with valid target VM id(s) but without command,
the generic help text is output. It would be more convenient if the
target VM would output a list of available commands.
In other words, "jcmd <target vm>" should behave like "jcmd <target vm>
help".
Thanks, Thomas
