robertklaus-bosch opened a new issue, #13468: URL: https://github.com/apache/maven/issues/13468
### Affected version 3.10.0 ### Bug description In an automated build scenario, we upgraded from 3.9.16 to 3.10.0. The log now contains several new warnings. In comparison, the build in 3.9.16 has none. I decided to report this, as I could not really find the problem and maybe other users stumble over this. This could be more of a migration guide topic or a mentioning in the release notes on what to do, to get your build clean. As the 3.10.0 release is on the "alignment" between 3.10.0 and 4.0 I think it would make sense to have that in a Maven 4 migration guide (Not in https://maven.apache.org/guides/mini/guide-migration-to-mvn4.html). We call Maven with following arguments to keep log output small and focused on problems: `mvn -e -B --no-transfer-progress` This one is mentioned as new feature in release notes with `repositoryOrigins` and was backported to 3.x according to issue. The documentation does not explain this (I looked at https://maven.apache.org/settings.html#Servers). ```bash Warning: Using credentials of server 'xyz-releases' for repository https://<host>/<app>/xyz-release-local/, although no repository or mirror with this id is declared in settings or on the command line and the server declares no <repositoryOrigins>. Declare 'https://<host>/' in <repositoryOrigins> of that server in settings to bind these credentials explicitly, or set maven.repository.credentialScope=strict to refuse such credential use. ``` In this case we have a company mirror for Maven Central. As this is in an automated build and I have no control over the cache, I am unsure how to resolve this warning. There are more than 400 new lines of warnings now, so would be nice to know what to do: ```bash Warning: org.apache.groovy:groovy-bom:pom:5.0.6 was downloaded from https://<host>/<app>/maven-central-remote/ while a cached not-found from a previous attempt suppresses re-checking https://<host>/<app>/xyz-release-local/; expiring the cached not-found so that repository is checked again on the next resolution ``` -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected]
