So again, please clarify what this change means with regard to what all ELSE is in the prerelease-which I'd just blogged about with more info, for those who have not yet checked it out: Lots more to the current CF2021, 2018 prerelease than folks may realizeīKBK, to be clear, one can "go ahead with Oracle JDK 11.0.11" right now, with CF2021 or 2018 (if on CF2018's update 2 or later, or even on CF2016 if on its update 8 or later-those are the updates that added Java 11 support for those CF versions). (It's also unclear from the prerelease if the new CFBuilder 2018 installer there was ALSO adding support for Big Sur.)
Then there's the new installer for CF to support MacOS Big Sur. While you may be choosing proceed with only the updates for CF20 (and without the Azul support, if that's what all this means), my point is that the updates alone wouldn't solve the other problems I just mentioned-or would they somehow? To be clear, the new installers not only were changing to support Azul but also to a) roll in all previous updates (especially important for CF2018), b) update both CF20 to run on Java 11.0.11 (vs they 11.0.1 that even CF2021 came out with), and c) update Tomcat to 9.0.43, aong other things. Is it that you'll roll all that out still with support for Azul? Or will you need to pull all the Azul-related changes out, but still proceed with the new installers and updates? But where does that put things, with regard to everything ELSE in the prerelease (with its new installers for CF20, new updates for CF20, updates for CFBuilder, and more)?
0 kommentar(er)
