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

["Dave Wichers (JIRA)" <ji...@apache.org>]

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

Dave Wichers commented on MNG-6222:
-----------------------------------

I'm in exactly this situation right now and can't figure out how to address it without hacking the pom.xml file of the plugin dependency causing the problem. Any chance this is going to get worked on any time soon?

> 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
>            Priority: Major
>             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
(v7.6.3#76005)