Ladicek commented on pull request #2: URL: https://github.com/apache/maven-jar-plugin/pull/2#issuecomment-912922679
Is there a way to disable this behavior? My case is that I need to compile one module in a multi-module Maven project with JDK 16. That module unfortunately includes `module-info.class`. I use Maven compiler plugin's `fork` and `executable` options to set path to JDK 16's `javac`, so that works nicely. Then the Maven JAR plugin builds a JAR, that works nicely too. But then if current JDK is newer than 8 but older than 16 (e.g. 11, which is an LTS), Maven JAR plugin tries to use the current JDK's `jar` tool to update the JAR file, which fails miserably (doesn't understand newer bytecode). -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: issues-unsubscr...@maven.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
