[ https://issues.apache.org/jira/browse/MNG-7379?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17466542#comment-17466542 ]
Michael Osipov commented on MNG-7379: ------------------------------------- This doesn't look healthy. Can you show me your repo config in your pom or settings and purge the local repo and retry snapshot. > SNAPSHOT versions of Custom rules appear to only come from > repository.apache.org > -------------------------------------------------------------------------------- > > Key: MNG-7379 > URL: https://issues.apache.org/jira/browse/MNG-7379 > Project: Maven > Issue Type: Bug > Components: Artifacts and Repositories, Dependencies > Affects Versions: 3.8.4 > Environment: Apache Maven 3.6.3 > (cecedd343002696d0abb50b32b541b8a6ba2883f) > Maven home: C:\Program Files (x86)\apache-maven-3.6.1\bin\.. > Java version: 11.0.3, vendor: Amazon.com Inc., runtime: C:\Program > Files\Java\jdk11.0.3 > Default locale: en_GB, platform encoding: Cp1252 > OS name: "windows 10", version: "10.0", arch: "amd64", family: "windows" > Reporter: Rod Widdowson > Priority: Major > Fix For: waiting-for-feedback > > Attachments: RELEASE.TXT, SNAPSHOT.TXT > > > We use a customer build enforcer in our build & CI process. > It is configured in the canonical fashion > {code:java} > <plugin> > <groupId>org.apache.maven.plugins</groupId> > <artifactId>maven-enforcer-plugin</artifactId> > <dependencies> > <dependency> > <groupId>net.shibboleth.maven.enforcer.rules</groupId> > <artifactId>maven-dist-enforcer</artifactId> > <version>3.0.0</version> > </dependency> > </dependencies> > <executions> > ..... {code} > This collects the plugin from our repositories as defined with > {{<repositories/>}} > I recently wanted to start running from a SNAPSHOT version. If I build this > locally everything works fine. But if I delete it from my local repository > and start again it appears (from watching the denug outto want to only load > the enforcer plugin from {{repository.apache.org}} > This feels like a bug but I may have missed some configuration somewhere. -- This message was sent by Atlassian Jira (v8.20.1#820001)