[ https://issues.apache.org/jira/browse/MCOMPILER-446?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17737000#comment-17737000 ]
ASF GitHub Bot commented on MCOMPILER-446: ------------------------------------------ bdecaestecker opened a new pull request, #196: URL: https://github.com/apache/maven-compiler-plugin/pull/196 …ent if specified Following this checklist to help us incorporate your contribution quickly and easily: - [ ] Make sure there is a [JIRA issue](https://issues.apache.org/jira/browse/MCOMPILER) filed for the change (usually before you start working on it). Trivial changes like typos do not require a JIRA issue. Your pull request should address just this issue, without pulling in other changes. - [ ] Each commit in the pull request should have a meaningful subject line and body. - [ ] Format the pull request title like `[MCOMPILER-XXX] - Fixes bug in ApproximateQuantiles`, where you replace `MCOMPILER-XXX` with the appropriate JIRA issue. Best practice is to use the JIRA issue title in the pull request title and in the first line of the commit message. - [ ] Write a pull request description that is detailed enough to understand what the pull request does, how, and why. - [ ] Run `mvn clean verify` to make sure basic checks pass. A more thorough check will be performed on your pull request automatically. - [ ] You have run the integration tests successfully (`mvn -Prun-its clean verify`). If your pull request is about ~20 lines of code you don't need to sign an [Individual Contributor License Agreement](https://www.apache.org/licenses/icla.pdf) if you are unsure please ask on the developers list. To make clear that you license your contribution under the [Apache License Version 2.0, January 2004](http://www.apache.org/licenses/LICENSE-2.0) you have to acknowledge this by using the following check-box. - [ ] I hereby declare this contribution to be licenced under the [Apache License Version 2.0, January 2004](http://www.apache.org/licenses/LICENSE-2.0) - [ ] In any other case, please file an [Apache Individual Contributor License Agreement](https://www.apache.org/licenses/icla.pdf). > Compiler is crashing while setting JPMS module version > ------------------------------------------------------ > > Key: MCOMPILER-446 > URL: https://issues.apache.org/jira/browse/MCOMPILER-446 > Project: Maven Compiler Plugin > Issue Type: Bug > Affects Versions: 3.8.1 > Reporter: Bruno Medeiros > Priority: Major > > I have upgraded maven compiler plugin to 3.8.1 and I started getting this > error: > {code:java} > [ERROR] Failed to execute goal > org.apache.maven.plugins:maven-compiler-plugin:3.8.1:compile > (default-compile) on project common: Fatal error compiling: error: bad value > for --module-version option: 'local-SNAPSHOT' -> [Help 1]{code} > Because we set versions in pom to local-SNAPHOT (and use maven-version-plugin > when we actually realease to set a proper version), all our builds are > failing locally. > It seems javac does not like versions that do not have just alpha characters, > like ours local-SNAPHOT. > I thought about a few ways to fix that: > * Allow the use of --module-version to be optional through config > * Allow the version itself to be configurable > * Validate if the version is a valid version for --module-version and not > set it in case it is not > Let me know what you guys think, I can try to provide a PR with the given > solution. > -- This message was sent by Atlassian Jira (v8.20.10#820010)