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

[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, that would be helpful to tell if there is something different in JLink.

Cheers,
Henry

On October 27, 2016 at 2:27:44 PM, Robert Scholte (rfscholte at apache.org) wrote:
> 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" filename (not a URI or URL), but I need
> to escape the \ with an \, resulting in
> "E:\\java-workspace\\sandbox\\mvnexbook-examples-1.0\\ch-multi-spring\\simple-parent\\simple-command\\target\\classes;E:\\java-workspace\\sandbox\\mvnexbook-examples-1.0\\ch-multi-spring\\simple-parent\\simple-weather\\target\\simple-weather-0.8-SNAPSHOT.jar;"  
> (and much more entries)
>  
> You can use a space or a newline as separator between arguments, but if an
> argument contains spaces it must be surrounded with double quotes.
> However, the path to my local (Maven) repository contains a space and
> JLink is complaining it cannot find these dependencies. It seems like I
> need to escape spaces too, though I haven't figured out how to do that.
> Changing my local repo to a space-less path works. There should be a way
> to handle spaces, but how?
>  
> I'm not sure if there are other specific things to keep in mind when
> writing @-files, but it would be nice if that would be explained it the
> jep too.
>  
> thanks,
> Robert
>  
> [1] http://openjdk.java.net/jeps/293
>