[
https://jira.codehaus.org/browse/ARCHETYPE-318?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=276630#comment-276630
]
Tuomas Kiviaho commented on ARCHETYPE-318:
------------------------------------------
I see that there is a property-setting-cli that could be converted to batch
mode test quite easily. The required property in the declaration is a good
permutation to begin with and both cli and batch mode should contain also more
deeply nested property referencing scenarios. (a=${b},b=${c},c=foobar).
> <requiredProperty> <defaultValue> not correctly filtered
> --------------------------------------------------------
>
> Key: ARCHETYPE-318
> URL: https://jira.codehaus.org/browse/ARCHETYPE-318
> Project: Maven Archetype
> Issue Type: Bug
> Components: Generator
> Affects Versions: 2.0-alpha-5
> Reporter: Jochen Ehret
> Priority: Minor
> Fix For: 2.x
>
> Attachments: DefaultArchetypeGenerationConfigurator.patch
>
>
> In our archetype-metadata.xml we´ve defined a <requiredProperty> with a
> default value like this:
> {code:xml}<requiredProperty key="subArtifactId">
> <defaultValue>${artifactId}.itest1</defaultValue>
> </requiredProperty>{code}
> When we call "archetype:generate" and enter the parameters in interactive
> mode everything works fine. But when we try to set the parameter
> "subArtifactId" on the command line (mvn archetype:generate
> -DsubArtifactId=xyz) or from an "archetype.properties" file, the value is
> ignored. In the generated pom.xml the variable ${subArtifactId} is always
> replaced with "${artifactId}.itest1".
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
