You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Michael Osipov (Jira)" <ji...@apache.org> on 2022/10/19 20:11:00 UTC

[jira] [Commented] (MINSTALL-178) Maven Doesn't Pick Locally Installed Package / Artifact

    [ https://issues.apache.org/jira/browse/MINSTALL-178?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17620571#comment-17620571 ] 

Michael Osipov commented on MINSTALL-178:
-----------------------------------------

You should provide a sample project for this. Your information is very sparse.

> Maven Doesn't Pick Locally Installed Package / Artifact
> -------------------------------------------------------
>
>                 Key: MINSTALL-178
>                 URL: https://issues.apache.org/jira/browse/MINSTALL-178
>             Project: Maven Install Plugin
>          Issue Type: Bug
>          Components: install:install
>    Affects Versions: 3.0.1
>         Environment: Linux
>            Reporter: Surendra
>            Priority: Major
>              Labels: easyfix, performance
>
> Java Version - 11
> `mvn clean install` is not picking up a locally installed snapshot artifact that is present in the .m2 folder.
> It complains with the following warning and then start looking for this artifact in maven central -
>  
> {code:java}
> [DEBUG]  Could not find metadata
> <GROUP_ID>:<ARTIFACT_ID>:0.0.1-SNAPSHOT/maven-metadata.xml in local {code}
>  
> I checked .m2 directory and it has maven-metadata-local.xml, why does maven look for maven-metadata.xml file? It's a locally installed artifact and maven should be able to pick this up directly. Looks like I'm missing something.



--
This message was sent by Atlassian Jira
(v8.20.10#820010)