Repository navigation
Conversation
pom.xml declared org.apache.maven.plugins:maven-dependency-plugin twice. Older Maven treated that as a warning; current Maven rejects it: 'build.plugins.plugin.(groupId:artifactId)' must be unique but found duplicate declaration of plugin maven-dependency-plugin @ line 295 Every Maven job on master currently fails at POM parsing because of it. The two declarations pinned the same version (3.10.0). The first carries the copy-agent execution that stages the jmockit agent for tests; the second was bare, with no executions or configuration, so removing it changes nothing. Verified the agent is still copied to target/agents and the suite passes.
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
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.
masteris currently red in CI: every Maven job fails at POM parsing, before any compilation.pom.xmldeclaredmaven-dependency-plugintwice, at line 200 and line 297. Older Maven treated a duplicate as a warning; current Maven rejects it. Nothing is pinned, so the runner image moved underneath the repo — this went red without any commit landing.Both declarations pinned the same version (
3.10.0). The first carries thecopy-agentexecution that stages the jmockit agent for tests; the second was bare, with no executions or configuration. Removed the bare one.Verification
mvn validatepasses (it did not before).target/agents/jmockit-1.49.jaris still staged, so the agent wiring is intact.Confirmed pre-existing by pushing a throwaway branch at
master's exact tip with zero changes (since deleted): 4 failures, 22 cancelled, 0 passes, identicalline 295error.This unblocks #38, which is otherwise green.