Details
-
Bug
-
Status: Resolved
-
Normal
-
Resolution: Fixed
-
None
-
Correctness
-
Normal
-
Normal
-
User Report
-
All
-
None
-
Description
The problem is related to how we produce the dtest jar. That repackages all dependencies along with our classes in a single jar. Some dependencies might have digital signatures extracted into META-INF as, say, *.SF files. We need to remove them because they are invalid for the uber-jar we produce. Therefore, there are exclusions in zipgroupfileset operations, more or less like this:
<zipgroupfileset dir="${build.lib}" includes="*.jar" excludes="META-INF/*.SF"/>
However, this does not work as expected. The exclude attribute denotes jar files we don't want to repackage rather than filter on the content of the jar file. The new BouncyCastle jars include signatures in SF and DSA files, which all land in the final dtest.jar regardless of that filter.
The issue was discovered and explained by jlewandowski in CASSANDRA-17992
Attachments
Issue Links
- Discovered while testing
-
CASSANDRA-17992 Upgrade Netty on 5.0
- Resolved
- links to