Details
Assignee
UnassignedUnassignedReporter
Zac SpitzerZac SpitzerNew Issue warning screen
Before you create a new Issue, please post to the mailing list first https://dev.lucee.org
Once the issue has been verified, one of the Lucee team will ask you to file an issue
Priority
New
Details
Details
Assignee
Unassigned
UnassignedReporter
Zac Spitzer
Zac SpitzerNew Issue warning screen
Before you create a new Issue, please post to the mailing list first https://dev.lucee.org
Once the issue has been verified, one of the Lucee team will ask you to file an issue
Priority
Created 26 December 2022 at 12:30
Updated 26 December 2022 at 12:30
Let’s change / improve the lucee-forgebox build process
https://github.com/Ortus-Lucee/forgebox-cfengine-publisher
rather than creating the forgebox files, which bundle the lucee war files with some json, I'd rather the forgebox publisher use the normal Lucee war distribution, thus we can avoid creating and storing two files, totaling 100mb that are only ever used once, as far as i can tell?
the forgebox build process can then add the required forgebox json metadata itself
the light war, it just the fat war with the *.lex files removed and the "Require Extension" section from the core manifest
https://github.com/lucee/lucee-data-provider/blob/master/update/S3.cfc#L365
I would then move the war generation (light.jar and express .zip too) into the main Lucee Github Action