always create light and zero

Description

this https://luceeserver.atlassian.net/browse/LDEV-3921 causes that locally zero and light not always get created. in past that was okay, because their only use, was to copy to S3, but now they are also needed locally to send to maven.

Also updating SNAPSHOT should be okay.

Environment

None

relates to

Activity

Show:

Pothys - MitrahSoft 20 March 2025 at 15:55

I have tested this ticket with Lucee version 6.2.1.77-RC. Now, the light build and zero build JARs are successfully created and uploaded to S3 Maven. It works fine now.

Zac Spitzer 14 March 2025 at 13:05

zero was actually light again, but it’s zero again

https://github.com/lucee/Lucee/commit/f5be1778d2be78c35eaf869a0f0bfd43075bccf5

Zac Spitzer 13 March 2025 at 11:01

Zac Spitzer 12 March 2025 at 14:17
Edited

I think this change went to far, we really shouldn’t be overwriting builds ever, even snapshots. This explains why in testing I’m often seeing mismatched versions, i.e. changes appearing in the previous version, making bisecting regressions even more difficult!

since this change, we are also kicking off docker builds repeatedly for already built images, which I just noticed (wasting CO2)

I’d like to propose we revert back to the following rules, if an artifact exists on s3, that’s final, no overwriting.

We can still build zero and light builds without uploading them to s3 for these sub snapshots on maven

https://oss.sonatype.org/content/repositories/snapshots/org/lucee/lucee/6.2.1.61-SNAPSHOT/

Does it mean with these sub snapshots, Lucee will also be grabbing the latest sub snapshots from maven? that’s also not so great, all published artefacts should be reliably static

Fixed

Details

Assignee

Reporter

Priority

Fix versions

New 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

Sprint

Created 10 July 2024 at 09:20
Updated 20 March 2025 at 15:55
Resolved 11 July 2024 at 06:10

Flag notifications