Request to Restore Version 2.2.3 of com.android.tools.build:gradl to Maven Central [361717762]

Assigned

Bug

Status Update

No update yet.

Description

al...@gmail.com

created issue #1

Aug 23, 2024 08:46PM

Dear Android Tools Team,

I hope this message finds you well.

I'm currently working on a project that depends on version 2.2.3 of the `com.android.tools.build:gradle` package. Unfortunately, this version is no longer available in Maven Central or JCenter, and I've encountered significant issues trying to use other versions or alternatives.

Given that our project critically relies on version 2.2.3, I would like to kindly request if it would be possible to restore this version to Maven Central. This would help us avoid a major disruption in our build process.

repo1.maven.org/maven2/com/android/tools/build/gradle/2.2.3

Thank you in advance for considering this request. I would greatly appreciate any assistance or guidance you can provide.

Best regards,
Fernande, Alex

Comments

al...@gmail.com <al...@gmail.com> #2Aug 25, 2024 01:10PM

Disregard - after adding

enableUnitTestCoverage = false
enableAndroidTestCoverage false

Thinks started to work again.

But for what it is worth - the error message could have been more helpful.

hu...@google.com <hu...@google.com> Aug 27, 2024 10:54AM

Assigned to an...@google.com.

je...@google.com <je...@google.com> #3Aug 27, 2024 05:55PM

Reassigned to je...@google.com.

Well the error message is that it tried to configure jacoco task and failed, so it works for you because you disabled the feature.

So the error message is indicative of a bigger problem. Oviously, 8.2 is pretty old for us, not sure you are interested in trying 8.8.

The easiest would be to have a project reproducing the issue, if that's possible, we'll look into it.

al...@gmail.com <al...@gmail.com> #4Aug 27, 2024 06:15PM

We tried bumping things up to 8.8 but that causes other problems that we need to resolve first. There was a long list of issues with name spaces and what not due to clashes across different 3rd part integrations that we have in the app.
Unfortunately we haven't had the resources to keep things up to date for a long time - and now every possible problem is just piling up...

I'll get back once we manage to upgrade to 8.8...

je...@google.com <je...@google.com> #5Aug 27, 2024 06:28PM

unfortunately, I cannot think of any unless you have the binaries locally cached on one of your machines. If you do I would stage them somewhere internally and have a repositories entry pointing to it.

jcenter sent plenty of warnings about the imminent turning down, but you could also reach out to them in case there is a way to access to bits and then do what I suggested above.

finally, you can try to downgrade to 2.1.3 which is there (I think).

but obviously upgrading would be better, any information about the incompatibilities you can share ?

Issue 361717762