Gradle 3.0 API Breakage
See original GitHub issueGradle 3.0 is here! Maybe we still work with it? Let’s find out!
This issue will track general 3.0 compatibility; individual API breakages will be tracked in their own issues:
-
StyledTextOutput
removed, issue #124
Issue Analytics
- State:
- Created 7 years ago
- Reactions:5
- Comments:5
Top Results From Across the Web
Gradle 3.0 Release Notes
Additionally, Gradle 3.0 provides support for running on the latest Java 9 EAP builds. ... Changes to previously deprecated APIs; Groovy to Java...
Read more >Gradle 3.0.0-alpha1 proguard breaks compile - Issue Tracker
After Upgrading to 3.0.0-alpha1 it seems that gradle proguard (breaks) is not taken from Firebase libs ... at org.gradle.api.internal.project.taskfactory.
Read more >Android Gradle plugin update to v2.3.0 breaks Copy task
No signature of method: org.gradle.api.internal.tasks.DefaultTaskOutputs$TaskOutputUnionFileCollection.setFrom() is applicable for argument ...
Read more >Android Gradle plugin release notes - Android Developers
Important: For a detailed log of Android Gradle plugin API deprecations and ... For a high-level summary of upcoming breaking changes in the...
Read more >Implementation vs API dependency - Jeroen Mols
Upgrading to Android studio 3.0 territory will make building multi-module projects a lot faster, but it also means a breaking Gradle plugin ...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Thanks, @EddieRingle. It’s our old friend,
StyledTextOutput
; I missed that it was being removed. Bummer!I’ll open a new issue for this particular class; undoubtedly there will be others.
@benjamin-bader 0.5.6 seems to resolve our issues, thanks!