Wrong handling of test JARs

[dnsbtchr]

Is there an existing issue for this?

• I have searched the existing issues

Package ecosystem

Maven

Package manager version

Apache Maven 3.9.8

Language version

No response

Manifest location and content before the Dependabot update

pom.xml

...
<dependency>
  <groupId>dummy.group</groupId>
  <artifactId>dummy-artifact</artifactId>
  <type>test-jar</type>
  <classifier>tests</classifier>
  <version>123</version>
  <scope>test</scope>
</dependency>
...

dependabot.yml content

version: 2
registries:
release-artifactory:
type: maven-repository
url: https://dummy-nexus.com/
plugins-artifactory:
type: maven-repository
url: https://dummy-nexus.com/

updates:

• package-ecosystem: "maven"
  directory: "/"
  registries:
  • release-artifactory
  • plugins-artifactory
    schedule:
    interval: "daily"
    time: "09:00"
    timezone: "Europe/Berlin"
    rebase-strategy: auto
    commit-message:
    prefix: "chore"
    include: scope
    labels:
  • "skynet:merge:squash"
  • "skynet:update:rebase"
  • "dependencies"

Updated dependency

No response

What you expected to see, versus what you actually saw

According to https://maven.apache.org/guides/mini/guide-attached-tests.html test JARs should be specified with scope=test, type=test-jar and classifier=tests. When doing this Maven downloads the dependency with the suffix -tests.jar as in
Downloaded from central: https://dummy-nexus.com/dummy.group/dummy-artifact/123/dummy-artifact-tests.jar (10 kB at 4.5 kB/s).

Dependabot seems to behave differently, because it only looks for updates using the suffix -tests.test-jar as in
proxy | 2024/07/05 07:00:02 [156] HEAD https://dummy-nexus.com/dummy.group/dummy-artifact/123/dummy-artifact-tests.test-jar.

Because such an artifact doesn't exist, Dependabot doesn't find any updates.

Native package manager behavior

No response

Images of the diff or a link to the PR, issue, or logs

No response

Smallest manifest that reproduces the issue

No response