http://coldfusion.com logo
Join Slack
Powered by
Good morning, all! The past couple of `box` start...
# box-products
r
Good morning, all! The past couple of 
box
startups have been showing the following. Is this of any concern?
Copy code
Ryan@Ryan-Y70 MINGW64 ~
$ box
The module (commandbox-cfformat) cannot be loaded as it does not have a ModuleConfig.cfc in its root. Path Checked: F:\code\.CommandBox\cfml\modules/commandbox-cfformat
I have checked the directory and confirmed that the ModuleConfig.cfc file is missing. Do I need to somehow pull this again in some way? This is the latest version.
I forced an upgrade of CommandBox and the same issue remains.
Also, after upgrading, the jline regression came back that we resolved last September. https://github.com/jline/jline3/pull/704
Added the previous jline-3.20.1-SNAPSHOT.jar into the .CommandBox/lib directory and the regression is fixed, again. Back to the original issue now with commandbox-cfformat.
b
Upgrading CommandBox isn't going to affect cfformat
r
noticed that 🙂
b
Just uninstall and reinstall cfformat
r
ok, will do that, thank you
b
Not quite following what you're saying about jline
I thought I have the latest jline release in the CommandBox bleeding edge
If you're seeing the latest jline is broken, please open a ticket with them.
r
I'm not sure. One of the last comments you mentioned is that you were going to hold off until they have a stable version or something. Not sure if you actually included a stable version.
b
Do you have a link to the ticket to refresh my memory?
r
the link above
wait
cfformat is back to normal. Thanks, @bdw429s
b
@ryan I guess I'm confused because I thought that version WAS included in the CommandBox bleeding edge
That ticket above says it's part of milestone 
3.21.0
and the bleeding edge of CommandBox is using that version of JLine!
I just double checked, and my 
.CommadnBox/lib
folder as the jar
Copy code
jline-3.21.0.jar
inside of it
If you don't have that jar, I'm guessing you're not on the bleeding edge of CommandBox
r
Should I be able to see the 
3.21.0
jline file with .CommandBox/lib?
b
I would hope so
I mean, there's going to be SOME file in there with the text "jline" in the name
And there's only about 17 files
So ... this shouldn't hard to figure out 😉
r
lol, I don't see it in there
b
If you don't have a JLine jar, CommandBox won't run, lol
r
and I have a ton of previous versions of jline in there
b
perhaps you're looking in the wrong folder
and I have a ton of previous versions of jline in there
So you do have a Jline jar?
I'm confused
Are you saying there are or are not jars with "jline" in the name present
Because I'm hearing both
r
however, none of them beginning with 
3.21
or highrer
b
Let's back up-- what version of CommandBox do you have installed?
r
The 
3.20.1-SNAPSHOT.jar
was not present in the lib folder, nor was 
3.21
I copied & pasted 3.20.1-SNAPSHOT.jar back in to make it work
b
So you DO have versions of Jline present
If you have an old version of Jline, then that's obviously the reason you have the issue
The question is WHY you have olders versions of JLine
Which is why I asked what version of CommandBox you have installed
r
when we were testing in September
b
I've mentioned that the latest JLine is only on the bleeding edge of CommandBox so if you have any other version of CommandBOx, then it would be expect3ed that you would not have the latest JLine jar
But the fact that you have several older versions of Jline you've manually placed in the folder seems troubling
If you haven't renamed the file extension to remove the 
.jar
then they are all being loaded
r
but they are labeled with 'X' in the extension like '.jarX' except for the 3.20.1 snapshot
b
OK, that's good
but what version of CommandBox are you usiing?
r
just upgraded today to 
5.4.2+00453
b
Ok, so is that the bleeding edge of CommandBox?
I'll give you a hint (beside the fact there's no prerelease identifier in the version number). Here is the version of JLine that shipped with CommandBox 5.4.2 https://github.com/Ortus-Solutions/commandbox/blob/v5.4.0/build/build.properties#L23
r
ok, thanks
I assumed that 
box upgrade
was capturing the latest. It must be the latest stable and not bleeding edge. Thanks
b
You can update to the bleeding edge, but you must use the 
--latest
flag with the command
r
I figured that out, thank you
b
Otherwise, you'll get the stable version, unless you're already on the latest (bleeding edge)
Hopefully CommandBox 5.5 will ship very very soon (with the latest JLine). I've just been sitting around waiting for Lucee 5.3.9 to finally go gold.
👍🏼 1
And as I've found, getting held up on Lucee to release before I can release is never a quick game to play 😕
They average about 8 months between each release
r
it's a hurry-up-and-wait game, unfortunately.
b
You can help test out 5.5.0-alpha in the mean time. It's pretty stable
r
upgrading to it
You are probably aware of this warning already.
Copy code
Libraries initialized
updated f:\code\.CommandBox!
WARNING: sun.reflect.Reflection.getCallerClass is not supported. This will impact performance.
so far, so good with 
5.5.0
! Thank you.
b
It's a Lucee bug
👍🏼 1
They make their own OSGI bundles and don't do them right so it pisses off the new version of Log4j 😕
r
that's a bummer..
that's something you are waiting as a correction in Lucee's new version?
b
Yes
The ticket is marked resolved, but you can see from the comments on it today it's still seemingly a work in progress
👀 1
The log4j updates came with a whole slew of stupid new console messages that appeared, This is the last one to take care of
r
awesome
4 Views
Open in Slack
PreviousNext
Powered by