maven-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Robert Scholte (Jira)" <>
Subject [jira] [Commented] (MJAR-238) Allow setting of module main class
Date Sun, 08 Sep 2019 14:16:00 GMT


Robert Scholte commented on MJAR-238:

[~gunterze] that's done during compilation, see

> Allow setting of module main class
> ----------------------------------
>                 Key: MJAR-238
>                 URL:
>             Project: Maven JAR Plugin
>          Issue Type: Improvement
>         Environment: Java9 build 9+176, MacOS
>            Reporter: Machiel Groeneveld
>            Assignee: Enrico Olivelli
>            Priority: Minor
>             Fix For: 3.1.2
>          Time Spent: 10m
>  Remaining Estimate: 0h
> 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 gives the following error:
> _module 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.
> {noformat}
>   -e, --main-class=CLASSNAME The application entry point for stand-alone
>                              applications bundled into a modular, or executable,
>                              jar archive
> {noformat}
> 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.

This message was sent by Atlassian Jira

View raw message