-
Notifications
You must be signed in to change notification settings - Fork 7
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Hortonwork Schema Registry 1.0.0 (Invalid POM) #811
Comments
Another issue is that dropwizard-bom and dropwizard-dependencies are 'pom' dependency types, not jar, but this isn't clear in the generated pom, so maven will go and try and find jars for these - but they don't exist. Also there's no jersey-shaded 1.0.0 dependency - either because it's not needed any more (but still referenced), or it failed to get uploaded to maven central which thinks 0.9.1 is the latest. |
Hi. I got same problem on my project. It all started with the version 0.9.1. There were problems with |
Whilst doing an upgrade to 1.0.0, both IntelliJ and command-line Maven (3.9.0) are complaining that the pom files for 1.0.0 are invalid.
There are no further details when using -X with Maven.
Checking the schema-registry-client pom myself with mvn clean, I get:
I see there is no parent pom, nor
dependencyManagement
section, so it isn’t a surprise it is failing to validate the pom.And I think the problem is a conversion between Gradle (https://github.com/hortonworks/registry/blob/master/schema-registry/schema-registry-client/build.gradle) and the POM it is generating at build time?
Obviously, I can work around this by including the transitive dependencies myself for now, but perhaps it’s worth looking into this and creating a 1.0.1 for those of us stuck with Maven?
It may be similar to spring-gradle-plugins/dependency-management-plugin#141 but I think your Gradle version 6.7 is newer than that...
(I cannot do a gradle build of a checkout locally due to the corporate firewall, and lacking some of the build’s gradle dependencies on the local nexus)
The text was updated successfully, but these errors were encountered: