[
https://issues.apache.org/jira/browse/MSHADE-236?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15828591#comment-15828591
]
Robert Scholte commented on MSHADE-236:
---------------------------------------
bq. When building jars with Maven, by default you will get the following
entries: /META-INF/maven/${groupId}/${artifactId}/pom.properties and
/META-INF/maven/${groupId}/${artifactId}/pom.xml. When shading, all these files
will also end up in the shaded jar.
I guess this answers your question.
> Document artifacts that went into the shade.
> --------------------------------------------
>
> Key: MSHADE-236
> URL: https://issues.apache.org/jira/browse/MSHADE-236
> Project: Maven Shade Plugin
> Issue Type: New Feature
> Affects Versions: 2.4.3
> Reporter: Phil Wilkinson
> Priority: Minor
>
> Hi I asked a question a while ago on
> http://stackoverflow.com/questions/38096958/how-do-i-embed-artifact-information-in-maven-shaded-jar
> basically I wanted to be able to look at the shaded jar that's being used by
> a custom and figure out exactly what versions of the artifacts went in to it.
> It looks this isn't supported currently by the plugin and I think it would be
> a nice feature.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
