Why would CommandBox keep using lucee even though ...
# box-productsl
laslo7
02/02/2022, 5:51 PMWhy would CommandBox keep using lucee even though I am telling it to use the latest ACF?
b
bdw429s
02/02/2022, 5:51 PM@laslo7 Please be more specific in your question 🙂
bdw429s
02/02/2022, 5:51 PMWhat are your
server.jsonl
laslo7
02/02/2022, 5:51 PMCommandBox> start cfengine=adobe@2021.0.3+329779
b
bdw429s
02/02/2022, 5:51 PMAlso show the output of a
--verbosel
laslo7
02/02/2022, 5:54 PMserver.json:
{
"app":{
"cfengine":"adobe@2021.0.3+329779"
},
"jvm":{
"heapSize":512,
"args":""
},
"name":"test1",
"openBrowser":true
}
laslo7
02/02/2022, 5:55 PMIt says it is:
Adobe [5.3.7+41]
b
bdw429s
02/02/2022, 5:58 PMHmm, never seen that. And the verbose start output?
l
laslo7
02/02/2022, 5:58 PMah I think I got an answer:
| You've asked for the engine [adobe@2021.0.3+329779] to be started,
| but this server home already has [lucee@5.3.7+47] deployed to it!
| In order to get the new version, you need to run 'server forget' on this server and start it again.
laslo7
02/02/2022, 6:00 PMThis looks different
laslo7
02/02/2022, 6:01 PMAnd that did it
laslo7
02/02/2022, 6:01 PMVerbose for the win
b
bdw429s
02/02/2022, 6:08 PMYep-- one of the many reasons I dislike using a hard-coded server home
bdw429s
02/02/2022, 6:09 PMI have a ticket in place to consider just throwing an error in this situation instead of ignoring
bdw429s
02/02/2022, 6:09 PMThe existing behavior catches a lot of people off guard- especially in our docker images which use a custom server home
l
laslo7
02/02/2022, 6:20 PMthanks for the help
👍 1