oooh, testbox 5.0 is out <https://github.com/Ortus...
# cfml-general
z
šŸ‘šŸ¾ 1
@lmajano the 5.0.0 zip doesn't nest the files inside the zip as testbox anymore? also getting this with the Lucee build invalid component definition, can't find component [testbox.system.modules.globber.models.PathPatternMatcher]
l
Maybe I screwed up the build
Will check now
z
this doesn't look so bad, but if people depend on the directory structure
b
@zackster That was a really old behavior that I'm surprised we were still doing
So long as you are using CommandBox to install testbox, it is smart enough to detect the extra folder if it exists
l
image.png
Hmm, not sure what you mean then @zackster because, between 4 and 5 they are identical
plus, testbox has dependencies now
so you need COmmandBox
image.png
downloading it, won't give you the dependencies
z
image.png
globber is used by the coverageService, that could be lazy loaded, coverageEnabled doesn't default to true
this works
b
Is the file not present? It should be.
l
if you don't install TestBox with CommandBox you won't get the dependencies though
āœ… 1
is that what you are experiencing the missing modules?
z
yep
b
Yep, just like using Maven to install a jar vs just downloading the jar. You don't get dependencies if you bypass the package manager
z
well, it always worked before
b
lol, you got lucky before
z
i've been battling @lmajano on this for a while
b
This is no different than manually downloading a jar which previously didn't have any dependencies, but now it does.
l
yea sorry man, you got lucky
z
why not degrade gracefully
l
but we are using more little dependencies as we grow
b
Just do
Copy code
box install testbox
l
and that's why we use CommandBox to package it
so use commandbox to install it šŸ™‚
z
am i allowed to go all Brad here? you broke backward compat for an edge use case
"This works well for specs in a single test directory where they are flat, for example the TestBox project specs."
we burn enough CO2 during the lucee CI process already
a
100% onboard with TestBox using dependency management rather than encapsulating them all. Actually surprised it already worked with "just get TestBox". That's not been the install path for a while, has it?
And as it's 5.x not 4.x, it's allowed to break shit. Like install methods, right?
All that said... we don't use CommandBox, and won't be, so this is gonna make upgrading interesting, @lmajano I presume if I use
box install
to get the right files into the right place in the file system, there's no dependency on commandbox after that, right?
z
basically you can copy one file into the right folder and it works without box
a
Any file, Zac? Or are you prepared to throw me a bone here?
(and like... tell me which one šŸ˜‰
z
b
there's no dependency on commandbox after that, right?
Correct
a
Yeah cool. I used it to get the files, and slung them where they needed to be and we were all good