You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Elliotte Rusty Harold (Jira)" <ji...@apache.org> on 2020/04/13 16:13:00 UTC
[jira] [Commented] (MNG-6454) Introduce option to allow non-pom
packaging types to also support the modules-tag
[ https://issues.apache.org/jira/browse/MNG-6454?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17082447#comment-17082447 ]
Elliotte Rusty Harold commented on MNG-6454:
--------------------------------------------
I suspect we need a full proposal for multi-release jar handling first.
> 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)