jira-importer commented on issue #154: URL: https://github.com/apache/maven-install-plugin/issues/154#issuecomment-2771841828
**[Robert Scholte](https://issues.apache.org/jira/secure/ViewProfile.jspa?name=rfscholte)** commented 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. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
