[
https://issues.apache.org/jira/browse/MSHADE-316?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16816031#comment-16816031
]
Robert Scholte commented on MSHADE-316:
---------------------------------------
So if I read this correctly, you have control which classes under
target/classes should be part of the minified jar? What's the idea behind this?
Shouldn't simply all these files be added?
> 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
> Priority: Major
> Time Spent: 10m
> 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)
