Re: Automatic module names

While true that would be immensely confusing to users I think. However, if two modules have the same packages in them you will get an error at runtime. "Now consider again the key restriction that a package must be found in one and only one module. This restriction applies to hidden packages as

Re: Automatic module names

Isn't it the opposite? Giving them the same module name will prevents them from being used together, which is what we want: http://blog.joda.org/2017/04/java-se-9-jpms-module-naming.html?m=1 "JPMS will simply refuse to start a modulepath where two modules have the same name, even if they contain

Re: Automatic module names

Actually, re-reading this again makes it clear to me that log4j-slf4j-impl and log4j-to-slf4j SHOULD use the same package name as it prevents them from both being present at the same time. Obviously, their module names still have to be different but this could mean the code doesn’t really need t

Re: Automatic module names

You should read (or re-read) this - http://blog.joda.org/2017/04/java-se-9-jpms-module-naming.html . I believe it is the most likely standard to be adopted. Ralph > On Sep 11, 2017, at 6:26 PM, Matt Sicker wrote: > > Is it possi

Re: Automatic module names

Is it possible to make the JPMS module names the same as the OSGi ones? The default OSGi naming scheme is basically: groupId: org.apache.logging.log4j, artifactId: log4j-foo becomes bundleId: org.apache.logging.log4j.foo On 11 September 2017 at 13:01, Gary Gregory wrote: > On Mon, Sep 11, 2017

Re: Automatic module names

On Mon, Sep 11, 2017 at 11:27 AM, Ralph Goers wrote: > I know we discussed module names in the past and decided not to go the > route of modularizing now - in fact, we can’t until all of our dependencies > are modularized. However, we can (and probably should) add the automatic > module name as a

Automatic module names

I know we discussed module names in the past and decided not to go the route of modularizing now - in fact, we can’t until all of our dependencies are modularized. However, we can (and probably should) add the automatic module name as a manifest entry to each of our jars. My understanding is tha