[MNG-6222] Support exclusion of direct plugin dependencies

• Type: Improvement
• Status: Open
• Priority: Major
• Resolution: Unresolved
• Fix Version/s: Issues to be reviewed for 4.x
• Component/s: Plugins and Lifecycle
• Assignee: Unassigned
• Reporter: Robert Scholte
• Created: 27/Apr/17 08:07
• Updated: 24/Jun/24 23:52

Description

Based on http://stackoverflow.com/questions/43630262/how-to-exclude-a-direct-dependency-of-a-maven-plugin

<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>

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