I'm having an issue building the Lucee's 5.3.9.133...
# luceed
dswitzer
05/13/2022, 4:47 PMI'm having an issue building the Lucee's 5.3.9.133 source code.
The error I'm getting is:
Copy code
javax.servlet.ServletException: java.lang.RuntimeException: Lucee is missing the Bundle jar, javax.mail.activation:1.6.2.0000L, and has been prevented from downloading it. If this jar is not a core jar, it will need to be manually downloaded and placed in the {{lucee-server}}/context/bundles directory.b
bdw429s
05/13/2022, 4:53 PM@dswitzer That's likely just an issue on the bleeding edge of Lucee. The Lucee build is configured to disable Lucee's feature of auto-downloading missing OSGI bundles to help root out issues with lucee configuration at build time.
bdw429s
05/13/2022, 4:54 PMI would check Lucee's github actions and see if the latest builds are failing with the same error. if so, there's not much to do other than wait for them to fix it, or go fiddle with the build to stop disabling bundle downloads
z
zackster
05/13/2022, 4:55 PMyeah, but the build should download those at the start of the process. auto download is only disabled at later steps
b
bdw429s
05/13/2022, 4:56 PMRight, the error is being thrown when actually booting up the newly built Lucee to run the tests
bdw429s
05/13/2022, 4:57 PMA different step from that part of the build that actually creates the lucee jar and downloads the default OSGI bundles that get packaged with it
z
zackster
05/13/2022, 4:57 PMmaybe the maven cache is corrupted?
zackster
05/13/2022, 4:58 PMthe .m2 dir under your user profile?
zackster
05/13/2022, 4:58 PMgithub actions runs a fresh maven download for any PRs
b
bdw429s
05/13/2022, 4:58 PM@zackster Do you know right off where Lucee lists the bundles that are downloaded as part of the build? I know where the extensions for the core are listed, but not the OSGI bundles that get baked into the lucee jar.
z
zackster
05/13/2022, 4:59 PMthat's all from pom.xml
👍 1
zackster
05/13/2022, 4:59 PMthen it reads the manifest and copies it in
zackster
05/13/2022, 4:59 PMand warns when there's a mismatch
b
bdw429s
05/13/2022, 4:59 PMOk, so the first step would be to check and actually see if
javax.mail.activation:1.6.2.0000Lz
zackster
05/13/2022, 5:00 PMit is
👍 1
zackster
05/13/2022, 5:00 PMwas looking at that yesterday 🙂
b
bdw429s
05/13/2022, 5:01 PM@dswitzer The next step would be to inspect your lucee.jar that was built (it may still be in a temp folder, not sure) and see if that bundle is inside the bundles folder when you unzip the jar
bdw429s
05/13/2022, 5:01 PMI would assume not since it threw the error, but if it's in the POM, it sounds like it should be in the jar
d
dswitzer
05/13/2022, 5:20 PMI'm trying to compile the 5.3.9.133 release, so the code should be stable.
I just tried clearing the Maven cache using:
Copy code
mvn dependency:purge-local-repositorydswitzer
05/13/2022, 5:25 PMThat seems to be the issue. I've just submitted a pull request for the docs to add that information.
👍 1
z
zackster
05/13/2022, 5:26 PMcool, love it when a wild guess works out, thanks for the PR.
b
bdw429s
05/13/2022, 5:49 PMSweet, good chance. I'm sure I'll run into that myself some day 👍
z
zackster
05/13/2022, 5:49 PMPR merged
zackster
05/13/2022, 5:50 PMI just wanted to make cfml better and somehow ended up learning all this crap about java build systems!
d
dswitzer
05/13/2022, 5:53 PMThere is no simple build systems. No matter what the original goals are, they all seem to get really complicated over time and usually expect the users to already know everything about the tools! 😆
z
zackster
05/13/2022, 5:55 PMnow that 5.3.9 is out, 5.3.10 will be a minor release, I've done a shitload of work to make the 6.0 build process way nicer
2 Views