[
https://issues.apache.org/jira/browse/MNG-6454?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17085197#comment-17085197
]
Robert Scholte commented on MNG-6454:
-
No, this fits in the current pom model 4.0.0. Still a challenge, but easier to
solve then some think of the MRJARs requirements.
The support for mutlirelease jar (which actually needs to be generalized
because it is too Java specific) will likely require changes in the pom. e.g
you cannot talk about THE source directory anymore, every source directory
needs its own context (source/target/release, output folder).
With MNG-6454 in place, you'll have
https://maven.apache.org/plugins/maven-compiler-plugin/multirelease.html Maven
MultiModule 2.0 (no need for the assembly-plugin to assemble the jar)
> Introduce option to allow non-pom packaging types to also support the
> modules-tag
> -
>
> Key: MNG-6454
> URL: https://issues.apache.org/jira/browse/MNG-6454
> Project: Maven
> Issue Type: New Feature
>Reporter: Robert Scholte
>Priority: Major
> Labels: intern, multirelease
>
> While working on the multirelease jars I noticed we're missing a feature in
> Maven. At JCrete after talking with [~sanne] he had a similar request for a
> different reason. In his case it is about having a jar where all Drivers are
> optional, so developers only have to add this jar. However, it would be great
> it code could be isolated per Driver.
> The idea is to allow packaging:jar to specify modules in the pom. These
> submodules follow the normal lifecycle, but are never installed or deployed.
> Instead the root-project will embed these files in the main jar.
> To support this, Maven first of all recognize if modules are allowed for a
> specific packaging type. The
> {{org.apache.maven.artifact.handler.ArtifactHandler}} looks close, but that
> should be about artifacts (dependencies). So most likely we need a new
> ProjectHandler here.
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
