maven-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Blake (JIRA)" <>
Subject [jira] [Created] (MSHADE-230) Cannot specify custom manifest file in a shaded jar.
Date Thu, 07 Jul 2016 22:38:10 GMT
Blake created MSHADE-230:

             Summary: Cannot specify custom manifest file in a shaded jar.
                 Key: MSHADE-230
             Project: Maven Shade Plugin
          Issue Type: Bug
    Affects Versions: 2.4.3
            Reporter: Blake

When a project uses the maven-jar-plugin, it's easy to include a custom (hand written) manifest
file in the jar, but I can't find a way to do the same thing with maven shade. How can I use
my own manifest file while using the "maven-shade-plugin"? 

Basic details:

My custom manifest file is located in "src/main/resources/META-INF/MANIFEST.MF". Shade is
not including my file, instead it is being replaced in the final jar with a default manifest

The reason I need a custom manifest file is to specify some JavaBeans classes in my manifest,
for a swing component library. Multiple JavaBeans classes should be specified in the manifest
file in the following format, as described here:
 (Note that the order of these lines is important. The ManifestResourceTransformer could add
the lines, but they get added out of order.)

Name: SomeBean1.class
Java-Bean: True
Name: SomeBean2.class
Java-Bean: True
Name: SomeBean3.class
Java-Bean: True

The POM file for this project is long, so I won't paste the whole thing here. However, the
current full POM for this project can be seen on github at this link:

Please see the list of (unsuccessful) solutions I have tried (and additional details), which
are located here.

Thank you.

This message was sent by Atlassian JIRA

View raw message