[
https://jira.codehaus.org/browse/ARCHETYPE-274?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=277391#comment-277391
]
Herve Boutemy commented on ARCHETYPE-274:
-----------------------------------------
no ETA for this: if you provide a patch, I'll look to integrate it
such a feature will require UI working tightly coupled with the generation
process: seems not easy to do (the generation is not an easy task, even in a
decoupled form)
> Conditionally include or exclude a file from archetype during generation
> ------------------------------------------------------------------------
>
> Key: ARCHETYPE-274
> URL: https://jira.codehaus.org/browse/ARCHETYPE-274
> Project: Maven Archetype
> Issue Type: Improvement
> Components: Generator
> Affects Versions: 2.0-alpha-4
> Reporter: Dan Allen
>
> I would like to be able to control which files are placed into the generated
> project based on the value of a property that is defined during
> archetype:generate. For instance, I forsee the following prompt:
> Define value for groupId: : com.example
> Define value for artifactId: : myproject
> Define value for package: com.example: :
> Define value for extraSupport: : y
> Based on the value of extraSupport, I want to include (or not include) a file
> in the generated project. If the user does not want the extra support, I
> don't want to clutter up the generated project with unnecessary files.
> It's all about customization of the project based on what the developer
> intends to use. While I could create a whole other archetype, sometimes the
> changes are so slight that it would be easier to include/exclude a file.
> Is there a way to control this behavior using the archetype-metadata.xml
> descriptor?
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
