(Still no definitive winner in the race to nickname ourselves, so I’m just randomly rotating nicknames with each post I write.)
Remember when I complained about the summer heat in my last release post? Time flies when you’re having fun, and now winter is fast approaching, which means we’re heading into the final stretch of the 2018 Lucee development schedule. We. Are. Ending. With. A. Bang. Actually–we’re ending with a Kabang, in case you missed the original post about Lucee 5.3’s beta release in May.
Today we’re announcing the first Release Candidate of 2018’s new minor version of Lucee–5.3 (5.3.1.87)
New minor versions are always an exciting time for us (second only to major versions, of course), because they allow us to tackle much bigger improvements to Lucee, and this is certainly true for 5.3, which includes a dizzying number of enhancements–everything from administrator improvements like new monitoring and debugging options, a new PDF engine, support for newer Java versions, etc.–along with, as always, lots of fixes and fine-tuning.
From the initial alpha builds, all the way through to this RC, the development team addressed a staggering 97 tickets, including a handful of tasks that had been nagging us (not to mention you!) for some time now. If you’ve been active with 5.3 releases, then here’s the final list of tickets resolved in the just-completed September sprint (which produced the 5.3 RC):
Also, if you haven’t been following the Lucee YouTube channel, the list of product videos is growing, including several related to 5.3 specifically.
5.3.1.87-RC went live on October 19, 2018, so please head over the the new-and-improved downloads site and grab a copy! Since this is a significant new release, we’re going to keep this one in RC status for a bit longer than planned, and we’ll finish 2018 with a final release of 5.3.1, along with a 5.3.2 Release Candidate. We welcome as much 5.3 testing and feedback as we can get from our beloved community!
Thanks so much for listening, and thanks as always for your interest in Lucee.
@Leftbower Pretty sure that includes Java 9, 10, and 11. I saw Micha talking about fixes he needed to put into place for Java 11 so I know he was testing it. Note there is some support for Java 9, 10, and 11 in 5.2.9 which I’ve tested on CommandBox but there’s at least one issue which is related to the automatic instrumentation that requires a JVM prop to be set.
I’ll get the full/final list, @Leftbower. Java 8 is a minimum requirement for 5.3 (1.7 no longer supported), and it definitely works with Java 9, but again I’ll list the full details here. cc @micstriit
there are currently some major blockers relating to when debugging is enabled with 5.3,
basically it’s often unusable after some requests depending on the nature of application
Using OpenJDK 11 and Tomcat 9.0.12, Lucee 5.3.2.8-SNAPSHOT produces the following apparently harmless warnings on startup:
WARNING: An illegal reflective access operation has occurred
WARNING: Illegal reflective access by org.apache.felix.framework.ext.ClassPathExtenderFactory$DefaultClassLoaderExtender (file:/C:/dev/lucee/WEB-INF/lib/lucee.jar) to method java.net.URLClassLoader.addURL(java.net.URL)
WARNING: Please consider reporting this to the maintainers of org.apache.felix.framework.ext.ClassPathExtenderFactory$DefaultClassLoaderExtender
WARNING: Use --illegal-access=warn to enable warnings of further illegal reflective access operations
WARNING: All illegal access operations will be denied in a future release
XMLParse in our application., obviously this support is gone
Eh ? I must have missed the depreciation discussion for a previous release as well.
Where was the huge flashing red letters in the change log that a core function was being removed ?
Have you told the CFDocs.org folks ?
No, XMLParse is still in there, the external jars have been removed and now it’s using the internal JVM xml parsing functionality. It hasn’t been removed as a function.
I moved ROOT to ROOT-TOMCAT and can access http://localhost:8080/ROOT-TOMCAT/
I downloaded WAR 5.3.2.8-SNAPSHOT, renamed to ROOT.war and dropped into webapps
In /usr/local/Cellar/tomcat/9.0.12/libexec/webapps/ROOT I can see the lucee default app files, inc WEB-INF
But http://localhost:8080 I get
HTTP Status 404 – Not Found
In http://localhost:8080/manager/html I notice Application path / is not running, so clicked start
and get this message
FAIL - Application at context path [/] could not be started
FAIL - Encountered exception [org.apache.catalina.LifecycleException: Failed to initialize component [org.apache.catalina.webresources.JarResourceSet@305a3a0c]]
Just a general question - what is the standard operating procedure for when a ticket is marked DEPLOYED but may still have issues?
In the case of LDEV-1984, I was able to reproduce the problem on 5.3.1.87 and the latest snapshot as well; I commented on the ticket but are we meant to open new tickets if the original one has been closed?
