Lenny Primak created MNG-8078:
---------------------------------

             Summary: BOM warnings are emitted on scopes and exclusions
                 Key: MNG-8078
                 URL: https://issues.apache.org/jira/browse/MNG-8078
             Project: Maven
          Issue Type: Bug
          Components: Core, Errors
    Affects Versions: 4.0.0-alpha-13
         Environment: Any
            Reporter: Lenny Primak


There a couple of scenarios that are generating warnings that should not:
 * BOM dependency entries that have a different scope
 * BOM dependency entries that have exclusions

There are many scenarios where multiple BOMs declare the same dependency 
versions, although in slightly different ways. Many of these are transient, and 
very hard to figure out in the first place. Warnings lead to multiple 
unnecessary exclusions and are forcing modifications to POM where they are not 
needed.

The above entries should not generate a warning, because the dependencies are 
not conflicting.

Examples (BOM):
{code:java}
<dependencyManagement>
    <dependencies>
...
<dependency>
    <groupId>org.junit.jupiter</groupId>
    <artifactId>junit-jupiter-api</artifactId>
    <version>${junit.version}</version>
    <scope>test</scope>
</dependency>
<dependency>
    <groupId>org.junit.jupiter</groupId>
    <artifactId>junit-jupiter-params</artifactId>
    <version>${junit.version}</version>
    <scope>test</scope>
</dependency>
<dependency>
    <groupId>org.junit.jupiter</groupId>
    <artifactId>junit-jupiter-engine</artifactId>
    <version>${junit.version}</version>
    <scope>test</scope>
</dependency>
 ...
    </dependencies>
</dependencyManagement>
{code}
 

Warnings:
{code:java}
[WARNING] Some problems were encountered while building the effective model for 
'com.flowlogix:hope-website:war:1.x-SNAPSHOT'
[WARNING] Ignored POM import for: org.slf4j:jcl-over-slf4j:jar:2.0.12@test as 
already imported org.slf4j:jcl-over-slf4j:jar:2.0.12@compile.  Add a the 
conflicting managed dependency directly to the dependencyManagement section of 
the POM.

WARNING] Ignored POM import for: net.bytebuddy:byte-buddy:jar:1.14.12@compile[1 
exclusions] as already imported net.bytebuddy:byte-buddy:jar:1.14.12@compile.  
Add a the conflicting managed dependency directly to the dependencyManagement 
section of the POM.
[WARNING] Ignored POM import for: 
net.bytebuddy:byte-buddy-agent:jar:1.14.12@compile[1 exclusions] as already 
imported net.bytebuddy:byte-buddy-agent:jar:1.14.12@compile.  Add a the 
conflicting managed dependency directly to the dependencyManagement section of 
the POM.
[WARNING] Ignored POM import for: 
org.junit.jupiter:junit-jupiter-api:jar:5.10.2@compile[1 exclusions] as already 
imported org.junit.jupiter:junit-jupiter-api:jar:5.10.2@test.  Add a the 
conflicting managed dependency directly to the dependencyManagement section of 
the POM.
[WARNING] Ignored POM import for: 
org.junit.jupiter:junit-jupiter-engine:jar:5.10.2@compile[1 exclusions] as 
already imported org.junit.jupiter:junit-jupiter-engine:jar:5.10.2@test.  Add a 
the conflicting managed dependency directly to the dependencyManagement section 
of the POM.
[WARNING] Ignored POM import for: 
org.junit.jupiter:junit-jupiter-params:jar:5.10.2@compile[1 exclusions] as 
already imported org.junit.jupiter:junit-jupiter-params:jar:5.10.2@test.  Add a 
the conflicting managed dependency directly to the dependencyManagement section 
of the POM. {code}



--
This message was sent by Atlassian Jira
(v8.20.10#820010)

Reply via email to