Skip to content
This repository was archived by the owner on Dec 2, 2023. It is now read-only.
This repository was archived by the owner on Dec 2, 2023. It is now read-only.

Plugin dependencies should not be managed #106

@pkocandr

Description

@pkocandr

Dependencies of a plugin cannot be managed by dependencyManagement in Maven. But it happened, that an internal redhat version was returned as a dependency of public version from Maven Central, while this was not declared in its pom. To be concrete one of the paths was:

org.jboss.teiid.quickstart:drools-integration:3.0.0.redhat-63-8
has parent org.jboss.teiid.quickstart:teiid-quickstart-parent:3.0.0.redhat-63-8 
uses plugin org.apache.maven.plugins:maven-compiler-plugin:3.1 
depends on (scope compile) org.apache.openjpa:openjpa:2.2.0 
depends on (scope compile) com.sun.xml.bind:jaxb-impl:2.2.5.redhat-9 
has parent com.sun.xml.bind:jaxb-project:2.2.5.redhat-9 
embeds relaxngcc:relaxngcc:1.12-redhat-2 
depends on (scope compile) net.java.dev.msv:msv-core:2011.1-redhat-2

The problem is that openjpa 2.2.0 specifies a dependency on jaxb-imple 2.0.5, not 2.2.5.redhat-9. The graph was computed with build-requires preset, default mutator and patcher-ids "dependency-plugin" and "dist-pom".

When we reach a plugin we should probably replace the selected mutator by NOOP and use it down the dependency graph.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions