New Extensions are not available

The lucee 7 administrator says, I can upgrade my mysql extension from 9.5 to 9.6 but the file is missing:

https://ext.lucee.org/com.mysql.cj-9.6.0.lex

If this is already known, please disregard my post.

New filename schema, ignore my post, its

https://ext.lucee.org/mysql-jdbc-extension-9.6.0.lex

Maven Time!

https://mvnrepository.com/artifact/org.lucee/mysql-jdbc-extension

org.lucee:mysql-jdbc-extension:9.6.0

As I already have a thread, maybe this is a bug:

I click on any extension (mysql or esapi or Lucee Documentation);

Bundles Info:

esapi.extension	            2.6.0.1	Aug 15, 2025	34.5kb		ESAPI extension	active
org.lucee.esapi
OSGI version of jar esapi	2.6.0.0	Mar 7, 2025	     442kb		ESAPI extension	active

Its a fresh build with docker. If I add the esapi 3.0.0.14 into the docker build, functions like Canonicalize() are missing.

Any ideas?

Lucee: 7.0.2.106
Tomcat: 11
Java: 21

If it’s a fresh build, how do you have the older esapi extension in there?

Sorry Zac, what do you mean by the older version? The 2.6 I add in my docker build?
Is Lucee 7 and esapi 2.6 not compatible?

I deleted the docker containers and images

root@610a3c6dc83b:/opt/lucee/server/lucee-server# ls -laR | grep esapi
-rw-r----- 1 root root    35328 Mar 17 07:35 esapi.extension-2.6.0.1.jar
-rw-r----- 1 root root   452466 Mar 17 07:35 org.lucee.esapi-2.6.0.0.jar
-rw-r----- 1 root root     6497 Mar 17 07:35 org.lucee.esapi-logger-1.0.6.jar
-rw-r----- 1 root root 22634 Mar 17 07:35 esapi-function.fld
root@610a3c6dc83b:/opt/lucee/server/lucee-server# ls -laR | grep 3.0.0
-rw-r----- 1 root root  2744753 Mar 17 07:35 org.lucee.pdfbox-3.0.0.RC101.jar
-rw-r----- 1 root root  1590809 Mar 17 07:35 org.lucee.pdfbox-fontbox-3.0.0.RC1.jar

Docker command:

ADD https://ext.lucee.org/esapi-extension-2.6.0.1.lex /opt/lucee/server/lucee-server/deploy/esapi-extension-2.6.0.1.lex

I did a docker system prune and have no more Ideas, what to check.

You were using an older extension matrix for your custom build, rather than updating to match the release extension matrix, i.e. the versions the MANIFEST.mf specifies, which is the known / supported versions.

We can’t retrospectively patch older extensions

1 Like

Got it now, thank you.

1 Like