chore: remove parent pom depdendencies, which break maven consumers #7
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 way Physikal is currently packaged on maven central, the pom e.g. of
si-units-1.1.1.0
currently includes:This breaks consumers of Physikal using maven to build:
I think the situation si somewhat similar to https://stackoverflow.com/questions/27110014/could-not-find-artifact-in-maven-central-repo-when-search-returns-a-match
In any case, I believe the parent pom is not necessary as a direct dependency. I confirm I can build and consume phyiskal to my local repo just fine using the change in this PR.