witty-family-13337
03/02/2022, 4:17 PMreference.conf
file at the top-level, when trying to pack the code that needs Akka using deploy_jar
we get file colissions (as it finds the same file name more than once).
So this either requires having a target that allows to package a thin jar, or use something similar to what SBT does (in sbt-assembly
) by having Merge strategies, not sure if anyone here has thought on other ways of solving this.enough-analyst-54434
03/02/2022, 4:45 PMfast-nail-55400
03/02/2022, 5:19 PMjvm_war
target type). dependencies in the WAR are not unpacked so no collisions would occur from an unpacking.fast-nail-55400
03/02/2022, 5:19 PMwitty-family-13337
03/02/2022, 9:12 PMwitty-family-13337
03/02/2022, 9:13 PMwitty-family-13337
03/02/2022, 9:14 PMfast-nail-55400
03/02/2022, 9:15 PMfast-nail-55400
03/02/2022, 9:16 PMfast-nail-55400
03/02/2022, 9:16 PMfast-nail-55400
03/02/2022, 9:17 PMthe WAR gets close, but it’s a runnable JAR what I’m thinking of. More like just contents of the WEB-INF/classes folder from the WARdo you still want third-party jars unpacked in this runnable jar?
fast-nail-55400
03/02/2022, 9:18 PMwitty-family-13337
03/02/2022, 9:23 PMreference.conf
file. Or a thin runnable jar with only 1st class compiled classes.witty-family-13337
03/02/2022, 9:24 PMwitty-family-13337
03/02/2022, 9:24 PMwitty-family-13337
03/02/2022, 9:25 PMfast-nail-55400
03/02/2022, 9:33 PMso, it’s either a fat jar with some options for rules to merge files when collisions show ups (due to the Akka jars all having awe would need to port the merging code from Pants v1 into v2file. Or a thin runnable jar with only 1st class compiled classes.reference.conf
fast-nail-55400
03/02/2022, 9:33 PMfast-nail-55400
03/02/2022, 9:35 PMWEB-INF/classes
will be empty as first-party classfiles are emitted as their thin jars in WEB-INF/lib
alongside third-party jarswitty-family-13337
03/03/2022, 7:55 AMfast-nail-55400
03/03/2022, 1:20 PMClasspathEntry
instances where first-party or third-party.