The JEE packager in ACF 2023 Enterprise is straight-up broken. It will NOT create a functioning war file. I have been going back-and-forth with Adobe support for a month and they still don't even understand the problem, let alone come anywhere close to fixing it.
😢 1
d
Dave Merrill
03/24/2025, 7:42 PM
Paging @Mark Takata (Adobe), maybe he can help.
m
Mark Takata (Adobe)
03/24/2025, 7:54 PM
Traveling currently but I’ll do what I can
👍 1
j
Jason Dean
03/24/2025, 8:14 PM
Oh, maybe I should be happy that ACF 2023 generates a broken file. ACF2025 doesn't generate a file at all. It says it does, but it doesn't.
s
SteveJ
03/25/2025, 3:08 PM
hmmm - that's worrying. creating WAR files is the only way we've found to submit our CF code to Veracode for a static scan.
j
Jason Dean
03/25/2025, 4:15 PM
@SteveJ How do you create your war files? I am referring to using the JEE packager within the CFAdmin. It is broken (in different ways) in my testing in both ACF 2023 and ACF 2025.
s
SteveJ
03/25/2025, 4:55 PM
we load the Docker image and then run the /opt/coldfusion/cfusion/bin/cfcompile.sh script. it's an automated Jenkins script so that our code gets scanned every night.
SteveJ
03/25/2025, 4:57 PM
i guess that only compiles it - once we have the compiled class files we run this to create the WAR file:
/usr/lib/jvm/jdk-11/bin/jar -cvf /opt/WAR/FUELoct.war /opt/compiled/FUEL/*