Hi,
in the "Alternatives to automatic modules..." thread David mentioned
ModiTect [1], a tool I've been working on for creating/adding Java 9
module descriptors. I thought I'd share some more details, hoping it's
helpful to others for moving their apps and libraries to Jigsaw.
The tool currently
sure, I will do that in the future if that is then the way to go.
Because before (maybe a year ago) I was told to post to the dev list
instead.
On 16.03.2017 18:19, Andrew Dinn wrote:
Hi Jochen,
If you want to comment on a thread on the expert group list then you
really need to post that comm
Changeset: 3029d66f1952
Author:mchung
Date: 2017-03-16 14:21 -0700
URL: http://hg.openjdk.java.net/jigsaw/jake/jdk/rev/3029d66f1952
remove unused qualified qualifed from java.base
! src/java.base/share/classes/module-info.java
Hi Jochen,
If you want to comment on a thread on the expert group list then you
really need to post that comment to the observers or comments list.
Posting it here without any context is just going to confuse people who
don't read the expert group list
n.b. I am replying to the jigsaw-dev list ra
> On Mar 16, 2017, at 6:09 AM, Chris Hegarty wrote:
>
> Updated webrev:
> http://cr.openjdk.java.net/~chegar/8176772.01/
Looks good.
thanks
Mandy
On 03/16/2017 10:48 AM, Stephen Colebourne wrote:
Automodules exist to provide a means for gradual migration from a
non-modular world to a modular one. Unfortunately, they have proven
controversial with most of the EG and Jigsaw list. This thread seeks
to bring together some of the proposals to r
Automodules exist to provide a means for gradual migration from a
non-modular world to a modular one. Unfortunately, they have proven
controversial with most of the EG and Jigsaw list. This thread seeks
to bring together some of the proposals to remove automodules.
The key issue is that automodule
On 16.03.2017 14:39, David M. Lloyd wrote:
[...]
It's clear that modules are not to be treated like classes, because (for
example) circularity among modules is considered "bad" whereas
circularity among classes has been shown to be indispensable, and
classes within a class loader or module are
The standard within the scala ecosystem is to append the runtime version to
the artifactid, making every scala module out of compliance with the
proposal.
On Wed, Mar 15, 2017 at 4:00 PM, Robert Scholte
wrote:
> On Wed, 15 Mar 2017 11:13:25 +0100, Stephen Colebourne <
> scolebou...@joda.org> wro
On 16 Mar 2017, at 13:09, Chris Hegarty wrote:
>
>> On 15 Mar 2017, at 17:30, Mandy Chung wrote:
>>
>> ...
>> provides and main class, if present.
>>
>> The modifier of ModuleDescriptor will have AUTOMATIC and so all packages are
>> exported and open implicitly and not shown in the output wh
> On 15 Mar 2017, at 17:30, Mandy Chung wrote:
>
> ...
> provides and main class, if present.
>
> The modifier of ModuleDescriptor will have AUTOMATIC and so all packages are
> exported and open implicitly and not shown in the output which is okay.
This is a good idea. Here’s an example:
ja
Changeset: 59dcb23b9a72
Author:alanb
Date: 2017-03-16 10:33 +
URL: http://hg.openjdk.java.net/jigsaw/jake/jdk/rev/59dcb23b9a72
ModuleFinder.ofSystem() failing with exploded build + security manager
! src/java.base/share/classes/java/lang/module/ModuleFinder.java
!
src/java.bas
12 matches
Mail list logo
