-
Notifications
You must be signed in to change notification settings - Fork 475
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
Parent POM referenced but not published to Maven Central #11
Comments
Initially the goal was to deploy only the plugin. But with the parent link all artifacts will need to be publish after all. Please test this staging repository : I have change slightly the artifact ids. The version was increment because I don't maintain old versions (only few detectors were add).
Notify me once, you have done your test. I will promote the artifacts to main repository after. |
[EDIT: missed updating the artifactId, but after verifying ID and version, get the same result] |
Ok I'll make minimal test on my side and publish after. |
I have just release all the artifacts (root-pom, plugin-deps, ...). It will be available soon if not already. Pay attention to the new artifact prefix "findsecbugs"
|
Confirmed fixed for me as of version |
plugin-1.1.0.pom
references a parent POM:But
com.h3xstream.findsecbugs:root-pom:1.1.0
does not exist in Maven Central. This is a problem for the Gradle build tool, which attempts to resolve the parent POM:The text was updated successfully, but these errors were encountered: