I *think* this issue was mentioned by someone on this mailing list not too long ago.
Please create a small project that reproduces this. Then create a jira and attach it. Then that project could be used as an IT. If you could create it as an IT (with a verify script) that would be even better. /Anders On Fri, Sep 14, 2012 at 8:38 PM, Jeffrey Brekke <[email protected]> wrote: > I've checked the issues and didn't see this particular problem documented. > When the shade plugin generates a jar comprised of all the classes, the > META-INF/MANIFEST.MF directory and file are lowercased. The specifications > as I have read them state the case doesn't matter, but along with the lower > case meta-inf/manifest.mf, there is also and upper-case META-INF/ directory > with all the maven pom files in the jar. I think this situation where > there is a lowercase and uppercaser meta-inf directory is the issue and > causes the manifest.mf file to be unreadable in these jars ( it looks as if > there isn't one ). > > Could anyone else confirm this situation, or know if this is a known issue? > > -- > Jeffrey D. Brekke > Wisconsin, USA > > [email protected] > [email protected] > [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
