Short-hand component properties parsed incorrectly - regression from 5.3.3

Description

Given a component with short-hand properties:

Dumping the property metadata should show the following (works on 5.3.3.62):

On 5.3.5-78 RC, dumping the property metadata shows:

Note what should be the property type (numeric) has become the name, and the name (versionValue) has become the type. This tells me that the parsing is off.

Environment

Lucee 5.3.5.78-RC
Java 13
Fedora Linux
Tomcat

Activity

Show:
Jesse Shaffer
April 9, 2020, 10:26 PM
Edited

I updated the description to make it more clear.

Pothys - MitrahSoft
April 10, 2020, 1:00 AM
Edited

I've checked this ticket and confirmed the issue happened on lucee latest version 5.3.6.46-SNAPSHOT also.

Abram Adams
June 2, 2020, 7:08 AM

Just ran into this issue. Had to revert back to a previous Lucee version to get our app working. Seems like a very serious regression; why is it still awaiting approval?

Jesse Shaffer
June 3, 2020, 2:34 AM

I’m not sure either - other similar tickets were added after this, not marked as duplicates, and were put on the backlog. This is a complete showstopper for us for all versions post 5.3.4.

Michael Offner
June 15, 2020, 11:47 PM

Fixed

Assignee

Michael Offner

Reporter

Jesse Shaffer

Priority

Blocker

Fix versions

Sprint

5.3.8 Sprint 3

Affects versions