Re: JEP 293: Guidelines for JDK Command-Line Tool Options - @-files

2016-10-28 Thread Alan Bateman
On 28/10/2016 20:15, Robert Scholte wrote: : Now I'm getting new messages, often one of these: Error: module-info.class not found for hibernate.jpa module or Error: module-info.class not found for spring.context module or Error: module-info.class not found for spring.orm module So let's forge

Re: JEP 293: Guidelines for JDK Command-Line Tool Options - @-files

2016-10-28 Thread Robert Scholte
On Fri, 28 Oct 2016 07:05:06 +0200, Henry Jen wrote: OS-specific encoding, but has to be ASCII friendly, modern system with UTF-8 as system encoding should work just fine. Hmm, this will probably work for 99%, but I'm sure that we will have Maven users which use special characters on their

Re: JEP 293: Guidelines for JDK Command-Line Tool Options - @-files

2016-10-27 Thread Henry Jen
OS-specific encoding, but has to be ASCII friendly, modern system with UTF-8 as system encoding should work just fine. Space in quote should work just fine, for example, “c:\\Program Files” should be correct. Can you post messages from JLink? Also if you can verify java is working OK with space

JEP 293: Guidelines for JDK Command-Line Tool Options - @-files

2016-10-27 Thread Robert Scholte
Hi, I'm facing some troubles with the content of the @-files and the documentation[1] isn't helping me yet. First of all it doesn't mention the encoding, I assume it is the OS specific encoding. I'm facing issues with a long --module-path on Windows. I noticed I can use the "normal" filen

Re: JEP 293: Guidelines for JDK Command-Line Tool Options

2016-07-13 Thread Stuart Marks
On 7/7/16 12:16 PM, mark.reinh...@oracle.com wrote: New JEP Candidate: http://openjdk.java.net/jeps/293 Hi Jon, Good writeup and rundown of the issues. I have a few questions to raise. options can allow an argument to be provided This describes an option with an optional argument. I rec

Re: JEP 293: Guidelines for JDK Command-Line Tool Options

2016-07-08 Thread Dan Smith
> On Jul 8, 2016, at 8:01 AM, Jonathan Gibbons > wrote: > > On 07/07/2016 11:07 PM, Dan Smith wrote: >> A suggestion for clarifying the text: I was confused about whether "may" >> refers to choices that the tool developer is allowed to make, or choices >> that the end user is allowed to make.

Re: JEP 293: Guidelines for JDK Command-Line Tool Options

2016-07-08 Thread Jonathan Gibbons
On 07/07/2016 11:07 PM, Dan Smith wrote: A suggestion for clarifying the text: I was confused about whether "may" refers to choices that the tool developer is allowed to make, or choices that the end user is allowed to make. For example: "Options can require an argument to be provided. For a l

Re: JEP 293: Guidelines for JDK Command-Line Tool Options

2016-07-07 Thread Dan Smith
A suggestion for clarifying the text: I was confused about whether "may" refers to choices that the tool developer is allowed to make, or choices that the end user is allowed to make. For example: "Options can require an argument to be provided. For a long-form options, the argument may be sepa

JEP 293: Guidelines for JDK Command-Line Tool Options

2016-07-07 Thread mark . reinhold
New JEP Candidate: http://openjdk.java.net/jeps/293 - Mark