[
https://jira.codehaus.org/browse/MINSTALL-96?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=334274#comment-334274
]
Ivan Bondarenko commented on MINSTALL-96:
-----------------------------------------
Yes, 'skip' is more like a workaround. Excluding certain classifiers (maybe in
both install and deploy) is better. Though I'm not sure how it should look
like, because different conditional/dynamic stuff is a weak side of Maven. For
example "<excludeTag>sources tests</excludeTag>" or
"<excludesTag><excludeTag>sources</excludeTag><excludeTag>tests</excludeTag></excludesTag>"
will not fit because exact classifiers may be not known beforehand. For
war-plugin we are solving it with "<webResources combine.children='append'>",
however I don't know is 'combine.children' some common Maven stuff or just
related to 'webResources'.
> Skip option for install-file
> ----------------------------
>
> Key: MINSTALL-96
> URL: https://jira.codehaus.org/browse/MINSTALL-96
> Project: Maven Install Plugin
> Issue Type: Improvement
> Components: install:install-file
> Affects Versions: 2.4
> Reporter: Tiemo Vorschütz
> Attachments: InstallFileMojo.java.patch
>
>
> For my process it would be helpful to also introduce a skip option for
> install:install-file to be able to disable install-file creation by setting a
> pom property.
> This could be necessary if the build chain is designed by a parent pom and
> should by simply modified inside the child pom.
> In my case all plugin definitions are outsourced to the parent pom file and
> should only be set by properties by the developers to take care that
> modifications to the build chain are inherited.
> I attached a patch to enable skipping also for install-file.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
