Relating to the WEB-INF, I’ve run into some similar issues in the past. What I ended up doing (for this and other reasons) was switching the Lucee service to run under a specific user with full rights to the Lucee folder, read & execute rights to the folder that I keep all our sites in, and then, whenever I added a site, I ran a batch file that created the WEB-INF folder and applied modify rights to it for the custom lucee service user. Lucee then added the necessary files to that folder.
For lucee rollback, I just download the last-known-good .lco file and keep it handy to drop into [lucee]\tomcat\lucee-server\patches before a restart.
Of course, that wouldn’t help with Java. For Java, I don’t have any environmental variables set. For updating Java, I’ve used this process:
copy \lucee\jre to \lucee\jre_new (double-check user permissions)
delete all in jre_new
copy new jre files into jre_new
stop lucee
rename jre to jre-[version]
rename jre_new to jre
start lucee
To rollback, just stop lucee, reverse the renaming process, and restart lucee.
Also lucee 6 is a very different beast from 5. To see some of the issues I’ve been running into on Windows, check out these posts:
With the eventual dropping of Multi Mode, I’m not even sure each site will need a WEB-INF folder. But, I could be totally wrong about that. I still have much testing to do…