Duplicate
Details
Assignee
UnassignedUnassignedReporter
Zac SpitzerZac SpitzerPriority
NewNew 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
None
Details
Details
Assignee
Unassigned
UnassignedReporter
Zac Spitzer
Zac SpitzerPriority
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
None
Created 27 October 2024 at 10:33
Updated 15 January 2025 at 08:00
Resolved 6 December 2024 at 11:19
pom style dependencies definitions are quite verbose
component javaSettings = '{ maven:[ { "groupId" : "org.graalvm.polyglot", "artifactId" : "polyglot", "version" : "24.1.1" }, { "groupId" : "org.graalvm.polyglot", "artifactId" : "python", "version" : "24.1.1" } ] }'
vs the much less verbose
component javaSettings = '{ maven:[ "org.graalvm.polyglot:polyglot:24.1.1" , "org.graalvm.polyglot:python:24.1.1" ] }'
both can be supported quite easily (string or struct)
when classifier is required, it’s the last item in the list