Skip to:

  1. Skip to Jira Navigation
  2. Skip to Side Navigation
  3. Skip to Main Content

invalid extension is reported as successful

Description

an invalid extension isn’t reported correctly as failing (: instead of ;, no version= )

SET LUCEE_EXTENSIONS=B737ABC4-D43F-4D91-8E8E973E37C40D1B:2.0.0.28-SNAPSHOT

a different invalid variation is

SET LUCEE_EXTENSIONS=B737ABC4-D43F-4D91-8E8E973E37C40D1B:version=2.0.0.28-SNAPSHOT

when there is a version present, it’s reported as failing (as well as null?)

Activity

Show:

Zac Spitzer 9 January 2025 at 12:42

this is another situation where I’d like to propose crashing on startup due to invalid config, like we do when LUCEE_BASE_CONFIG points to a missing file, would make devops easier, otherwise, it can lead to a bit of a magical mystery tour

Zac Spitzer 9 January 2025 at 12:27

I’m not going to worry about the null, it’s not important and indicates something is wrong

Fixed

Details

Assignee

Reporter

Labels

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

Fix versions

Priority

Created 9 January 2025 at 11:57
Updated 15 January 2025 at 08:04
Resolved 15 January 2025 at 08:04