[
https://issues.apache.org/jira/browse/MCOMPILER-322?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mike Hogye updated MCOMPILER-322:
---------------------------------
Comment: was deleted
(was: Any chance this behavior could be made disable-able?
A non-standard Maven version string now causes the Java compile to fail, which
seems unnecessarily harsh. And because there is no way to turn this behavior
off, the only workaround for non-standard situations is to use an earlier
version of maven-compiler-plugin.
My team has a library that uses a non-standard Maven version string
(CURRENT-SNAPSHOT) for historical reasons having to do with our team workflow.
We know that non-standard version strings have always been discouraged, but we
are reluctant to screw with a workflow that has served us well for many years.)
> Set the JPMS module version
> ---------------------------
>
> Key: MCOMPILER-322
> URL: https://issues.apache.org/jira/browse/MCOMPILER-322
> Project: Maven Compiler Plugin
> Issue Type: Improvement
> Reporter: Plamen Totev
> Assignee: Robert Scholte
> Priority: Minor
> Fix For: 3.8.1
>
>
> The {{javac}} compiler (Java 9+) allows you to set the Java module version.
> It would be nice if the compiler plugin allows the user to set this value.
> The default value should be the project version.
> While it is true that the module version is not really used by JPMS, it would
> be nice if the modules created by Maven does have the version set. It could
> be useful for debugging for example.
>
> I'm not sure if we need the version only for the {{compile}} target or it
> useful for {{testCompile}} as well?
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
