On Tue, 24 Nov 2020 09:52:34 GMT, Joel Borggrén-Franck
wrote:
>> Magnus Ihse Bursie has updated the pull request incrementally with one
>> additional commit since the last revision:
>>
>> Fix whitespace issues
>
> src/jdk.compiler/share/classes/com/sun/tools/sjavac/Util.java line 96:
>
>> 9
On Mon, 16 Nov 2020 12:44:08 GMT, Magnus Ihse Bursie wrote:
>> Currently, to use the javac server, a horrendously long command line option
>> is created, looking like this: `--server:portfile=> portfile>:sjavac=`, where the sjavac command has
>> had all spaces replaced by %20. Since Project Jig
On Tue, 17 Nov 2020 23:00:26 GMT, Jonathan Gibbons wrote:
>> Magnus Ihse Bursie has updated the pull request incrementally with one
>> additional commit since the last revision:
>>
>> Fix whitespace issues
>
> There seems to be much more here than there needs to be.
>
> If the issue is just
On Mon, 16 Nov 2020 12:44:08 GMT, Magnus Ihse Bursie wrote:
>> Currently, to use the javac server, a horrendously long command line option
>> is created, looking like this: `--server:portfile=> portfile>:sjavac=`, where the sjavac command has
>> had all spaces replaced by %20. Since Project Jig
On Mon, 16 Nov 2020 12:44:08 GMT, Magnus Ihse Bursie wrote:
>> Currently, to use the javac server, a horrendously long command line option
>> is created, looking like this: `--server:portfile=> portfile>:sjavac=`, where the sjavac command has
>> had all spaces replaced by %20. Since Project Jig
> Currently, to use the javac server, a horrendously long command line option
> is created, looking like this: `--server:portfile= portfile>:sjavac=`, where the sjavac command has
> had all spaces replaced by %20. Since Project Jigsaw, the set of module
> arguments needed is huge to begin with,
On Thu, 12 Nov 2020 22:13:37 GMT, Magnus Ihse Bursie wrote:
> Currently, to use the javac server, a horrendously long command line option
> is created, looking like this: `--server:portfile= portfile>:sjavac=`, where the sjavac command has
> had all spaces replaced by %20. Since Project Jigsaw,
On Fri, 13 Nov 2020 01:08:09 GMT, Magnus Ihse Bursie wrote:
>> Currently, to use the javac server, a horrendously long command line option
>> is created, looking like this: `--server:portfile=> portfile>:sjavac=`, where the sjavac command has
>> had all spaces replaced by %20. Since Project Jig
> Currently, to use the javac server, a horrendously long command line option
> is created, looking like this: `--server:portfile= portfile>:sjavac=`, where the sjavac command has
> had all spaces replaced by %20. Since Project Jigsaw, the set of module
> arguments needed is huge to begin with,
> Currently, to use the javac server, a horrendously long command line option
> is created, looking like this: `--server:portfile= portfile>:sjavac=`, where the sjavac command has
> had all spaces replaced by %20. Since Project Jigsaw, the set of module
> arguments needed is huge to begin with,
> Currently, to use the javac server, a horrendously long command line option
> is created, looking like this: `--server:portfile= portfile>:sjavac=`, where the sjavac command has
> had all spaces replaced by %20. Since Project Jigsaw, the set of module
> arguments needed is huge to begin with,
> Currently, to use the javac server, a horrendously long command line option
> is created, looking like this: `--server:portfile= portfile>:sjavac=`, where the sjavac command has
> had all spaces replaced by %20. Since Project Jigsaw, the set of module
> arguments needed is huge to begin with,
Currently, to use the javac server, a horrendously long command line option is
created, looking like this: `--server:portfile=:sjavac=`, where the sjavac command has had
all spaces replaced by %20. Since Project Jigsaw, the set of module arguments
needed is huge to begin with, making this comman
13 matches
Mail list logo
