Details
-
Improvement
-
Status: Open
-
Major
-
Resolution: Unresolved
-
3.1.2
-
None
-
None
-
Linux (fc33)
Description
I can't seem to be able to copy a dependency that I previously downloaded from a 3rd party repository, when referring to it using metaversion.
This doesn't work, unless I refer to the version directly in the :copy invocation:
$ # rm -rf ~/.m2/repository/org/openconext/ # clean up $ mvn org.apache.maven.plugins:maven-dependency-plugin:3.1.2:get \ -DremoteRepositories=excelfore.public::::https://dev-esync.excelfore.com/artifactory/excelfore.public \ -Dartifact=org.openconext:mujina-idp:LATEST:jar $ mvn org.apache.maven.plugins:maven-dependency-plugin:3.1.2:copy \ -Dartifact=org.openconext:mujina-idp:LATEST:jar -DoutputDirectory=/tmp [ERROR] Failed to execute goal org.apache.maven.plugins:maven-dependency-plugin:3.1.2:copy (default-cli) on project standalone-pom: Unable to find/resolve artifact.: Failed to read artifact descriptor for org.openconext:mujina-idp:jar:LATEST: Failed to resolve version for org.openconext:mujina-idp:jar:LATEST: Could not find metadata org.openconext:mujina-idp/maven-metadata.xml in local (/home/vps/.m2/repository) -> [Help 1]
(this is from a real public repo)
I figure this has something to do with the fact that plugin has no knowledge of the repository ID, and needs it to find the right metadata file. So maybe the plugin should have "repositoryId" property that can be supplied to it so it knows which metadata file to check.