Point the module POMs at the 6.1.0-SNAPSHOT parent - #8
Open
dionmcm wants to merge 1 commit into
Open
Conversation
The root POM moved to 6.1.0-SNAPSHOT, but both modules still declare <parent> 6.0.0. Maven resolves a parent by relativePath first and falls back to the repositories, so with no 6.0.0 parent on the filesystem and none published it fails at POM read time: Non-resolvable parent POM for org.ihtsdo.drools:snomed-drools-engine:6.0.0: org.ihtsdo.drools:snomed-drools:pom:6.0.0 was not found This happens before anything is compiled, so `mvn test` on develop currently fails for every module. With the two versions aligned the reactor builds and all 34 tests pass.
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.
The root POM moved to
6.1.0-SNAPSHOT, but both modules still declare<parent>6.0.0.Maven resolves a parent by
relativePathfirst and falls back to the repositories, so with no6.0.0parent on the filesystem and none published, it fails at POM read time:Found while rebasing another branch onto
developafter you merged #6–IHTSDO#11 — thank you for those. Nothing else here depends on this beyond needing a green build.