You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@maven.apache.org by "Hudson (JIRA)" <ji...@apache.org> on 2019/05/01 19:01:00 UTC

[jira] [Commented] (MSHADE-316) Explicit minijar includes

    [ https://issues.apache.org/jira/browse/MSHADE-316?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16831186#comment-16831186 ] 

Hudson commented on MSHADE-316:
-------------------------------

Build succeeded in Jenkins: Maven TLP » maven-shade-plugin » MSHADE-316 #2

See https://builds.apache.org/job/maven-box/job/maven-shade-plugin/job/MSHADE-316/2/

> Explicit minijar includes
> -------------------------
>
>                 Key: MSHADE-316
>                 URL: https://issues.apache.org/jira/browse/MSHADE-316
>             Project: Maven Shade Plugin
>          Issue Type: Improvement
>            Reporter: Markus Karg
>            Assignee: Robert Scholte
>            Priority: Major
>          Time Spent: 0.5h
>  Remaining Estimate: 0h
>
> Minijar currently respects includes, but these have a drawback: Once you defined an include, the _default includes_ are gone! But what you actually want to have when combining minijar with includes is just an "exception" to minijar's filtering, not a complete replacement of the default includes!
> So what we need to make this work intuitively is either "explicit minijar exceptions", or a "useDefaultIncludes=true" option that turns the notion from "replace default includes by the single given include" to "add the single given include ontop of the default includes".



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)