Android samples for Google Workspace APIs

Google Workspace

Last update: Jan 8, 2023

Related tags

Overview

Google Workspace Android Samples

A collection of samples that demonstrate how to call Google Workspace APIs from Android.

Products

Drive

Deprecation

A sample app demonstrating migrating from the Android API to the REST API. See the migration guide for details.

Contributing

Contributions welcome! See the Contributing Guide.

Comments

Can't get fileId of selected file from google drive .

Method to open file , here i can only access name and content

private void openFileFromFilePicker(Uri uri) {

    if (mDriveServiceHelper != null) {

        Log.d(TAG, "Opening " + uri.getPath());

        mDriveServiceHelper.openFileUsingStorageAccessFramework(getContentResolver(), uri)
                .addOnSuccessListener(nameAndContent -> {
                    String name = nameAndContent.first;
                    String content = nameAndContent.second;


                    mFileTitleEditText.setText(name);
                    mDocContentEditText.setText(content);



                    // Files opened through SAF cannot be modified, except by retrieving the
                    // fileId from its metadata and updating it via the REST API. To modify
                    // files not created by your app, you will need to request the Drive
                    // Full Scope and submit your app to Google for review.
                    setReadOnlyMode();
                })
                .addOnFailureListener(exception ->
                        Log.e(TAG, "Unable to open file from picker.", exception));
    }
}

Comment : Files opened through SAF cannot be modified, except by retrieving the // fileId from its metadata and updating it via the REST API. To modify // files not created by your app, you will need to request the Drive // Full Scope and submit your app to Google for review.

Please guide me here . How can we get fileId here . I need fileId to download the selected file .

question

opened by himanshiThakur 19

GoogleApiClient connection failed

Hi all,

When i running the demo, one issue appeared:

I choose my Google Account: [email protected] to access Google Drive, but failed. Here is the log message:

I/BaseDriveActivity: GoogleApiClient connection failed: ConnectionResult{statusCode=SIGN_IN_REQUIRED, resolution=PendingIntent{419fdaa8: android.os.BinderProxy@419cad20}, message=null}

Is there something wrong or i missed something? Could you please share your advice here? TIA

Thanks Muran

opened by Muran-Hu 16
delete/trash issue

Hi, I am only bringing the SO discussions #21369573 and #21370636 here, so we do not vent it there. I installed this DEMO package and ran a few simple tests to see. The issue I mentioned on SO is showing with this DEMO as well. Steps to reproduce: 1/ Android device: "Create a file" ... creates "New file" in the root 2/ WEB browser: https://drive.google.com ... REMOVE (TRASH, DELETE...) the "New file" 3/ Android device: "List files with pagination" the list is unchanged, "New file" is showing.

Since this DEMO does not display the files' status, I ran the same (simplified) scenario in my test suite showing the file's "trashed" status, but did not get conclusive results.

Drive.DriveApi.query(mGAC, query).addResultCallback(new OnChildrenRetrievedCallback() { @Override public void onChildrenRetrieved(MetadataBufferResult rslt) { if (!rslt.getStatus().isSuccess()) return; MetadataBuffer mdb = rslt.getMetadataBuffer(); for (int ii = 0; ii < mdb.getCount(); ii++) { Log.i(TAG, (mdb.get(ii).isTrashed()?"-":"+")+mdb.get(ii).getTitle()); } mdb.close(); } });

Originally, the deleted file was showing as (+) (not trashed) After I EMPTIED TRASH on the web, it changed status to (-) (trashed) But when I re-ran the same test again (delete file, empty trash), I could not reproduce the same behavior. Conclusion: The trashed status (true/false, -/+) may be just random noise. So, the behavior I would expect (after sync): delete file on the web: The file/folder isTrashed() should change false -> true recover file on the web: Change true -> false empty trash - the file should not be listed anymore

This issue isn't a showstopper for me and I assume that it is just work-in-progress and it will be corrected eventually. And the code Burcu's asking for is 0B1mQUW2aFJfdd2JTSkVIQnBoRm8.

opened by seanpjanson 12
Issue for import in Android demos?

Hello, In this demo projects there is use of Drive SDK which imports com.google.android.gms.drive.MetadataChangeSet but in new api there is no imnport of MetadataChangeSet so can you plese tell me how i solve this problem and make this demo working.

opened by solankiranvir 12
Error on query file in google driver

I'm using google driver api for my Android app and have some troubles with it. I'm using query builder to get File by title, then I get count metadata at onSuccessfulListener. I got count = 1 but in my driver has no file with thats title. Sorry about my bad English. Anyone can fix it?

opened by GReaper13 11
issues in classes with latest google play service 21

hi i have imported this demo with latest google play service library 21 but i am getting some errors in some classes like The method newDriveContents(GoogleApiClient) is undefined for the type DriveApi DriveContents cannot be resolved to a type DriveContentsResult cannot be resolved to a type

please any one guide me is there any updated demo with latest google play service library 21 ?

opened by achinverma 11
app not working and log shows Unsupported scope: https://www.googleapis.com/auth/drive

I am trying to test the drive api, I manage to login but when trying to use drive api app crashes and logcat shows:

01-15 14:03:34.481 3090 3177 E ClientConnectOperation: nzh: Authorization failed: Unsupported scope: https://www.googleapis.com/auth/drive 01-15 14:03:34.481 3090 3177 E ClientConnectOperation: at nzl.a(:com.google.android.gms@11951440:25) 01-15 14:03:34.481 3090 3177 E ClientConnectOperation: at nvy.(:com.google.android.gms@11951440:26) 01-15 14:03:34.481 3090 3177 E ClientConnectOperation: at nxh.a(:com.google.android.gms@11951440:72) 01-15 14:03:34.481 3090 3177 E ClientConnectOperation: at swi.run(:com.google.android.gms@11951440:11) 01-15 14:03:34.481 3090 3177 E ClientConnectOperation: at mvc.run(:com.google.android.gms@11951440:26) 01-15 14:03:34.481 3090 3177 E ClientConnectOperation: at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1133) 01-15 14:03:34.481 3090 3177 E ClientConnectOperation: at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:607) 01-15 14:03:34.481 3090 3177 E ClientConnectOperation: at nak.run(:com.google.android.gms@11951440) 01-15 14:03:34.481 3090 3177 E ClientConnectOperation: at java.lang.Thread.run(Thread.java:761)

opened by jacobhub 9

Problem in running android-demos - Login can never success.

I found out I can never run the android-demos successful

I running code with last commit - https://github.com/googledrive/android-demos/commit/4f57857ee10d94fabc4e381d39795eb8cd71b93d

Whenever I choose an item, says "Create a file in App Folder",

the following login dialog box will pop up

Whenever I select my account for example, the dialog will close for few seconds, and then re-appear again.

My logging message is as follow

01-09 11:36:32.783 25040-25040/? I/art: Late-enabling -Xcheck:jni
01-09 11:36:32.897 25040-25040/com.google.android.gms.drive.sample.demo W/System: ClassLoader referenced unknown path: /data/app/com.google.android.gms.drive.sample.demo-2/lib/arm
01-09 11:36:33.056 25040-25068/com.google.android.gms.drive.sample.demo D/OpenGLRenderer: Use EGL_SWAP_BEHAVIOR_PRESERVED: true
01-09 11:36:33.118 25040-25068/com.google.android.gms.drive.sample.demo I/Adreno-EGL: <qeglDrvAPI_eglInitialize:379>: QUALCOMM Build: 10/21/15, 369a2ea, I96aee987eb
01-09 11:36:33.122 25040-25068/com.google.android.gms.drive.sample.demo I/OpenGLRenderer: Initialized EGL, version 1.4
01-09 11:36:36.898 25040-25040/com.google.android.gms.drive.sample.demo I/BaseDriveActivity: GoogleApiClient connection failed: ConnectionResult{statusCode=SIGN_IN_REQUIRED, resolution=PendingIntent{d9ab090: android.os.BinderProxy@c093d89}, message=null}
01-09 11:36:36.909 25040-25046/com.google.android.gms.drive.sample.demo W/art: Suspending all threads took: 11.169ms
01-09 11:36:48.094 25040-25040/com.google.android.gms.drive.sample.demo I/BaseDriveActivity: GoogleApiClient connection failed: ConnectionResult{statusCode=SIGN_IN_REQUIRED, resolution=PendingIntent{a2c01a8: android.os.BinderProxy@c093d89}, message=null}
01-09 11:36:49.664 25040-25040/com.google.android.gms.drive.sample.demo I/BaseDriveActivity: GoogleApiClient connection failed: ConnectionResult{statusCode=SIGN_IN_REQUIRED, resolution=PendingIntent{860b3a7: android.os.BinderProxy@c093d89}, message=null}
01-09 11:36:51.105 25040-25040/com.google.android.gms.drive.sample.demo I/BaseDriveActivity: GoogleApiClient connection failed: ConnectionResult{statusCode=SIGN_IN_REQUIRED, resolution=PendingIntent{fdcd0f2: android.os.BinderProxy@c093d89}, message=null}
01-09 11:36:52.529 25040-25040/com.google.android.gms.drive.sample.demo I/BaseDriveActivity: GoogleApiClient connection failed: ConnectionResult{statusCode=SIGN_IN_REQUIRED, resolution=PendingIntent{dbf9af9: android.os.BinderProxy@c093d89}, message=null}
01-09 11:36:53.770 25040-25040/com.google.android.gms.drive.sample.demo I/BaseDriveActivity: GoogleApiClient connection failed: ConnectionResult{statusCode=SIGN_IN_REQUIRED, resolution=PendingIntent{e095ec: android.os.BinderProxy@c093d89}, message=null}
01-09 11:36:55.085 25040-25040/com.google.android.gms.drive.sample.demo I/BaseDriveActivity: GoogleApiClient connection failed: ConnectionResult{statusCode=SIGN_IN_REQUIRED, resolution=PendingIntent{82377bb: android.os.BinderProxy@c093d89}, message=null}
01-09 11:36:56.734 25040-25040/com.google.android.gms.drive.sample.demo I/BaseDriveActivity: GoogleApiClient connection failed: ConnectionResult{statusCode=SIGN_IN_REQUIRED, resolution=PendingIntent{a542316: android.os.BinderProxy@c093d89}, message=null}

Even if I press the back button, the login dialog will disappear for few seconds, then re-appear again

01-09 11:37:30.704 25040-25040/com.google.android.gms.drive.sample.demo I/BaseDriveActivity: GoogleApiClient connection failed: ConnectionResult{statusCode=SIGN_IN_REQUIRED, resolution=PendingIntent{6b2333: android.os.BinderProxy@c093d89}, message=null}
01-09 11:37:31.568 25040-25040/com.google.android.gms.drive.sample.demo I/BaseDriveActivity: GoogleApiClient connection failed: ConnectionResult{statusCode=SIGN_IN_REQUIRED, resolution=PendingIntent{847eee: android.os.BinderProxy@c093d89}, message=null}
01-09 11:37:32.964 25040-25040/com.google.android.gms.drive.sample.demo I/BaseDriveActivity: GoogleApiClient connection failed: ConnectionResult{statusCode=SIGN_IN_REQUIRED, resolution=PendingIntent{c1eae25: android.os.BinderProxy@c093d89}, message=null}
01-09 11:37:34.252 25040-25040/com.google.android.gms.drive.sample.demo I/BaseDriveActivity: GoogleApiClient connection failed: ConnectionResult{statusCode=SIGN_IN_REQUIRED, resolution=PendingIntent{8a97408: android.os.BinderProxy@c093d89}, message=null}
01-09 11:37:34.999 25040-25040/com.google.android.gms.drive.sample.demo I/BaseDriveActivity: GoogleApiClient connection failed: ConnectionResult{statusCode=SIGN_IN_REQUIRED, resolution=PendingIntent{ff11187: android.os.BinderProxy@c093d89}, message=null}
01-09 11:37:35.754 25040-25040/com.google.android.gms.drive.sample.demo I/BaseDriveActivity: GoogleApiClient connection failed: ConnectionResult{statusCode=SIGN_IN_REQUIRED, resolution=PendingIntent{43fb052: android.os.BinderProxy@c093d89}, message=null}

I do have a valid Google Drive account.

My device is Nexus 5, Android version 6.0.1

May I know is this bug from code example, or something wrong with my device settings?

I compile the code using Android studio 1.5.1, with all tools and sdk up-to-date.

opened by yccheok 8

Question: Google Drive Application Specific Folder Deprecation

As per Google's Documentation:

Support for storing and syncing in the app data folder will likely be removed from Drive in the future. Clients requiring app data storage are strongly encouraged to migrate to a non-Drive solution such as Cloud Firestore.

Is there any timeline around this change? We (Duo Security) are currently storing data in the application specific folder due to security reasons and would like to continue doing so, if possible. If we cannot, then we need to come up with another solution (similar to what is mentioned in the documentation linked above).

As a follow up, will apps still be able to read from the application specific folder after support is removed but not write to it, or will reading from it also no longer be possible?
question

opened by robsmall 7
Invalid parent folder

i am creating one folder using drive API from one device. now i am trying to create file inside that folder using other device but i cant create it. i am getting invalid parent folder error. please help me with this major issue.

opened by Slake07 7
How to use Google Drive API in Android application?

Hi,

I have been searching for the right resources for syncing files with Google Drive by Drive API from the android application. As I can see so many links, from that many are deprecated and some are about to shut down by Google.

Can anyone please help me with this? I am new to this development. It would be great if someone who guide me in the right way to achieve this Google Drive sync from Android application.

opened by subashdbc 6
Dependency Dashboard
This issue provides visibility into Renovate updates and their statuses. Learn more

Rate Limited

These updates are currently rate limited. Click on a checkbox below to force their creation now.

[ ] Update dependency com.google.android.gms:play-services-auth to v11.8.0

[ ] Update dependency com.google.android.gms:play-services-drive to v11.8.0

[ ] Update dependency com.google.api-client:google-api-client-android to v1.32.2

[ ] Update dependency com.google.http-client:google-http-client-gson to v1.40.1

[ ] Update dependency com.android.support:appcompat-v7 to v28

[ ] Update dependency com.android.support:support-v4 to v28

[ ] Update dependency com.android.tools.build:gradle to v7

[ ] Update dependency com.google.android.gms:play-services-auth to v19

[ ] Update dependency com.google.android.gms:play-services-drive to v17

Open

These updates have all been created already. Click a checkbox below to force a retry/rebase of any.

[ ] Update dependency com.google.apis:google-api-services-drive to v3-rev20210919-1.32.1

[ ] Update dependency com.android.tools.build:gradle to v3.6.4

[ ] Update dependency gradle to v4.10.3

[ ] Update dependency gradle to v7

[ ] Click on this checkbox to rebase all open PRs at once

[ ] Check this box to trigger a request for Renovate to run again on this repository
opened by renovate[bot] 0
Update dependency com.android.tools.build:gradle to v3.6.4
This PR contains the following updates:

| Package | Change | Age | Adoption | Passing | Confidence | |---|---|---|---|---|---| | com.android.tools.build:gradle (source) | 3.0.1 -> 3.6.4 | | | | | | com.android.tools.build:gradle (source) | 3.2.1 -> 3.6.4 | | | | |

Configuration

📅 Schedule: At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about these updates again.

[ ] If you want to rebase/retry this PR, check this box.

This PR has been generated by WhiteSource Renovate. View repository job log here.
opened by renovate[bot] 0
Update dependency com.google.apis:google-api-services-drive to v3-rev20210919-1.32.1
This PR contains the following updates:

| Package | Change | Age | Adoption | Passing | Confidence | |---|---|---|---|---|---| | com.google.apis:google-api-services-drive (source) | v3-rev136-1.25.0 -> v3-rev20210919-1.32.1 | | | | |

Configuration

📅 Schedule: At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.

[ ] If you want to rebase/retry this PR, check this box.

This PR has been generated by WhiteSource Renovate. View repository job log here.
opened by renovate[bot] 0
Update dependency gradle to v7
This PR contains the following updates:

| Package | Update | Change | |---|---|---| | gradle (source) | major | 4.1 -> 7.2 | | gradle (source) | major | 4.6 -> 7.2 |

Release Notes

gradle/gradle

v7.1.1

This is a patch release for Gradle 7.1.

It fixes the following issues:

#17488 Many Micronaut builds failing with NPE with Gradle 7.1 & JDK 8

#17548 [Configuration cache] Task not up-to-date for SantaTracker

#17542 [Configuration cache] Filtered FC with mapped elements stored incorrectly

We recommend users upgrade to 7.1.1 instead of 7.1.

Upgrade Instructions

Switch your build to use Gradle 7.1.1 by updating your wrapper:

./gradlew wrapper --gradle-version=7.1.1

See the Gradle 7.x upgrade guide to learn about deprecations, breaking changes and other considerations when upgrading to Gradle 7.1.1.

Reporting Problems

If you find a problem with this release, please file a bug on GitHub Issues adhering to our issue guidelines. If you're not sure you're encountering a bug, please use the forum.

v7.0.2

This is a patch release for Gradle 7.0.

This fixes an issue with files system watching on certain Linux distributions.

We recommend users upgrade to 7.0.2 instead of 7.0.

Upgrade Instructions

Switch your build to use Gradle 7.0.2 by updating your wrapper:

./gradlew wrapper --gradle-version=7.0.2

See the Gradle 6.x upgrade guide to learn about deprecations, breaking changes and other considerations when upgrading to Gradle 7.0.1.

Reporting Problems

If you find a problem with this release, please file a bug on GitHub Issues adhering to our issue guidelines. If you're not sure you're encountering a bug, please use the forum.

v7.0.1

This is a patch release for Gradle 7.0.

This fixes several issues reported against 7.0.

We recommend users upgrade to 7.0.1 instead of 7.0.

Upgrade Instructions

Switch your build to use Gradle 7.0.1 by updating your wrapper:

./gradlew wrapper --gradle-version=7.0.1

See the Gradle 6.x upgrade guide to learn about deprecations, breaking changes and other considerations when upgrading to Gradle 7.0.1.

Reporting Problems

If you find a problem with this release, please file a bug on GitHub Issues adhering to our issue guidelines. If you're not sure you're encountering a bug, please use the forum.

v7.0

v6.9.1

This is a patch release for Gradle 6.9, containing backported bugfixes in Gradle 7.2 to Gradle 6.x.

It fixes the following issues:

#18089 Deprecate jcenter() repository

#17950 Renaming and recreating the project directory causes Gradle to lose track of changes on Windows

#17949 Gradle's up-to-date checks do not work on Windows FAT drives

We recommend users upgrade to 6.9.1 instead of 6.9.

Upgrade Instructions

Switch your build to use Gradle 6.9.1 by updating your wrapper:

./gradlew wrapper --gradle-version=6.9.1

See the Gradle 6.x upgrade guide to learn about deprecations, breaking changes and other considerations when upgrading to Gradle 6.9.1.

Reporting Problems

If you find a problem with this release, please file a bug on GitHub Issues adhering to our issue guidelines. If you're not sure you're encountering a bug, please use the forum.

v6.8.3

This is a patch release for Gradle 6.8.

This fixes a critical bug present in Gradle 6.8, 6.8.1 and 6.8.2.

All issues fixed in this patch release

Please don’t use the original 6.8 release or previous patch releases, and instead upgrade to 6.8.3.

Upgrade Instructions

Switch your build to use Gradle 6.8.3 by updating your wrapper:

./gradlew wrapper --gradle-version=6.8.3 --gradle-distribution-sha256-sum 7faa7198769f872826c8ef4f1450f839ec27f0b4d5d1e51bade63667cbccd205

See the Gradle 6.x upgrade guide to learn about deprecations, breaking changes and other considerations when upgrading to Gradle 6.8.3.

Reporting Problems

If you find a problem with this release, please file a bug on GitHub Issues adhering to our issue guidelines. If you're not sure you're encountering a bug, please use the forum.

v6.8.2

This is a patch release for Gradle 6.8.

This fixes several bugs in Gradle 6.8.1.

All issues fixed in this patch release

Please don’t use the original 6.8 release or the 6.8.1, and instead upgrade to 6.8.2.

Upgrade Instructions

Switch your build to use Gradle 6.8.2 by updating your wrapper:

./gradlew wrapper --gradle-version=6.8.2

See the Gradle 6.x upgrade guide to learn about deprecations, breaking changes and other considerations when upgrading to Gradle 6.8.2.

Reporting Problems

If you find a problem with this release, please file a bug on GitHub Issues adhering to our issue guidelines. If you're not sure you're encountering a bug, please use the forum.

v6.8.1

This is a patch release for Gradle 6.8.

This fixes several critical bugs in Gradle 6.8.

All issues fixed in this patch release

We recommend that you use Gradle 6.8.1 over the initial release of Gradle 6.8.

Upgrade Instructions

Switch your build to use Gradle 6.8.1 by updating your wrapper:

./gradlew wrapper --gradle-version=6.8.1

See the Gradle 6.x upgrade guide to learn about deprecations, breaking changes and other considerations when upgrading to Gradle 6.8.1.

Reporting Problems

If you find a problem with this release, please file a bug on GitHub Issues adhering to our issue guidelines. If you're not sure you're encountering a bug, please use the forum.

v6.7.1

This is a patch release for Gradle 6.7.

This fixes several critical bugs in Gradle 6.7.

All issues fixed in this patch release

We recommend that you use Gradle 6.7.1 over the initial release of Gradle 6.7.

Upgrade Instructions

Switch your build to use Gradle 6.7.1 by updating your wrapper:

./gradlew wrapper --gradle-version=6.7.1

See the Gradle 6.x upgrade guide to learn about deprecations, breaking changes and other considerations when upgrading to Gradle 6.7.1.

Reporting Problems

If you find a problem with this release, please file a bug on GitHub Issues adhering to our issue guidelines. If you're not sure you're encountering a bug, please use the forum.

v6.7

v6.6.1

This is a patch release for Gradle 6.6.

This fixes several critical bugs in Gradle 6.6.

All issues fixed in this patch release

We recommend that you use Gradle 6.6.1 over the initial release of Gradle 6.6.

Upgrade Instructions

Switch your build to use Gradle 6.6.1 by updating your wrapper:

./gradlew wrapper --gradle-version=6.6.1

See the Gradle 6.x upgrade guide to learn about deprecations, breaking changes and other considerations when upgrading to Gradle 6.6.1.

Reporting Problems

If you find a problem with this release, please file a bug on GitHub Issues adhering to our issue guidelines. If you're not sure you're encountering a bug, please use the forum.

v6.6

v6.5.1

This is a patch release for Gradle 6.5.

This fixes several critical bugs in Gradle 6.5:

Regression: Gradle 6.5 cached builds cause IllegalStateException #13367

Regression: Compile classpath configuration is not deterministic #13555

Regression: Class cast exception when GStrings are used with System.getProperty #13569

And a number of dependency graph resolution errors (#13251, #13316, #13329, #13551)

All issues fixed in this patch release

We recommend that you use Gradle 6.5.1 over the initial release of Gradle 6.5.

Upgrade Instructions

Switch your build to use Gradle 6.5.1 by updating your wrapper:

./gradlew wrapper --gradle-version=6.5.1

See the Gradle 6.x upgrade guide to learn about deprecations, breaking changes and other considerations when upgrading to Gradle 6.5.1.

Reporting Problems

If you find a problem with this release, please file a bug on GitHub Issues adhering to our issue guidelines. If you're not sure you're encountering a bug, please use the forum.

v6.5

v6.4.1

This is a patch release for Gradle 6.4.

This fixes several critical bugs in Gradle 6.4:

Regression: Different daemons are used between IDE and CLI builds for the same project #13069

Regression: Main-Class attribute always added to jar manifest when using application plugin #13057

All issues fixed in this patch release

We recommend that you use Gradle 6.4.1 over the initial release of Gradle 6.4.

Upgrade Instructions

Switch your build to use Gradle 6.4.1 by updating your wrapper:

./gradlew wrapper --gradle-version=6.4.1

See the Gradle 6.x upgrade guide to learn about deprecations, breaking changes and other considerations when upgrading to Gradle 6.4.1.

Reporting Problems

If you find a problem with this release, please file a bug on GitHub Issues adhering to our issue guidelines. If you're not sure you're encountering a bug, please use the forum.

v6.4

v6.3

v6.2.2

This is a patch release for Gradle 6.2.

This fixes a critical bug in Gradle 6.2:

Multi-project build use the properties of the rootProject for all included builds. #12381

All issues fixed

We recommend that you use Gradle 6.2.2 over the initial release of Gradle 6.2.

Read the full release notes

Upgrade Instructions

Switch your build to use Gradle 6.2.2 by updating your wrapper:

./gradlew wrapper --gradle-version=6.2.2

See the Gradle 6.x upgrade guide to learn about deprecations, breaking changes and other considerations when upgrading to Gradle 6.2.2.

Reporting Problems

If you find a problem with this release, please file a bug on GitHub Issues adhering to our issue guidelines. If you're not sure you're encountering a bug, please use the forum.

v6.2.1

This is a patch release for Gradle 6.2.

This fixes several critical bugs in Gradle 6.2:

Project name disambiguation causes project / external dependency conflicts to be missed. #12315

IdeaModelBuilder does not provide groovy-all as compile dep for buildSrc #12274

Gradle crashes if GRADLE_RO_DEP_CACHE is set and it cannot create modules-2 directory within it #12293

All issues fixed

We recommend that you use Gradle 6.2.1 over the initial release of Gradle 6.2.

Read the full release notes

Upgrade Instructions

Switch your build to use Gradle 6.2.1 by updating your wrapper:

./gradlew wrapper --gradle-version=6.2.1

See the Gradle 6.x upgrade guide to learn about deprecations, breaking changes and other considerations when upgrading to Gradle 6.2.1.

Reporting Problems

If you find a problem with this release, please file a bug on GitHub Issues adhering to our issue guidelines. If you're not sure you're encountering a bug, please use the forum.

v6.2

v6.1.1

This is a patch release for Gradle 6.1.

This fixes several critical bugs in Gradle 6.1:

Plugins using kotlin-dsl and compiled with 6.1 are incompatible with Gradle 6.0 #11947

Missing fixed issues from Gradle 6.1 release notes #11954

Memory regression when resolving large artifacts while computing checksums #11966

Gradle 6.1 generates an empty .gradle and gradle directories on each execution in subproject directories #11971

All issues fixed

We recommend that you use Gradle 6.1.1 over the initial release of Gradle 6.1.

Read the full release notes

Upgrade Instructions

Switch your build to use Gradle 6.1.1 by updating your wrapper:

./gradlew wrapper --gradle-version=6.1.1

See the Gradle 6.x upgrade guide to learn about deprecations, breaking changes and other considerations when upgrading to Gradle 6.1.x.

Reporting Problems

If you find a problem with this release, please file a bug on GitHub Issues adhering to our issue guidelines. If you're not sure you're encountering a bug, please use the forum.

v6.1

v6.0.1

This is a patch release for Gradle 6.0.

This fixes several critical bugs in Gradle 6.0:

Incremental Java compilation is broken with Android 3.5.1 and Gradle 6.0 #11330

Unable to use a Provider as an artifact for the maven-publish plugin #11054

Implicit capabilities not always applied/detected #11300

maven-metadata.xml SHA256 and SHA512 checksums prevent publishing to Nexus #11308

Unable to properly resolve dynamic dependencies from mavenLocal() repo #11321

Kotlin DSL: fileTree(mapOf(...)) has unexpected behavior #11335

Attribute disambiguation rule for 'org.gradle.category' can cause unexpected type exception #11365

All issues fixed

We recommend that you use Gradle 6.0.1 over the initial release of Gradle 6.0.

Upgrade Instructions

Switch your build to use Gradle 6.0.1 by updating your wrapper properties:

./gradlew wrapper --gradle-version=6.0.1

Standalone downloads are available at https://gradle.org/install.

Reporting Problems

If you find a problem with Gradle, please file a bug on GitHub Issues adhering to our issue guidelines. If you're not sure you're encountering a bug, please use the forum.

v5.6.4

This bug-fix release contains all changes from 5.6.1 through 5.6.3 as well as:

Can't configure kotlinOptions after upgrade to gradle 5.6.3 using kotlin-dsl #11083

Slow localhost look-up on macOS #11134

We recommend that you use Gradle 5.6.4 over any other 5.6.x release.

Upgrade Instructions

Switch your build to use Gradle 5.6.4 by updating your wrapper properties:

./gradlew wrapper --gradle-version=5.6.4

Standalone downloads are available at https://gradle.org/install.

Reporting Problems

If you find a problem with Gradle, please file a bug on GitHub Issues adhering to our issue guidelines. If you're not sure you're encountering a bug, please use the forum.

v5.6.3

This bug-fix release contains all changes from 5.6.1 and 5.6.2 as well as:

Let Kotlin DSL gracefully handle lambdas registered as extensions (5.6.3) #11014

Gradle Module Metadata compatibility for unique snapshots #11050

maven-publish publishes jars with wrong extension for known jar packagings like 'ejb' in 5.6 #10555

Regression in 5.5 when using dependency constraints for non-jar dependencies without a POM #10948

resolution failure when dependency locks and kotlin-dsl plugin are present #10697

Non-Kotlin extensions crash the build when using Kotlin DSL + Kotlin plugins #10729

Sporadic build failures with build-scan due to an overlapping ID assignment https://github.com/gradle/gradle/pull/10286

Prevent StackOverflowException caused by excessive 'or' via PatternMatcher #10330

We recommend that you use Gradle 5.6.3 over any other 5.6.x release.

Upgrade Instructions

Switch your build to use Gradle 5.6.3 by updating your wrapper properties:

./gradlew wrapper --gradle-version=5.6.3

Standalone downloads are available at https://gradle.org/install.

Reporting Problems

If you find a problem with Gradle, please file a bug on GitHub Issues adhering to our issue guidelines. If you're not sure you're encountering a bug, please use the forum.

v5.6.2

This bug-fix release contains changes to Gradle 5.6.1:

Duplicate entry in generated .classpath file in Gradle >= 5.6 (#10393)

Memory leak when using tasks that use Worker API and process isolation (#10411)

We recommend that you use Gradle 5.6.2 over 5.6.1.

Upgrade Instructions

Switch your build to use Gradle 5.6.2 by updating your wrapper properties:

./gradlew wrapper --gradle-version=5.6.2

Standalone downloads are available at https://gradle.org/install.

Reporting Problems

If you find a problem with Gradle, please file a bug on GitHub Issues adhering to our issue guidelines. If you're not sure you're encountering a bug, please use the forum.

v5.6.1

This bug-fix release contains changes to Gradle 5.6:

Unable to publish artifacts with custom classifier/extension from java project with Gradle 5.6 (https://github.com/gradle/gradle/issues/10287)

Regression in 5.6 signArchives (Duplicate key) (https://github.com/gradle/gradle/issues/10302)

Regression setting version for ArchiveTasks in 5.6 (https://github.com/gradle/gradle/issues/10311)

A failure occurred while executing org.jetbrains.kotlin.compilerRunner.GradleKotlinCompilerWork (https://github.com/gradle/gradle/issues/10317)

DirectoryFileTree breaks SourceTask since 5.6 (https://github.com/gradle/gradle/issues/10322)

Regression: Unable to pass java.util.Properties object using Worker API in Gradle 5.6 (https://github.com/gradle/gradle/issues/10323)

Unable to publish multiple publications with same coordinates (https://github.com/gradle/gradle/issues/10333)

Gradle 5.6 - Resolving resources from buildSrc or plugins (https://github.com/gradle/gradle/issues/10347)

We recommend that you use Gradle 5.6.1 over 5.6.

Upgrade Instructions

Switch your build to use Gradle 5.6.1 by updating your wrapper properties:

./gradlew wrapper --gradle-version=5.6.1

Standalone downloads are available at https://gradle.org/install.

Reporting Problems

If you find a problem with Gradle, please file a bug on GitHub Issues adhering to our issue guidelines. If you're not sure you're encountering a bug, please use the forum.

v5.5.1

This bug-fix release contains three changes to Gradle 5.5:

Combination of errorprone-gradle-plugin and options.fork = true causes Java compilation to fail in Gradle 5.5 #9897

Using dependency declaration gradleKotlinDsl() fails with 5.5 #9919

Chain of transitives aligned by same platform can lead to broken resolution #9882

We recommend that you use Gradle 5.5.1 over 5.5.

Upgrade Instructions

Switch your build to use Gradle 5.5.1 by updating your wrapper properties:

./gradlew wrapper --gradle-version=5.5.1

Standalone downloads are available at https://gradle.org/install.

Reporting Problems

If you find a problem with Gradle, please file a bug on GitHub Issues adhering to our issue guidelines. If you're not sure you're encountering a bug, please use the forum.

v5.4.1

This bug-fix release contains two changes to Gradle 5.4:

Fix inconsistent classpath ordering when dependencies have lots of excludes - https://github.com/gradle/gradle/issues/9197

Kotlin DSL IDEA script editor can't find JDK classes with Gradle 5.4 if Gradle JVM != Project SDK - https://github.com/gradle/gradle/issues/9195

We recommend that you use Gradle 5.4.1 over 5.4.

Upgrade Instructions

Switch your build to use Gradle 5.4.1 by updating your wrapper properties:

./gradlew wrapper --gradle-version=5.4.1

Standalone downloads are available at https://gradle.org/install.

Reporting Problems

If you find a problem with Gradle, please file a bug on GitHub Issues adhering to our issue guidelines. If you're not sure you're encountering a bug, please use the forum.

v5.3.1

This bug-fix release contains several changes to Gradle 5.3, notably:

Unable to use java-platform and maven-publish in multi-project: https://github.com/gradle/gradle/issues/8845

Unexpected exception when adding a plugin on buildSrc compile classpath: https://github.com/gradle/kotlin-dsl/issues/1363

We recommend that you use Gradle 5.3.1 over 5.3.

Upgrade Instructions

Switch your build to use Gradle 5.3.1 by updating your wrapper properties:

./gradlew wrapper --gradle-version=5.3.1

Standalone downloads are available at https://gradle.org/install.

Reporting Problems

If you find a problem with Gradle, please file a bug on GitHub Issues adhering to our issue guidelines. If you're not sure you're encountering a bug, please use the forum.

v5.2.1

This bug-fix release contains several changes to Gradle 5.2, notably:

Checkstyle issues with a single source file: https://github.com/gradle/gradle/issues/8394

BOM support conflicts: https://github.com/gradle/gradle/issues/8420

We recommend that you use Gradle 5.2.1 over 5.2.

Upgrade Instructions

Switch your build to use Gradle 5.2.1 by updating your wrapper properties:

./gradlew wrapper --gradle-version=5.2.1

Standalone downloads are available at https://gradle.org/install.

Reporting Problems

If you find a problem with Gradle, please file a bug on GitHub Issues adhering to our issue guidelines. If you're not sure you're encountering a bug, please use the forum.

v5.1.1

This bug-fix release contains several changes to Gradle 5.1, notably:

A daemon memory leak affecting all projects https://github.com/gradle/gradle/issues/8142

Incremental Java compilation https://github.com/gradle/gradle/issues/8194

A fix to Gradle's generated Javadoc in 5.1 https://github.com/gradle/gradle/issues/8183

We recommend that you use Gradle 5.1.1 over 5.1.

Upgrade Instructions

Switch your build to use Gradle 5.1.1 by updating your wrapper properties:

./gradlew wrapper --gradle-version=5.1.1

Standalone downloads are available at https://gradle.org/install.

Reporting Problems

If you find a problem with Gradle, please file a bug on GitHub Issues adhering to our issue guidelines. If you're not sure you're encountering a bug, please use the forum.

v4.10.3

This bug-fix release contains 3 changes to Gradle 4.10.2:

https://github.com/gradle/gradle/pull/7510

https://github.com/gradle/gradle/issues/6849

https://github.com/gradle/gradle/issues/7014

It also incorporates all fixes to 4.10.1 and 4.10.2.

We recommend that you use Gradle 4.10.3 over 4.10, 4.10.1 and 4.10.2.

Upgrade Instructions

Switch your build to use Gradle 4.10.3 by updating your wrapper properties:

./gradlew wrapper --gradle-version=4.10.3

Standalone downloads are available at https://gradle.org/install.

Reporting Problems

If you find a problem with Gradle 4.10.3, please file a bug on GitHub Issues adhering to our issue guidelines. If you're not sure you're encountering a bug, please use the forum.

v4.10.2

This bug-fix release contains 3 changes to Gradle 4.10.1:

Dependent module Scala compilation in test context fails for 4.10.1 #6735

Gradle fails to resolve project dependencies against Scala projects #6750

Candidate set provided to AttributeDisambiguationRule contains null entry #6747

We recommend that you use Gradle 4.10.2 over 4.10.1 or 4.10.

Upgrade Instructions

Switch your build to use Gradle 4.10.2 by updating your wrapper properties:

./gradlew wrapper --gradle-version=4.10.2

Standalone downloads are available at https://gradle.org/install.

Reporting Problems

If you find a problem with Gradle 4.10.2, please file a bug on GitHub Issues adhering to our issue guidelines. If you're not sure you're encountering a bug, please use the forum.

v4.10.1

This bug-fix release addresses 6 regressions in Gradle 4.10:

#6656: FileTreeElement.getPath() returns absolute system dependent filepath.

#6592: Up-to-date checks for missing files can be incorrect

#6612: Gradle fails when no incremental compile snapshot data available.

#6582: Gradle 4.10 incorrect ordering between dependencies of dependent tasks.

#6558: tasks.withType(ScalaCompile::class.java).configureEach fails on multi-project builds.

#6653: Double deprecation message when using publishing plugin.

In addition, the Gradle Kotlin DSL has been updated to 1.0 RC6, see the release notes for the list of included fixes.

Upgrade Instructions

Switch your build to use Gradle 4.10.1 by updating your wrapper properties:

./gradlew wrapper --gradle-version=4.10.1

Standalone downloads are available at https://gradle.org/install.

Reporting Problems

If you find a problem with Gradle 4.10.1, please file a bug on GitHub Issues adhering to our issue guidelines. If you're not sure you're encountering a bug, please use the forum.

v4.8.1

This bug-fix release addresses 6 regressions in Gradle 4.8:

#5740: Maven Central dropped support for older TLS implementations. This makes the dependency resolution fail if the Gradle build runs on JDK 7.

#5701: Gradle 4.8 broke compatibility with the artifactory and bintray publishing plugins.

#5708: Gradle 4.8 sometimes fails with ConcurrentModificationException when project.tasks.withType() is used.

#5729: The dependency resolution engine sometimes fails with "Unexpected parent dependency" message, which became more apparent in Gradle 4.8.

#5722: Gradle 4.8 broke the ability of the SourceSet to override the compile tasks' destination directory.

#5692: Gradle 4.8 doesn't consider versions equal when using dependencySubstitution and failOnVersionConflict.

Upgrade Instructions

Switch your build to use Gradle 4.8.1 by updating your wrapper properties:

./gradlew wrapper --gradle-version=4.8.1

Standalone downloads are available at https://gradle.org/install.

Reporting Problems

If you find a problem with Gradle 4.8.1, please file a bug on GitHub Issues adhering to our issue guidelines. If you're not sure you're encountering a bug, please use the forum.

v4.5.1

This bug-fix release addresses 3 regressions in Gradle 4.5.

Changes in dependency management caused a regression in 4.5 where in some rare cases a dependency could be imported into a different scope than the one declared.

Starting in 4.5, the build cache configuration is shared between builds part of a composite build. NullPointerException could be observed if the parent build finished before the different composites. This lifecycle issue has now been resolved.

A regression in Eclipse project generation caused a sub-project to be added as a dependency to itself, resulting in an error when opening the project in Eclipse.

For the full list of fixed issues, see the 4.5.1 GitHub milestone.

Upgrade Instructions

Switch your build to use Gradle 4.5.1 by updating your wrapper properties:

./gradlew wrapper --gradle-version=4.5.1

Standalone downloads are available at https://gradle.org/install.

Reporting Problems

If you find a problem with Gradle 4.5.1, please file a bug on GitHub Issues adhering to our issue guidelines. If you're not sure you're encountering a bug, please use the forum.

v4.4.1

This bug-fix release addresses 3 regressions in Gradle 4.4.

We started shipping JGit 4.5.3.201708160445-r in Gradle 4.4. Some of the non-shaded JGit resources leaked into the gradleApi() dependency and caused problems in some builds. We now shade all of JGit's resources.

Some builds using Kotlin DSL had problems applying the build-scan plugin in Gradle 4.4. We've updated to kotlin-dsl 0.13.2.

Gradle 4.4 contained changes to internal APIs that broke the popular Nebula dependency lock plugin. This release restores binary compatibility for that plugin. Internal APIs are subject to change, although we try to be mindful of the impact of every change in each Gradle release. If particular internal APIs are useful, please open an issue describing your use case, so we can judge where our public APIs are lacking.

For the full list of fixed issues, see the 4.4.1 GitHub milestone.

Upgrade Instructions

Switch your build to use Gradle 4.4.1 by updating your wrapper properties:

./gradlew wrapper --gradle-version=4.4.1

Standalone downloads are available at https://gradle.org/install.

Reporting Problems

If you find a problem with Gradle 4.4.1, please file a bug on GitHub Issues adhering to our issue guidelines. If you're not sure you're encountering a bug, please use the forum.

v4.3.1

This bug-fix release addresses 3 regressions in Gradle 4.3.

Gradle 4.3 introduced an change where an error in resolving a module from one repository would prevent Gradle from searching for that same module in subsequent repositories.

However, the change to abort searching repositories on all unrecognized errors proved to be too aggressive. With 4.3.1, only repository timeout errors will prevent Gradle from searching for a module in a subsequent repository.

Moreover, the connection and socket timeouts for HTTP/HTTPS requests have been increased to 30 seconds.

This version of Gradle also removes an overload of TaskInputs.property which caused statically compiled plugin code to use the wrong method when calling TaskInputs.property(..., null).

Finally, when using --scan the build scan plugin is applied before other plugins to avoid rendering a warning message.

For the full list of fixed issues, see the GitHub milestone.

Upgrade Instructions

Switch your build to use Gradle 4.3.1 by updating your wrapper properties:

./gradlew wrapper --gradle-version=4.3.1

Standalone downloads are available at https://gradle.org/install.

Reporting Problems

If you find a problem with Gradle 4.3.1, please file a bug on GitHub Issues adhering to our issue guidelines. If you're not sure you're encountering a bug, please use the forum.

v4.2.1

This bug-fix release addresses a regression in 4.2, which caused Android instrumented tests to fail. It also improves Java 9 compatibility and clarifies a few deprecation warnings. We recommend that all Gradle 4.2 users upgrade to 4.2.1

For the full list of fixed issues, see the GitHub milestone.

Upgrade Instructions

Switch your build to use Gradle 4.2.1 by updating your wrapper properties:

./gradlew wrapper --gradle-version=4.2.1

Standalone downloads are available at https://gradle.org/install.

Reporting Problems

If you find a problem with Gradle 4.2.1, please file a bug on GitHub Issues adhering to our issue guidelines. If you're not sure you're encountering a bug, please use the forum.

Configuration

📅 Schedule: At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about these updates again.

[ ] If you want to rebase/retry this PR, check this box.

This PR has been generated by WhiteSource Renovate. View repository job log here.
opened by renovate[bot] 0
Update dependency gradle to v4.10.3
This PR contains the following updates:

| Package | Update | Change | |---|---|---| | gradle (source) | minor | 4.1 -> 4.10.3 | | gradle (source) | minor | 4.6 -> 4.10.3 |

Release Notes

gradle/gradle

v4.10.3

This bug-fix release contains 3 changes to Gradle 4.10.2:

https://github.com/gradle/gradle/pull/7510

https://github.com/gradle/gradle/issues/6849

https://github.com/gradle/gradle/issues/7014

It also incorporates all fixes to 4.10.1 and 4.10.2.

We recommend that you use Gradle 4.10.3 over 4.10, 4.10.1 and 4.10.2.

Upgrade Instructions

Switch your build to use Gradle 4.10.3 by updating your wrapper properties:

./gradlew wrapper --gradle-version=4.10.3

Standalone downloads are available at https://gradle.org/install.

Reporting Problems

If you find a problem with Gradle 4.10.3, please file a bug on GitHub Issues adhering to our issue guidelines. If you're not sure you're encountering a bug, please use the forum.

v4.10.2

This bug-fix release contains 3 changes to Gradle 4.10.1:

Dependent module Scala compilation in test context fails for 4.10.1 #6735

Gradle fails to resolve project dependencies against Scala projects #6750

Candidate set provided to AttributeDisambiguationRule contains null entry #6747

We recommend that you use Gradle 4.10.2 over 4.10.1 or 4.10.

Upgrade Instructions

Switch your build to use Gradle 4.10.2 by updating your wrapper properties:

./gradlew wrapper --gradle-version=4.10.2

Standalone downloads are available at https://gradle.org/install.

Reporting Problems

If you find a problem with Gradle 4.10.2, please file a bug on GitHub Issues adhering to our issue guidelines. If you're not sure you're encountering a bug, please use the forum.

v4.10.1

This bug-fix release addresses 6 regressions in Gradle 4.10:

#6656: FileTreeElement.getPath() returns absolute system dependent filepath.

#6592: Up-to-date checks for missing files can be incorrect

#6612: Gradle fails when no incremental compile snapshot data available.

#6582: Gradle 4.10 incorrect ordering between dependencies of dependent tasks.

#6558: tasks.withType(ScalaCompile::class.java).configureEach fails on multi-project builds.

#6653: Double deprecation message when using publishing plugin.

In addition, the Gradle Kotlin DSL has been updated to 1.0 RC6, see the release notes for the list of included fixes.

Upgrade Instructions

Switch your build to use Gradle 4.10.1 by updating your wrapper properties:

./gradlew wrapper --gradle-version=4.10.1

Standalone downloads are available at https://gradle.org/install.

Reporting Problems

If you find a problem with Gradle 4.10.1, please file a bug on GitHub Issues adhering to our issue guidelines. If you're not sure you're encountering a bug, please use the forum.

v4.8.1

This bug-fix release addresses 6 regressions in Gradle 4.8:

#5740: Maven Central dropped support for older TLS implementations. This makes the dependency resolution fail if the Gradle build runs on JDK 7.

#5701: Gradle 4.8 broke compatibility with the artifactory and bintray publishing plugins.

#5708: Gradle 4.8 sometimes fails with ConcurrentModificationException when project.tasks.withType() is used.

#5729: The dependency resolution engine sometimes fails with "Unexpected parent dependency" message, which became more apparent in Gradle 4.8.

#5722: Gradle 4.8 broke the ability of the SourceSet to override the compile tasks' destination directory.

#5692: Gradle 4.8 doesn't consider versions equal when using dependencySubstitution and failOnVersionConflict.

Upgrade Instructions

Switch your build to use Gradle 4.8.1 by updating your wrapper properties:

./gradlew wrapper --gradle-version=4.8.1

Standalone downloads are available at https://gradle.org/install.

Reporting Problems

If you find a problem with Gradle 4.8.1, please file a bug on GitHub Issues adhering to our issue guidelines. If you're not sure you're encountering a bug, please use the forum.

v4.5.1

This bug-fix release addresses 3 regressions in Gradle 4.5.

Changes in dependency management caused a regression in 4.5 where in some rare cases a dependency could be imported into a different scope than the one declared.

Starting in 4.5, the build cache configuration is shared between builds part of a composite build. NullPointerException could be observed if the parent build finished before the different composites. This lifecycle issue has now been resolved.

A regression in Eclipse project generation caused a sub-project to be added as a dependency to itself, resulting in an error when opening the project in Eclipse.

For the full list of fixed issues, see the 4.5.1 GitHub milestone.

Upgrade Instructions

Switch your build to use Gradle 4.5.1 by updating your wrapper properties:

./gradlew wrapper --gradle-version=4.5.1

Standalone downloads are available at https://gradle.org/install.

Reporting Problems

If you find a problem with Gradle 4.5.1, please file a bug on GitHub Issues adhering to our issue guidelines. If you're not sure you're encountering a bug, please use the forum.

v4.4.1

This bug-fix release addresses 3 regressions in Gradle 4.4.

We started shipping JGit 4.5.3.201708160445-r in Gradle 4.4. Some of the non-shaded JGit resources leaked into the gradleApi() dependency and caused problems in some builds. We now shade all of JGit's resources.

Some builds using Kotlin DSL had problems applying the build-scan plugin in Gradle 4.4. We've updated to kotlin-dsl 0.13.2.

Gradle 4.4 contained changes to internal APIs that broke the popular Nebula dependency lock plugin. This release restores binary compatibility for that plugin. Internal APIs are subject to change, although we try to be mindful of the impact of every change in each Gradle release. If particular internal APIs are useful, please open an issue describing your use case, so we can judge where our public APIs are lacking.

For the full list of fixed issues, see the 4.4.1 GitHub milestone.

Upgrade Instructions

Switch your build to use Gradle 4.4.1 by updating your wrapper properties:

./gradlew wrapper --gradle-version=4.4.1

Standalone downloads are available at https://gradle.org/install.

Reporting Problems

If you find a problem with Gradle 4.4.1, please file a bug on GitHub Issues adhering to our issue guidelines. If you're not sure you're encountering a bug, please use the forum.

v4.3.1

This bug-fix release addresses 3 regressions in Gradle 4.3.

Gradle 4.3 introduced an change where an error in resolving a module from one repository would prevent Gradle from searching for that same module in subsequent repositories.

However, the change to abort searching repositories on all unrecognized errors proved to be too aggressive. With 4.3.1, only repository timeout errors will prevent Gradle from searching for a module in a subsequent repository.

Moreover, the connection and socket timeouts for HTTP/HTTPS requests have been increased to 30 seconds.

This version of Gradle also removes an overload of TaskInputs.property which caused statically compiled plugin code to use the wrong method when calling TaskInputs.property(..., null).

Finally, when using --scan the build scan plugin is applied before other plugins to avoid rendering a warning message.

For the full list of fixed issues, see the GitHub milestone.

Upgrade Instructions

Switch your build to use Gradle 4.3.1 by updating your wrapper properties:

./gradlew wrapper --gradle-version=4.3.1

Standalone downloads are available at https://gradle.org/install.

Reporting Problems

If you find a problem with Gradle 4.3.1, please file a bug on GitHub Issues adhering to our issue guidelines. If you're not sure you're encountering a bug, please use the forum.

v4.2.1

This bug-fix release addresses a regression in 4.2, which caused Android instrumented tests to fail. It also improves Java 9 compatibility and clarifies a few deprecation warnings. We recommend that all Gradle 4.2 users upgrade to 4.2.1

For the full list of fixed issues, see the GitHub milestone.

Upgrade Instructions

Switch your build to use Gradle 4.2.1 by updating your wrapper properties:

./gradlew wrapper --gradle-version=4.2.1

Standalone downloads are available at https://gradle.org/install.

Reporting Problems

If you find a problem with Gradle 4.2.1, please file a bug on GitHub Issues adhering to our issue guidelines. If you're not sure you're encountering a bug, please use the forum.

Configuration

📅 Schedule: At any time (no schedule defined).

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about these updates again.

[ ] If you want to rebase/retry this PR, check this box.

This PR has been generated by WhiteSource Renovate. View repository job log here.
opened by renovate[bot] 0