maven-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From GitBox <>
Subject [GitHub] [maven-shade-plugin] raphw commented on pull request #59: MSHADE-373: adds a property to skip manifest transformer application when transforming a source file.
Date Thu, 02 Jul 2020 14:43:58 GMT

raphw commented on pull request #59:

   I don't think that that's my problem: I shade the actual jar and the source jar. Doing
so, I want to add a class-bundle name which I do not want to be part of the original, unshaded
jar. I neither want it to be part of the source jar since the bundle name identifies the jar
file uniquely within OSGi. If a tool (Exclipse in this case) depends on both jars, the actual
jar and the source jar, on it's OSGi class path, this resolution will fail since both jars
specify the same unique name. I need to be able to inject this unique name into the shaded
jar file without also injecting it into the shaded source jar.
   Is there a better way to do this? The problem is reproduced here:
and breaks Eclipse.

This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

For queries about this service, please contact Infrastructure at:

View raw message