Upgrade Gradle to 7.4 & AGP to 7.1.1 (& Disable Jetifier)#9
Upgrade Gradle to 7.4 & AGP to 7.1.1 (& Disable Jetifier)#9
Conversation
|
👋 @oguzkocer ! Do you have any idea why the I get the below and I am not sure what I need to be doing with the Many thanks for your support and guidance! 🙏 |
The workflow seems to be from the original repo and the secret is not configured in this repo. I think it's safe to ignore it. |
Ignore it it is then, at least for now, thanks Oguz! 🙇 |
The 'com.dipien.byebyejetifier' plugin was used to determine whether Jetifier can be disable for this project. After configuring 'Bye Bye Jetifier' and running the below command: ./gradlew canISayByeByeJetifier -Pandroid.enableJetifier=false The output was clear, Jetifier can be now safely disabled for this project: > Task :canISayByeByeJetifier ========================================= Project: : ========================================= * No legacy android support usages found ===================================================== ... * No dependencies with legacy android support usages! ... ===================================================== ... ... =============================== ... You can say Bye Bye Jetifier. * ... ===============================
# Conflicts: # package.json
|
👋 @oguzkocer ! As done here, Can you please take a look at this b4be54e commit, which resolves the same issue, and verify that I am not missing anything? 🙇 Cc @fluiddot PS: Can you also verify this 9bd99f5 commit, were I am re-adding the maven-publish plugin configuration. 🤔 |
The Android project publishing is now located in 'android-npm', it is only used for generating the AAR and is invoked when running the './createNPMPackage.sh' script.
# Conflicts: # android-npm/react-native-reanimated-66-hermes.aar # android/build.gradle # createNPMPackage.sh # package.json
android/build.gradle
Outdated
| id 'com.diffplug.gradle.spotless' apply false | ||
| } | ||
|
|
||
| if (project == rootProject) { | ||
| apply from: 'spotless.gradle' | ||
| } |
There was a problem hiding this comment.
👋 @fluiddot !
I am not sure why this Spotless plugin needs to be guarded with this if (project == rootProject) { ... } check, but we could maybe remove that check altogether and just have Spotless enabled by default. Then, this configuration will become much more straightforward. Wdyt? 🤔
Do do so, we would need to:
- Use
com.diffplug.spotlessinstead ofcom.diffplug.gradle.spotlesswhen defying the plugin version (settings.gradle.kts). - Use
id 'com.diffplug.spotless'instead ofid 'com.diffplug.gradle.spotless' apply falsewhen applying the plugin (build.gradle). - Since the
spotless.gradleis only used within the abovebuild.gradlefile, to move thespotless { ... }configuration directly into thebuild.gradleabove and removing thespotless.gradlefile altogether.
There was a problem hiding this comment.
I am not sure why this Spotless plugin needs to be guarded with this if (project == rootProject) { ... } check, but we could maybe remove that check altogether and just have Spotless enabled by default. Then, this configuration will become much more straightforward. Wdyt? 🤔
Me neither to be honest, but I agree about enabling it by default. I'll proceed with the changes, thanks 🙇 .
There was a problem hiding this comment.
Awesome @fluiddot , I double-checked that and can verify this change, thank you!
PS: Now we need to update the aar and tarball once more and we are done, right? 🤔
There was a problem hiding this comment.
PS: Now we need to update the aar and tarball once more and we are done, right? 🤔
Yep, actually, I ran the createNPMPackage script in 734d446 to generate both AAR and tarball files but there were no modifications.
There was a problem hiding this comment.
Btw, I also updated the reference of this package in the Gutenberg PR (reference).
|
Since we removed the source code for these projects from PS: Eventually, we might upgrade |
This PR is part of Upgrade Gradle to 7.4 & AGP to 7.1.1 (& Disable Jetifier) PR. There are
13libraries that are upgraded toGradle 7.4&AGP 7.1.1(&Disable Jetifier).All those PRs follow the general outline below:
Gradleversion upgraded to7.3.3with the./gradlew wrapper --gradle-version=7.3.3 --distribution-type=allcommand.AGPversion upgrade to7.0.4(seeandroid/settings.gradle.ktschange).Gradle 7.4&AGP 7.1.1.android/gradle.propertieschange).1.9.0-wp-3(seepackage.json).1.9.0-wp-3(seereact-native-reanimated-1.9.0-wp-3.tgz).AGPversion upgrade to7.1.1(from4.2.2) (withinandroid/build.gradle). Cc @oguzkocer2.2.4-wp-2(seepackage.json).2.2.4-wp-2(seereact-native-reanimated-2.2.4-wp-2.tgz).Spotlessconfiguration change (withinsettings.gradle.ktsandandroid/gradle).2.4.1-wp-2(seepackage.json).2.4.1-wp-2(seereact-native-reanimated-2.4.1-wp-2.tgz).To test - Now
These changes can be tested as part of the gutenberg PR which is updated to use the temporarily non-tagged node module project dependencies generated with these changes.
To test - Later ⚙️
These changes can be tested as part of the gutenberg-mobile PR ⚙️ or WordPress-Android PR ⚙️ which is updated to use the bundle ⚙️ generated with these changes.
FYI: It's best to leave the testing step to the gutenberg PR review since even if these PRs are merged, they won't impact anything until the package.json file is updated. Worst case scenario, a follow up PR will get opened to fix any issues that are found during testing.
Follow up
Once these PRs are merged in, a new tag will get created for each library and the package.json file will be again updated accordingly.