@otfrom
I think you can override the location here: https://maven.apache.org/settings.html#simple-values
But I'm mostly a #gradle user so I not that familiar with the #maven side of things
@svenjacobs none of the bots are able to properly do Gradle things... - it requires some level of *actual* thinking to realise what's going on that LoremImpsum2026 just can't :D
@iamkonstantin @svenjacobs I'd argue that quite a lot of regular humans can't do #gradle properly :P
During the migration to #AGP9, I noticed that the (Triple-T) Gradle Play Publisher plugin is now in maintenance mode. We currently use it to publish an app to the Play Store from our CI pipeline. Even though there’s already a pull request to make the plugin compatible with AGP 9.0, I’m not entirely comfortable relying on it long-term. Do you know of any good alternatives? How do you typically publish an Android app to the Play Store from CI?
Konstantin 🔭
boosted
ah yes… being incompatible crap that can't use system installed versions because it breakes everything on each release and requires you to fix your build on particular version and stick to it… and install it each time is such a brilliant idea!
Especially in the current day and age, when something constantly breaks (aws, cloudflare…)
all hail fucking #gradle !
And yet #maven #mvn nicely trots along, upgrading in the background and I don't even have to think if it updated or not (save for the upcomming #maven 4 release, but it's like "one in a generation" kind of thing…)
2 media
ah yes… being incompatible crap that can't use system installed versions because it breakes everything on each release and requires you to fix your build on particular version and stick to it… and install it each time is such a brilliant idea!
Especially in the current day and age, when something constantly breaks (aws, cloudflare…)
all hail fucking #gradle !
And yet #maven #mvn nicely trots along, upgrading in the background and I don't even have to think if it updated or not (save for the upcomming #maven 4 release, but it's like "one in a generation" kind of thing…)
2 media
![[...]
FAILURE: Build failed with an exception.
* What went wrong:
Execution failed for task ':app:processDebugResources'.
> Could not resolve all files for configuration ':app:debugRuntimeClasspath'.
> Failed to transform appcompat-1.7.0.aar (androidx.appcompat:appcompat:1.7.0) to match attributes {artifactType=android-compiled-dependencies-resources, org.gradle.category=library, org.gradle.dependency.bundling=external, org.gradle.libraryelements=aar, org.gradle.status=release, org.gradle.usage=java-runtime}.
> Execution failed for AarResourcesCompilerTransform: /root/.gradle/caches/8.13/transforms/459cb14f885dfe9984b3b738a7946fbf/transformed/appcompat-1.7.0.
> AAPT2 aapt2-8.7.3-12006047-linux Daemon #1: Daemon startup failed
This should not happen under normal circumstances, please file an issue if it does.
[...]
Deprecated Gradle features were used in this build, making it incompatible with Gradle 9.0.
You can use '--warning-mode all' to show the individual deprecation warnings and determine if they come from your own scripts or plugins.
For more on this, please refer to https://docs.gradle.org/8.13/userguide/command_line_interface.html#sec:command_line_warnings in the Gradle documentation.
BUILD FAILED in 1m 32s
27 actionable tasks: 27 executed
Command failed with exit code 1: /root/hello/platforms/android/tools/gradlew cdvBuildDebug](https://sfo3.digitaloceanspaces.com/veganism-space/media_attachments/files/115/622/655/452/040/485/original/24aa17f80de6ccc3.png)