Skip to content

build: resolve dependencies from Maven Central, not the global Nexus mirror - #541

Merged
AntondeGroot merged 1 commit into
mainfrom
maven-central
Nov 21, 2026
Merged

AntondeGroot merged 1 commit into
mainfrom
maven-central

Conversation

@AntondeGroot

Copy link
Copy Markdown
Owner

~/.m2/settings.xml mirrors every repository to the employer Nexus, so this personal project's downloads were proxied through it, and failed outright when the JDK did not trust its certificate (PKIX path building failed).

  • .mvn/settings.xml: an empty settings file, so no mirror applies and Maven falls back to Maven Central.
  • .mvn/maven.config: --settings=${maven.multiModuleProjectDirectory}/.mvn/settings.xml, so Maven loads it from the IDE, the repo root and CI alike.

CI is unaffected: GitHub runners have no Nexus mirror and already use Maven Central.

…mirror

~/.m2/settings.xml mirrors every repository to the employer Nexus. An
empty project settings file, loaded through .mvn/maven.config, makes
this project fall back to Maven Central.
@AntondeGroot
AntondeGroot merged commit b8a6b43 into main Nov 21, 2026
6 checks passed
@AntondeGroot
AntondeGroot deleted the maven-central branch November 21, 2026 07:30
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant