You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The task binary.jvm calls the cli org.pantsbuild.tools.jar.Main. If the target of the task has a jar dependency that contains different entries with the same name (e.g: http://central.maven.org/maven2/org/seleniumhq/selenium/htmlunit-driver/2.27/htmlunit-driver-2.27.jar ) the cli will raise an exception : Unexpected problem writing target jar target.jar: java.util.zip.ZipException: invalid entry size (expected x but got y bytes)
and assuming the file is bug/BUILD type ./pants binary.jvm bug.
To find out the exact problem I used the following utils : unizip -t htmlunit-driver-2.27.jar -> you can see duplicated entry zip -d htmlunit-driver-2.27.jar "org/*" -> remove non problematic file to make next comand output more readable zipdetails htmlunit-driver-2.27.jar you can see that pom.properties do not have the same CRC (pom.xml is also duplicated but they are identical and this does not make the cli to crash)
The text was updated successfully, but these errors were encountered:
The task
binary.jvm
calls the cliorg.pantsbuild.tools.jar.Main
. If the target of the task has a jar dependency that contains different entries with the same name (e.g: http://central.maven.org/maven2/org/seleniumhq/selenium/htmlunit-driver/2.27/htmlunit-driver-2.27.jar ) the cli will raise an exception :Unexpected problem writing target jar target.jar: java.util.zip.ZipException: invalid entry size (expected x but got y bytes)
To reproduce use the following BUILD
and assuming the file is
bug/BUILD
type./pants binary.jvm bug
.To find out the exact problem I used the following utils :
unizip -t htmlunit-driver-2.27.jar
-> you can see duplicated entryzip -d htmlunit-driver-2.27.jar "org/*"
-> remove non problematic file to make next comand output more readablezipdetails htmlunit-driver-2.27.jar
you can see thatpom.properties
do not have the same CRC (pom.xml is also duplicated but they are identical and this does not make the cli to crash)The text was updated successfully, but these errors were encountered: