On 30/04/2016 20:49, Andrej Golovnin wrote:
For now, the implementation only treat files on the module path ending in ".jar" as candidate modular JAR or automatic modules. You will get an unrecognized module error with `java -modulepath foo.JAR ..` for example. You'll see the same in the tools. This has not changed in this refresh.: I have a stupid question: Is it guaranteed that entry.getFileName().toString always returns a value in lowercase?
-Alan