[
https://issues.apache.org/jira/browse/MINSTALL-178?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17715265#comment-17715265
]
Slawomir Jaranowski commented on MINSTALL-178:
----------------------------------------------
[~surendra_lilly] in your command example {{mvn clean install}} two Maven phase
are executed: clean and install.
Each phase can have configured many goal - some can be default ... but some can
be added in your project.
So without simple example which reproduce your problem nobody is able to help.
https://maven.apache.org/guides/introduction/introduction-to-the-lifecycle.html
> 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
> Fix For: waiting-for-feedback
>
>
> 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)
