It looks like the 6.2.1.57 release aren't getting all the Docker builds posted. Or maybe the tags weren't updated since everything is Tomcat 11 only.

any reason not to be using tomcat 11?

nope. Was just expecting a

6.2.1.57-SNAPSHOT-lite

,

6.2.1.57-SNAPSHOT

and

6.2.1.57-SNAPSHOT-nginx-lite

tag. (also, this happened a while ago, but the -zero tag rolled off somewhere too)

yeah, i see some of the versions are missing https://hub.docker.com/r/lucee/lucee/tags?name=6.2.1.57 vs https://hub.docker.com/r/lucee/lucee/tags?name=6.2.1.48 (and zero is missing there too

yeah, -zero dropped off in the 6.0.x train somewhere. But the others should be there at the least.

I just noticed there is no JDK docker release of 6.2. The JDK version is needed for luceedebug support.

bug filed! https://luceeserver.atlassian.net/browse/LDEV-5396 @justincarter are you around?

Thanks will check out. I tried commandbox with lucee 6.2.0.321 plus/minus luceedebug yesterday , but kept getting an error like “ lucee.transformer.bytecode.statement.tag.TagComponent are in unnamed module of loader org.apache.felix.framework.BundleWiringImpl” from the hibernate ORM initialization. (Everything worked fine if I didnt use Docker but ran command box and lucee natively ). Can post separately with details but wondering if you encountered something similar prior to these new docker builds?

not sure, please fire off a post, the stacktrace will be very helpful

Sorry for being daft, but how do I tell what snapshot release a ticket/fix might be included in? It looks like the change logs are just for RCs and stable releases. I don’t see anything on the actual ticket (e.g. LDEV-5381). I’m sure I’m missing something silly. 😬

Looks like the fix version hasn't been assigned yet, if you look at the last commit, it will include a version bump in pom.xml

Awesome, very helpful. Thanks!