the compress extension is a Lucee required extension ... This is unrelated.

@Michael Offner You are incorrectly assuming that someone is using the full version of Lucee. In Lucee Light, the Compress extension is NOT part of Lucee. In my case, I was testing CommandBox on Lucee Light and I need a file-system based way to specify extensions for Lucee to load immediately on startup. I ended up having to hack apart the core.lco file from the Lucee jar, and add the compress extension to the manifest in the core as that was the only way to force the extension to load right away. That was significantly more work than just being able to use the deploy folder. Environment variables were out of the question in my case since I cannot control how box will be run and I cannot override arguments a user may specify. So my point above was not unrelated at all. It was exactly what this ticket was asking for.

i added the following function call at the first line of calling Lucee as a scripting engine (JSR223), to make sure/test if required extensions are existing right away.

Unless you were using Lucee Light as I was and adding the extension via the deploy folder, this was not a valid test of what I reported above. This was just testing the extensions loaded by the core.lco manifest fie, which we already know works.

deploy folder get now check in sync at the end of the startup process.

This looks very promising, thx. I will test it.

https://github.com/lucee/Lucee/commit/883014bc3cf6d34cd906e4d7f1e2c34ef0db477f

deploy folder get now check in sync at the end of the startup process.

@Brad Wood i added the following function call at the first line of calling Lucee as a scripting engine (JSR223), to make sure/test if required extensions are existing right away.

https://github.com/lucee/Lucee/commit/599f14eca443d5612f095f5be944d066621f758f#diff-15efaed19dd12175409dddfac5c094b7R30

they do. please also have in mind that extensions are not installed in a separate thread.

@Zac Spitzer the deploy folder already is read a second after startup, so that change is not necessary. so the point remains, can we install BEFORE startup ends?

@Brad Wood the compress extension is a Lucee required extension and because of that installed at startup and not after startup. If you think that is not the case, please raise a different ticket. This ticket is about extension inside the deploy folder, not required extensions. This is unrelated.

@Michael Offner One second is too long. I need the extensions to be ready immediately by the time Lucee is ready to run code or my code will fail. In the case of the CommandBox bootstrap, I load Lucee via JSR-223 and immediatley run the CFML bootstrap which instantly compiles code that requires extensions such as Compress so <cfzip> can compile. Any sort of "wait" period is unacceptable Lucee is simply not fully loaded until all extensions are installed and ready to go. This needs to be part of the Lucee bootstrap and cannot happen asynchronously.