[
https://issues.apache.org/jira/browse/MNG-6222?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17859792#comment-17859792
]
Thorsten Glaser commented on MNG-6222:
--------------------------------------
I’d be glad to have the scope workaround. (At the moment, only compile, runtime
and system are permitted, so not even using test could be used to work around
this.) In Maven 3, that is.
> 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
(v8.20.10#820010)
