[
https://issues.apache.org/jira/browse/MNG-7108?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17294345#comment-17294345
]
Herve Boutemy edited comment on MNG-7108 at 3/3/21, 7:36 AM:
-------------------------------------------------------------
in the error message:
{noformat}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){noformat}
as you say, LATEST is a meta-version, that is defined in maven-metadata.xml: no
maven-metadata.xml, no meta-version
maven-metadata.xml is managed by install/deploy and automatic download commands
of Maven: when you do something by hand, you need to do everything by hand =
define meta-version if you want to use it (see its internal documentation
https://maven.apache.org/ref/3.6.3/maven-repository-metadata/ )
BTW, using LATEST meta-version is clearly not recommended, because it is
unstable by nature (execution in 6 months may give a different result than
execution from today)
I don't know precisely your use case, but as dependencies of code, it's really
something to avoid
was (Author: hboutemy):
in the error message:
{noformat}Could not find metadata
org.openconext:mujina-idp/maven-metadata.xml{noformat}
as you say, LATEST is a meta-version, that is defined in maven-metadata.xml: no
maven-metadata.xml, no meta-version
maven-metadata.xml is managed by install/deploy and automatic download commands
of Maven: when you do something by hand, you need to do everything by hand =
define meta-version if you want to use it (see its internal documentation
https://maven.apache.org/ref/3.6.3/maven-repository-metadata/ )
BTW, using LATEST meta-version is clearly not recommended, because it is
unstable by nature (execution in 6 months may give a different result than
execution from today)
I don't know precisely your use case, but as dependencies of code, it's really
something to avoid
> Can't copy dependency from a 3rd party repository
> -------------------------------------------------
>
> Key: MNG-7108
> URL: https://issues.apache.org/jira/browse/MNG-7108
> Project: Maven
> Issue Type: Bug
> Components: Dependencies
> Affects Versions: 3.6.3
> Environment: Linux (fc33)
> Reporter: Pawel Veselov
> Priority: Major
>
> 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:
> {noformat}
> $ # 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]
> {noformat}
> (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.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
