[ 
https://issues.apache.org/jira/browse/ARCHETYPE-574?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Sorin Dan updated ARCHETYPE-574:
--------------------------------
    Description: 
If we don't set in archetype.properties the parameters for which a default 
value was defined in archetype-metadata.xml, running _mvn clean 
integration-test_ gives an error as a value is expected for all parameters in 
the template and the default value is not used.

 

After the fix people will still define all the parameters in 
archetype.properties but if they want to use the default value, they will give 
no value to the parameter:

parameter_X=

Here is the pull request: 
[https://github.com/apache/maven-archetype/pull/31/files]

  was:If we don't set in archetype.properties the parameters for which a 
default value was defined in archetype-metadata.xml, running _mvn clean 
integration-test_ gives an error as a value is expected for all parameters in 
the template and the default value is not used.


> Integration testing ignores default values
> ------------------------------------------
>
>                 Key: ARCHETYPE-574
>                 URL: https://issues.apache.org/jira/browse/ARCHETYPE-574
>             Project: Maven Archetype
>          Issue Type: Bug
>          Components: Archetypes, Plugin
>    Affects Versions: 3.1.1
>            Reporter: Sorin Dan
>            Priority: Major
>              Labels: pull-request-available
>
> If we don't set in archetype.properties the parameters for which a default 
> value was defined in archetype-metadata.xml, running _mvn clean 
> integration-test_ gives an error as a value is expected for all parameters in 
> the template and the default value is not used.
>  
> After the fix people will still define all the parameters in 
> archetype.properties but if they want to use the default value, they will 
> give no value to the parameter:
> parameter_X=
> Here is the pull request: 
> [https://github.com/apache/maven-archetype/pull/31/files]



--
This message was sent by Atlassian JIRA
(v7.6.14#76016)

Reply via email to