@lmajano can we please use threads? I've fixed the first bug, which was an recent regression when an extension has only one versions, which i believe was the one you are referring to, the 6.2.2.18 build addresses that https://github.com/lucee/Lucee/commit/b8921de16a53cbcdafb723d9807fa6023b18b8e7

oops, yes, sorry, got excited there

@lmajano for details about this issue please see https://luceeserver.atlassian.net/browse/LDEV-5598 in short there are 2 problems with that extension 1. have a OSGi bundle (jar) that does not export (“Export-package”) anything, that makes all classes in that bundle invisible to the outside world, this is like making a component with the constructor an all functions being private, i guess this was working in Lucee 5, because an older version of our OSGi engine Felix, did accept this somehow, to be honest it is strange to me that tis ever worked, it really should not. 2. the extension uses Log4j 1 and simply assume that it exists in the environment, problem is that we switched from log4j 1 to 2, means when a application needs version 1, it needs to provide the necessary bundles. i strongly suggest not to do that, log4j 1 should not be used in any production enviroment anymore, for logging you should really simply depend on Lucee itself like this

Log log = CFMLEngineFactory._getInstance_().getThreadConfig().getLog(“application”);

Thanks Micha!! 1. I will look into addding export packages, do you have any samples on this? 2. Hmm, this should not be used on this extension at all, will have to check why, because we removed this a long time ago and never use it