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

Réda Housni Alaoui commented on MRESOLVER-277:
----------------------------------------------

[~cstamas] I made a reproducer at => 
https://github.com/reda-alaoui/mresolver-277/

The issue is triggered by the following conditions:
- {{maven-enforcer-plugin}} with {{requireUpperBoundDeps}} rule enabled
- at least one custom snapshots repository declared
- no negative cache entry for the project modules in the local repository

The command to run would be like:
{code}
rm -fr .m2/repository/me/redaalaoui/mresolver_277 && mvn clean package
{code}

You will see these lines in the log:
{code}
[INFO] ------------------< me.redaalaoui.mresolver_277:core >------------------
[INFO] Building core 1-SNAPSHOT                                           [2/3]
[INFO] --------------------------------[ jar ]---------------------------------
[INFO] 
[INFO] --- maven-clean-plugin:2.5:clean (default-clean) @ core ---
[INFO] Deleting /home/rhousni/projects/mresolver-277/core/target
[INFO] 
[INFO] --- maven-enforcer-plugin:3.0.0:enforce (enforce) @ core ---
Downloading from spring-snapshot: 
https://repo.spring.io/snapshot/me/redaalaoui/mresolver_277/core/1-SNAPSHOT/maven-metadata.xml
{code}

> --no-snapshot-update option does not prevent metadata.xml download
> ------------------------------------------------------------------
>
>                 Key: MRESOLVER-277
>                 URL: https://issues.apache.org/jira/browse/MRESOLVER-277
>             Project: Maven Resolver
>          Issue Type: Bug
>            Reporter: Réda Housni Alaoui
>            Priority: Major
>             Fix For: waiting-for-feedback
>
>
> I have a multi-module project.
> Each time I build the project using an empty local repository, maven-resolver 
> tries to download the {{metadata.xml}} of each module even if I pass 
> {{--no-snapshot-update}} option.
> I think it is a bug.



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

Reply via email to