[MJAR-238] Allow setting of module main class

• Type: Improvement
• Status: Closed
• Priority: Minor
• Resolution: Fixed
• Fix Version/s: 3.1.2
• Environment: Java9 build 9+176, MacOS
• Assignee: Enrico Olivelli
• Reporter: Machiel Groeneveld
• Created: 11/Jul/17 07:43
• Updated: 11/Sep/21 14:27
• Resolved: 17/Jan/19 18:29

Description

When a Java9 module is created using the maven-jar plugin, setting the manifest/mainclass does not set the module main class. Therefore the module is not executable without specifying the main class. Executing the module using java -m domain.app gives the following error:
module jigsaw.app does not have a MainClass attribute

According to the module specification a module (jar) can have a main class set. If I understand correctly it's inside the module-info.class as a property called ModuleMainClass

When using the JDK9 jar command it will update the jar and the module-info.class.

  -e, --main-class=CLASSNAME The application entry point for stand-alone
                             applications bundled into a modular, or executable,
                             jar archive

I guess it would make sense to have this as a separate configuration item since the mainclass entry in the manifest file is not needed in 'module mode' and vice versa.

If this is a duplicate of another issue, please close this one, I couldn't find any existing issues related to this.

Issue Links

• links to: #67 Add ability to specify module version and main class
• links to: GitHub Pull Request #2
• mentioned in: Page Loading...