POM top level artifact is not shown in SpecificationDependencyDiagram

[JanWesterkamp-iJUG]

@DirkMahler I configured the analysis to show the current usage of Jakarta EE dependenies in MicroProfile, which uses a POM type artifact to configure platform component specs.

Here are the used properties for MP 5.0:

<repo.url>https://repo1.maven.org/maven2</repo.url> <repo.filter>org.eclipse.microprofile*:*:*</repo.filter> <platform.groupId>org.eclipse.microprofile</platform.groupId> <platform.artifactId>microprofile</platform.artifactId> <platform.type>pom</platform.type> <platform.version>5.0</platform.version>

In the jakarta-ee-dependencies_SpecificationDependencyDiagram is missing the top level
org.eclipse.microprofile:microprofile:pom:5.0 artifact, while in the PlatformDependencyDiagram is showing it properly.

Is this because a related query does have problems with the artifact type (POM instead of JAR)?

[JanWesterkamp-iJUG]

Here the related report SVGs:

[DirkMahler]

Just checked: the rules in jqassistant/jakarta-ee-dependencies.xml propagate declared dependencies from POMs to JAR artifacts which then allows queries over artifacts including their transitive dependencies. The POM model itself does not allow that.

I would need to have a closer look at it on how to solve this.