-
-
Notifications
You must be signed in to change notification settings - Fork 441
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
Gradle pom.xml incorrect metadata redirection #2233
Comments
@darekdeo thanks for raising this. We'll look into it and report back here once we know more. |
There's a draft PR that should address this issue: getsentry/craft#412 |
https://discuss.gradle.org/t/how-to-disable-using-gradle-module-metadata-then-to-use-pom-xml-to-resolve-dependencies/42995/2
|
FYI: For |
We still have to finalize the open craft PR getsentry/craft#412 to have this resolved. Maybe @buenaflor will take care of it when he's back again. |
Need to check if that works automatically after getsentry/craft#412 is merged |
@romtsn can you release a patch and see if it works? getsentry/craft#412 is merged |
Currently .module files are only supported automatically through |
Noting that https://repo.maven.apache.org/maven2/io/sentry/sentry-android/7.3.0/ |
hey, just an update here: |
Integration
sentry-android
Build System
Gradle
AGP Version
Any
Proguard
Disabled
Version
Every
Steps to Reproduce
Above is description of an cause.
The more important symptoms and in fact issues are while using artifactory: https://jfrog.com/artifactory/ which will throw 403, stopping the gradle build with failure.
Expected Result
Either:
Actual Result
pom.xml contains line do_not_remove: published-with-gradle-metadata and there is no published .module file (Gradle Module Metadata)
The text was updated successfully, but these errors were encountered: