Repository navigation
Conversation
openam-core/pom.xml declared org.testng:testng twice. Maven 3.9.x only warned about it, but Maven 3.10.0 - shipped in the ubuntu-24.04 runner image 20261004.327 - rejects the duplicate as a model error, so every ubuntu build-maven job fails while reading the POMs.
vharseko
added
bug
build
ci
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
openam-core/pom.xmldeclaresorg.testng:testngtwice (lines 405–409 and 471–475). Maven 3.9.x only warned about it:The ubuntu-24.04 runner image
20261004.327upgraded Maven from 3.9.16 to 3.10.0, which treats the duplicate as a model error. Everybuild-maven (ubuntu-latest, *)job now fails within ~40 s while reading the POMs ("The build could not read 1 project"), e.g. in #1163. The macOS and Windows images still ship Maven 3.9.x, so they are not affected yet.This removes the second, redundant declaration; the first one (test scope, version from
dependencyManagement) stays, so the resolved dependency set is unchanged.