You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Bradley Turek (JIRA)" <ji...@apache.org> on 2017/11/10 22:02:00 UTC
[jira] [Created] (MSHADE-266) Make more clear that
ManifestResourceTransformer can add *any* entry
Bradley Turek created MSHADE-266:
------------------------------------
Summary: Make more clear that ManifestResourceTransformer can add *any* entry
Key: MSHADE-266
URL: https://issues.apache.org/jira/browse/MSHADE-266
Project: Maven Shade Plugin
Issue Type: Improvement
Affects Versions: 3.1.0
Environment: Documentation on Web
Reporter: Bradley Turek
Priority: Minor
I suggest that it be made blatantly clear that the ManifestResourceTransformer can add any name-value pair.
Maybe by example. What if we add the following?
{quote}
h2. Setting Manifest Entries with the ManifestResourceTransformer
The ManifestResourceTransformer allows existing entries in the MANIFEST to be replaced and new entries added.
Manifest entries are added using the following format:
{{<Name>Value</Name>}}
For example, having a configuration of
{code:xml}
<transformer implementation=
"org.apache.maven.plugins.shade.resource.ManifestResourceTransformer">
<manifestEntries>
<Main-Class>com.foo.Main</Main-Class>
<Implementation-Version>1.5.0</Implementation-Version>
<Arbitrary-Entry>arbitrary value</Arbitrary-Entry>
</manifestEntries>
</transformer>
{code}
will result in a {{MANIFEST.MF}} of
{code}
...
Main-Class: com.foo.Main
Implementation-Version: 1.5.0
Arbitrary-Entry: arbitrary value
...
{code}
Here's a full example configuration with, the following sample entries and values
the Main-Class entry to the value of the app.main.class property,
the X-Compile-Source-JDK entry to the value of the maven.compile.source property and
the X-Compile-Target-JDK entry to the value of the maven.compile.target property.
...
{quote}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)