[jira] [Updated] (MSHADE-230) Cannot specify custom manifest file in a shaded jar.
[ https://issues.apache.org/jira/browse/MSHADE-230?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Elliotte Rusty Harold updated MSHADE-230: - Priority: Minor (was: Major) > Cannot specify custom manifest file in a shaded jar. > > > Key: MSHADE-230 > URL: https://issues.apache.org/jira/browse/MSHADE-230 > Project: Maven Shade Plugin > Issue Type: New Feature >Affects Versions: 2.4.3 >Reporter: BlakeTNC >Priority: Minor > > 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 file. > 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: > http://www.ewebprogrammer.com/java-beans/module3/javabeans-manifest-file.jsp > (Note that the order of these lines is important, as well as the empty lines > between them. The ManifestResourceTransformer could add the lines, but they > get added out of order and without the empty lines.) > 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: > https://github.com/LGoodDatePicker/LGoodDatePicker/blob/master/Project/pom.xml > See the list of (unsuccessful) solutions I have tried (and additional > details), which are located here. > http://stackoverflow.com/questions/38243222/how-can-i-specify-a-custom-manifest-mf-file-while-using-the-maven-shade-plugin > Thank you. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (MSHADE-230) Cannot specify custom manifest file in a shaded jar.
[ https://issues.apache.org/jira/browse/MSHADE-230?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Elliotte Rusty Harold updated MSHADE-230: - Issue Type: New Feature (was: Bug) > Cannot specify custom manifest file in a shaded jar. > > > Key: MSHADE-230 > URL: https://issues.apache.org/jira/browse/MSHADE-230 > Project: Maven Shade Plugin > Issue Type: New Feature >Affects Versions: 2.4.3 >Reporter: BlakeTNC >Priority: Major > > 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 file. > 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: > http://www.ewebprogrammer.com/java-beans/module3/javabeans-manifest-file.jsp > (Note that the order of these lines is important, as well as the empty lines > between them. The ManifestResourceTransformer could add the lines, but they > get added out of order and without the empty lines.) > 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: > https://github.com/LGoodDatePicker/LGoodDatePicker/blob/master/Project/pom.xml > See the list of (unsuccessful) solutions I have tried (and additional > details), which are located here. > http://stackoverflow.com/questions/38243222/how-can-i-specify-a-custom-manifest-mf-file-while-using-the-maven-shade-plugin > Thank you. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Updated] (MSHADE-230) Cannot specify custom manifest file in a shaded jar.
[ https://issues.apache.org/jira/browse/MSHADE-230?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] BlakeTNC updated MSHADE-230: Description: 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 file. 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: http://www.ewebprogrammer.com/java-beans/module3/javabeans-manifest-file.jsp (Note that the order of these lines is important, as well as the empty lines between them. The ManifestResourceTransformer could add the lines, but they get added out of order and without the empty lines.) 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: https://github.com/LGoodDatePicker/LGoodDatePicker/blob/master/Project/pom.xml See the list of (unsuccessful) solutions I have tried (and additional details), which are located here. http://stackoverflow.com/questions/38243222/how-can-i-specify-a-custom-manifest-mf-file-while-using-the-maven-shade-plugin Thank you. was: 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 file. 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: http://www.ewebprogrammer.com/java-beans/module3/javabeans-manifest-file.jsp (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: https://github.com/LGoodDatePicker/LGoodDatePicker/blob/master/Project/pom.xml See the list of (unsuccessful) solutions I have tried (and additional details), which are located here. http://stackoverflow.com/questions/38243222/how-can-i-specify-a-custom-manifest-mf-file-while-using-the-maven-shade-plugin Thank you. > Cannot specify custom manifest file in a shaded jar. > > > Key: MSHADE-230 > URL: https://issues.apache.org/jira/browse/MSHADE-230 > Project: Maven Shade Plugin > Issue Type: Bug >Affects Versions: 2.4.3 >Reporter: BlakeTNC > > 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 file. > 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: > http://www.ewebprogrammer.com/java-beans/module3/javabeans-manifest-file.jsp > (Note that the order of these lines is important, as well as the empty lines > between them. The ManifestResourceTransformer could add the lines, but they > get added out of order and without the empty lines.) > 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: > http
[jira] [Updated] (MSHADE-230) Cannot specify custom manifest file in a shaded jar.
[ https://issues.apache.org/jira/browse/MSHADE-230?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] BlakeTNC updated MSHADE-230: Description: 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 file. 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: http://www.ewebprogrammer.com/java-beans/module3/javabeans-manifest-file.jsp (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: https://github.com/LGoodDatePicker/LGoodDatePicker/blob/master/Project/pom.xml See the list of (unsuccessful) solutions I have tried (and additional details), which are located here. http://stackoverflow.com/questions/38243222/how-can-i-specify-a-custom-manifest-mf-file-while-using-the-maven-shade-plugin Thank you. was: 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 file. 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: http://www.ewebprogrammer.com/java-beans/module3/javabeans-manifest-file.jsp (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: https://github.com/LGoodDatePicker/LGoodDatePicker/blob/master/Project/pom.xml Please see the list of (unsuccessful) solutions I have tried (and additional details), which are located here. http://stackoverflow.com/questions/38243222/how-can-i-specify-a-custom-manifest-mf-file-while-using-the-maven-shade-plugin Thank you. > Cannot specify custom manifest file in a shaded jar. > > > Key: MSHADE-230 > URL: https://issues.apache.org/jira/browse/MSHADE-230 > Project: Maven Shade Plugin > Issue Type: Bug >Affects Versions: 2.4.3 >Reporter: BlakeTNC > > 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 file. > 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: > http://www.ewebprogrammer.com/java-beans/module3/javabeans-manifest-file.jsp > (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: > https://github.com/LGoodDatePicker/LGoodDatePicker/blob/master/Project/pom.xml > See the list of (unsuccessful) solutions I have tried (a
