You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "James Agnew (Jira)" <ji...@apache.org> on 2021/03/05 16:46:00 UTC
[jira] [Created] (MDEP-739) Dependency Plugin go-offline doesn't
respect artifact classifier
James Agnew created MDEP-739:
--------------------------------
Summary: Dependency Plugin go-offline doesn't respect artifact classifier
Key: MDEP-739
URL: https://issues.apache.org/jira/browse/MDEP-739
Project: Maven Dependency Plugin
Issue Type: Bug
Components: go-offline
Affects Versions: 3.1.2
Reporter: James Agnew
This is a regressing in 3.1.2, and does not occur in 3.1.1.
Given a pom.xml with the following dependency:
{code:java}
<dependency>
<groupId>ca.uhn.hapi.fhir</groupId>
<artifactId>hapi-fhir-testpage-overlay</artifactId>
<version>5.3.0</version>
<classifier>classes</classifier>
</dependency>
{code}
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}}
--
This message was sent by Atlassian Jira
(v8.3.4#803005)