But since jar vs module both require a manifest entry or command-line argument
to specify the exact thing to “run”, can’t they both inspect the opportunity to
act like the other form of command line, and then do the right thing?
The problem is that “uber JARs” (which I have used for decades at
On 05/03/2018 13:58, Gregg Wonderly wrote:
Will java -jar note that the argument is a module and help the user understand
how to invoke it, or will it just complain about a missing main-class:
attribute? From a practical perspective, why does it matter and demand a
different command line? Wh
Will java -jar note that the argument is a module and help the user understand
how to invoke it, or will it just complain about a missing main-class:
attribute? From a practical perspective, why does it matter and demand a
different command line? What happens when you double click on a module?
On 05/03/2018 10:43, Bernard Amade wrote:
thanks for your help
just curious about this internal information:
---
"ModuleMainClass" attribute. Note that this is a class file attribute, not an
attribute that you put in the main manifest of a JAR fi
On 05/03/2018 09:54, Bernard Amade wrote:
Hello all
the doc in https://docs.oracle.com/javase/9/docs/specs/jar/jar.html
lists for Main-Class entry in jars:
"attribute defined for stand-alone applications: This attribute is used by stand-alone
applications that are bundled into executable jar fil
Hello all
the doc in https://docs.oracle.com/javase/9/docs/specs/jar/jar.html
lists for Main-Class entry in jars:
"attribute defined for stand-alone applications: This attribute is used by
stand-alone applications that are bundled into executable jar files which can
be invoked by the java runtime
