[MDEP-739] Dependency Plugin go-offline doesn't respect artifact classifier

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 3.1.2
• Fix Version/s: 3.2.0
• Component/s: go-offline
• Assignee: Sylwester Lachiewicz
• Reporter: James Agnew
• Created: 05/Mar/21 16:45
• Updated: 07/Jun/21 12:30
• Resolved: 03/Jun/21 21:22

Description

This is a regressing in 3.1.2, and does not occur in 3.1.1.

Given a pom.xml with the following dependency:

<dependency>
    <groupId>ca.uhn.hapi.fhir</groupId>
    <artifactId>hapi-fhir-testpage-overlay</artifactId>
    <version>5.3.0</version>
    <classifier>classes</classifier>
</dependency>

The go-offline command will try (and fail) to resolve the JAR that does not have that classifier. Version 3.1.1 of the plugin correctly resolved the right JAR.

 

Error is:

 

[ERROR] Failed to execute goal org.apache.maven.plugins:maven-dependency-plugin:3.1.2:go-offline (default-cli) on project hapi-fhir-jpaserver-starter: org.eclipse.aether.resolution.DependencyResolutionException: Could not find artifact ca.uhn.hapi.fhir:hapi-fhir-testpage-overlay:jar:5.3.0 in oss-snapshots

Issue Links

• links to: GitHub Pull Request #133