[MNG-6541] less restrictive "is referencing itself" check

• Type: Wish
• Status: Closed
• Priority: Major
• Resolution: Duplicate
• Affects Version/s: 3.5.4
• Component/s: Dependencies
• Assignee: Unassigned
• Reporter: Václav Haisman
• Created: 20/Dec/18 13:52
• Updated: 06/Jan/19 23:06
• Resolved: 06/Jan/19 23:06

Description

I have issues when building site:site in project with OpenJFX. The javafx-graphics artifact sort of references itself:

<?xml version="1.0" encoding="UTF-8"?>
<project xmlns="http://maven.apache.org/POM/4.0.0" xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 http://maven.apache.org/xsd/maven-4.0.0.xsd" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
  <modelVersion>4.0.0</modelVersion>
  <groupId>org.openjfx</groupId>
  <artifactId>javafx-graphics</artifactId>
  <version>11.0.1</version>
  <parent>
    <groupId>org.openjfx</groupId>
    <artifactId>javafx</artifactId>
    <version>11.0.1</version>
  </parent>
  <dependencies>
    <dependency>
      <groupId>org.openjfx</groupId>
      <artifactId>javafx-graphics</artifactId>
      <version>11.0.1</version>
      <classifier>${javafx.platform}</classifier>
    </dependency>
    <dependency>
      <groupId>org.openjfx</groupId>
      <artifactId>javafx-base</artifactId>
      <version>11.0.1</version>
    </dependency>
  </dependencies>
</project>

But it does so with additional classifier. When I run site:site, it gives me this:

[WARNING] Unable to create Maven project from repository.
org.apache.maven.project.ProjectBuildingException: 1 problem was encountered while building the effective model for org.openjfx:javafx-graphics:11.0.1
[FATAL] 'dependencies.dependency org.openjfx:javafx-graphics:11.0.1' for org.openjfx:javafx-graphics:11.0.1 is referencing itself. @ line 13, column 17
 for project org.openjfx:javafx-graphics:11.0.1
    at org.apache.maven.project.DefaultProjectBuilder.build (DefaultProjectBuilder.java:165)
    at org.apache.maven.project.DefaultProjectBuilder.build (DefaultProjectBuilder.java:327)
    at org.apache.maven.report.projectinfo.dependencies.RepositoryUtils.getMavenProjectFromRepository (RepositoryUtils.java:125)

I was wondering if the check could not be relaxed to accommodate this situation that seems to be common even in core Java components?

Issue Links

• duplicates: MNG-6490 Maven shall not fail reporting circular dependency when the dependency is a classified secondary artifact