On 21/09/2016 12:48, Martin Lehmann wrote:
:
But with the new module system, classes on the unnamed package are no longer
allowed. The compiler rejects them with "error: unnamed package is not
allowed in named modules".
I am wondering what's going to happen with resources on the "unnamed path",
This would only make sense if it was likely to have to deal with two
Configuration classes in the same source file. How likely is that? OTOH,
short names make code easier to read.
Just my 2c.
Regards, Peter
On Sep 21, 2016 8:19 AM, "Stephen Colebourne" wrote:
> I had the
Hi all,
I have a follow-up question on the new proposal on #ResourceEncapsulation,
which states:
> The effective package name of a resource named by the string
> `"/foo/bar/baz"`, e.g., is 'foo.bar'.
The idea of using resource paths as "effective package names" definitely
makes sense to me.
I had the same thought while watching the slides. Configuration is
certainly a class name that exists other places, and would benefit
from being ModuleConfiguration. Layer is less common, so not worried
so much. Exceptions with "Module" in the name like
ModuleNotFoundException would also be
On 09/21/2016 12:50 AM, Jochen Theodorou wrote:
On 12.09.2016 17:08, Mark Reinhold wrote:
Issue summary
-
#ReflectiveAccessToNonExportedTypes --- Some kinds of framework
libraries require reflective access to members of the non-exported
types of other modules; examples
+1
I'd also propose FindException -> ModuleNotFoundException
Richard
On 09/21/2016 12:58 PM, Remi Forax wrote:
I agree.
And Layer should also be called Module Layer.
Remi
On September 21, 2016 12:36:51 PM GMT+02:00, Kasper Nielsen
wrote:
Hi,
I was wondering if there
I agree.
And Layer should also be called Module Layer.
Remi
On September 21, 2016 12:36:51 PM GMT+02:00, Kasper Nielsen
wrote:
>Hi,
>
>I was wondering if there are any reasons for why these 3 classes in
>java.lang.Module
>
>Configuration
>FindException
>ResolutionException
Hi,
I was wondering if there are any reasons for why these 3 classes in
java.lang.Module
Configuration
FindException
ResolutionException
Does not include the name Module?
I especially am not to fond of the very generic Configuration name in my
source code would much prefer something like