[
https://issues.apache.org/jira/browse/MNG-6293?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16227224#comment-16227224
]
Robert Scholte commented on MNG-6293:
-------------------------------------
We've defined a pattern a long time ago:
https://github.com/hboutemy/maven-jep238
It has the advantage that it already works with all current IDEs and that it
has isolation of unittests per version.
If you mean by out-of-the-box that is should be a single Maven Project, that
will be quite hard to do. It requires multiple executions of all the phases
between {{initialize}} until {{pre-package}} for every version, and package
should bring them all together. The architecture of Maven is not capable to do
that.
Also think of how developers should maintain different implementations of the
same class.
All together I don't think that MRJARs will be very popular, it comes with too
much pain. Having a solution is good enough for now.
As said, if we want to handle MRJARs properly we need to change the whole
architecture of Maven and right now I don't think taht's worth it. The pattern
is sufficient enough.
> Support multi-release JARs (JDK 9 feature)
> ------------------------------------------
>
> Key: MNG-6293
> URL: https://issues.apache.org/jira/browse/MNG-6293
> Project: Maven
> Issue Type: Improvement
> Reporter: Marcus Hirt
>
> In JDK 9 the concept of multi-release jars were introduced:
> http://openjdk.java.net/jeps/238
> It would be wonderful if maven supported building multi-release jars
> out-of-the-box. With the future high release-cadence of Java, this may become
> an increasingly important feature.
> Here is an interim solution:
> https://github.com/metlos/multi-release-jar-maven-plugin
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
