[ 
https://jira.codehaus.org/browse/MINSTALL-96?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=334340#comment-334340
 ] 

Robert Scholte commented on MINSTALL-96:
----------------------------------------

I'm not sure if the conditional/dynamic stuff is really that weak. The 
{{<inherited/>}}-tag for plugins is powerfull when you understand how to use 
it. If you combine it with the [combine.* 
attributes|http://blog.sonatype.com/people/2011/01/maven-how-to-merging-plugin-configuration-in-complex-projects]
 inside the configuration, almost every combination is possible. But this 
requires the 
{{<excludesTag><excludeTag>sources</excludeTag><excludeTag>tests</excludeTag></excludesTag>}}
 format, as most plugins do at both Apache Maven and Codehaus Mojo.
I don't understand the issue of not knowing classifiers beforehand. One should 
know what is attachted right? It won't be a problem, if the exclude contains 
classifiers, which don't exist.

                
> 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

Reply via email to