apache / apache/maven-dependency-plugin
[MDEP-569] copy fails on artifacts previously downloaded via get from repo specified via CLI
- Dominant language
- Java
- Stars
- 175
- Forks
- 196
- Avg merge
- 19h 30m
- Merged PRs (30d)
- 5
Description
**[Tom Wieczorek](https://issues.apache.org/jira/secure/ViewProfile.jspa?name=tom@bibbu.net)** opened **[MDEP-569](https://issues.apache.org/jira/browse/MDEP-569?redirect=false)** and commented
`dependency:copy` fails to copy artifacts that were previously downloaded via `dependency:get` from a remote repository that has been specified on the command line. The error message is:
> The POM for artifact is missing, no dependency information available
and later on
> Failed to execute goal dependency:copy (default-cli) on project standalone-pom: Unable to find/resolve artifact. Failure to find artifact in https://repo.maven.apache.org/maven2 was cached in the local repository, resolution will not be reattempted until the update interval of central has elapsed or updates are forced
But: `dependency:get` actually succeeded and the artifact and its POM are in the local repo.
```none
mvn -version
mvn org.apache.maven.plugins:maven-dependency-plugin:3.0.1:get \
org.apache.maven.plugins:maven-dependency-plugin:3.0.1:copy \
-DremoteRepositories=http://packages.confluent.io/maven/ \
-Dartifact=io.confluent:kafka-schema-registry:3.1.1
ls -la ~/.m2/repository/io/confluent/kafka-schema-registry/3.1.1
```
I've attached the output of the above test snippets.
---
**Affects:** 3.0.1
**Attachments:**
- [dependency-copy-problem-output.txt](https://issues.apache.org/jira/secure/attachment/12870749/dependency-copy-problem-output.txt) (_52.73 kB_)
**Issue Links:**
- [MNG-7001](https://issues.apache.org/jira/browse/MNG-7001) Reconsider seemingly useless check of artifacts' source repository introduced in Maven 3.0
1 votes, 3 watchers
Contributor guide
No contributing guide indexed for this repository
Research direction
Start by reproducing the Maven commands in the issue with the specified remote repository and artifact, then inspect the attached output and local repository contents. Trace how dependency:get and dependency:copy resolve the artifact and its POM; done means dependency:copy succeeds using the command-line repository.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- build-system
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100