[
https://issues.apache.org/jira/browse/ARCHETYPE-562?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17515503#comment-17515503
]
Matthew Jason Benson commented on ARCHETYPE-562:
------------------------------------------------
[~michael-o] I believe this was addressed by my commits:
*
[https://github.com/apache/maven-archetype/commit/137461e8dd71a26f53d25aa9c58e29e04127d6a7]
*
[https://github.com/apache/maven-archetype/commit/54b5fb4bf16d70fce0ab3493d2e178b317a2f5b7]
which enhanced
{{DefaultArchetypeGenerationConfigurator.RequiredPropertyComparator}} to
consider required properties referenced by other required properties' (complex)
default expressions. I believe this issue should have been included in the
3.2.1 changelog as ERH intended.
> Error ordering Default Properties
> ---------------------------------
>
> Key: ARCHETYPE-562
> URL: https://issues.apache.org/jira/browse/ARCHETYPE-562
> Project: Maven Archetype
> Issue Type: Bug
> Components: Plugin
> Affects Versions: 3.0.1, 3.1.0
> Reporter: David Castro
> Priority: Minor
> Original Estimate: 24h
> Remaining Estimate: 24h
>
> Default properties are being ordered consediring the "exact" use of another
> property. The assumption implies that a property that uses a derived string
> of a previous property may not be ordered as expected:
>
> {code:java}
> <requiredProperty key="domainUpperCase">
> <defaultValue>${${domainName}.toUpperCase()}</defaultValue>
> <validationRegex>[A-Z]+</validationRegex>
> </requiredProperty>
> {code}
>
>
>
--
This message was sent by Atlassian Jira
(v8.20.1#820001)
