[jira] [Commented] (MNG-6222) Support exclusion of direct plugin dependencies

["Sean Flanigan (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/MNG-6222?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16020681#comment-16020681 ] 

Sean Flanigan commented on MNG-6222:
------------------------------------

As another use case, a feature like this could also be used to configure findbugs-maven-plugin to use spotbugs instead of findbugs, by adding the dependency com.github.spotbugs:spotbugs and excluding com.google.code.findbugs:findbugs. See https://github.com/spotbugs/spotbugs/issues/8

> Support exclusion of direct plugin dependencies
> -----------------------------------------------
>
>                 Key: MNG-6222
>                 URL: https://issues.apache.org/jira/browse/MNG-6222
>             Project: Maven
>          Issue Type: Improvement
>          Components: Plugins and Lifecycle
>            Reporter: Robert Scholte
>             Fix For: Issues to be reviewed for 4.x
>
>
> Based on http://stackoverflow.com/questions/43630262/how-to-exclude-a-direct-dependency-of-a-maven-plugin
> {code:xml}
> <build>
>     <plugins>
>         <plugin>
>             <groupId>org.jvnet.jaxb2.maven2</groupId>
>             <artifactId>maven-jaxb2-plugin</artifactId>
>             <version>0.13.2</version>
>             <dependencies>
>                 <dependency>
>            <!-- how to exclude javax.xml.bind:jaxb-api so it can be picked up by the JRE -->
>                 </dependency>
>             </dependencies>
>         </plugin>
>     </plugins>
> </build>
> {code}
> Up until now there hasn't been any reason to do this, but this seems like a valid one. Most clean solution I can think of is allowing to override the scope with "none" for plugin dependencies.
> This solution won't break the pom-4.0.0.xsd



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)