[ https://issues.apache.org/jira/browse/MJAR-238?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16477264#comment-16477264 ]
Leonardo Zanivan edited comment on MJAR-238 at 5/16/18 11:37 AM: ----------------------------------------------------------------- [~rfscholte], ASM 6.1.1+ has support for Java 9 and 10. Please also support setting module version. Example: {code:java} jar --update --file=myapp.jar --main-class=Main --module-version=1.0.0{code} was (Author: panga): [~rfscholte], ASM 6.1.1+ has support for Java 9 and 10. > Allow setting of module main class > ---------------------------------- > > Key: MJAR-238 > URL: https://issues.apache.org/jira/browse/MJAR-238 > Project: Maven JAR Plugin > Issue Type: Improvement > Environment: Java9 build 9+176, MacOS > Reporter: Machiel Groeneveld > Assignee: Robert Scholte > Priority: Minor > > 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. > {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 (v7.6.3#76005)