Hey there, let's break down how to fix those frustrating Gradle errors, plus share some smarter approaches to studying these old RxJava versions without fighting build tools the whole time.

First: Fixing the Gradle Compatibility Issues #

Those errors pop up because RxJava 0.1.2 and 1.0.0 are ancient (released around 2013-2014) and were built for versions of Gradle, Android Plugin for Gradle (AGP), and Java that are wildly outdated compared to modern Android Studio setups. Here's how to align everything:

1. Match Exact Gradle/AGP Versions #

You'll need to roll back your project's build tools to versions that actually work with RxJava 1.0.0:

• In your project root's build.gradle, set the AGP version to a 1.x release (the first stable AGP version):

  buildscript {
      repositories {
          mavenCentral() // Google repo didn't exist back then
      }
      dependencies {
          classpath 'com.android.tools.build:gradle:1.0.0'
      }
  }
  
  allprojects {
      repositories {
          mavenCentral()
      }
  }
  

• In gradle/wrapper/gradle-wrapper.properties, set the Gradle distribution to match AGP 1.0.0 (it requires Gradle 1.12):

  distributionUrl=https\://services.gradle.org/distributions/gradle-1.12-all.zip
  

2. Fix Configuration Syntax #

Modern Gradle changed how configurations are handled. For the java.lang.String cannot be cast to org.gradle.api.artifacts.Configuration error:

• Ensure all references to configurations use the correct syntax. Your fix plusConfigurations += [configurations.provided] is correct for older Gradle versions, but also:
  • Replace any implementation/api dependencies with compile (old Gradle uses compile instead of modern configuration names)
  • Replace testImplementation with testCompile

3. Clean Up and Reset #

Corrupted caches or daemon processes often make things worse:

• Go to File > Invalidate Caches... > Invalidate and Restart to clear Android Studio's cache
• Delete the .gradle folder in your project root and all build folders in modules
• If daemon issues persist, kill all Java processes manually:

  # Windows
  taskkill /F /IM java.exe
  # macOS/Linux
  pkill -f java
  

• Restart Android Studio and re-sync the project

Better Alternatives for Studying RxJava Old Versions #

Honestly, fighting with ancient build tools takes time away from actually learning the source code. Here are more efficient ways:

1. Browse Source Code Online #

You don't need to run the project to read the code. Go to GitHub's RxJava repo, switch to the 1.0.0 or 0.1.2 tag, and browse directly:

• Focus on core classes first: Observable, Subscriber, Subscription, and key operators like map/flatMap
• Look at how the subscription flow works (from Observable.subscribe() to Subscriber callbacks)

2. Add RxJava 1.x to a Modern Project #

Create a new, empty Android project (using modern Gradle/AGP) and just add RxJava 1.0.0 as a dependency in your app's build.gradle:

dependencies {
    implementation 'io.reactivex:rxjava:1.0.0'
}

This lets you write test code to experiment with RxJava 1.x, and you can still jump to the source code directly in Android Studio (hold Ctrl/Cmd and click any RxJava class).

3. Prioritize Core Concepts Over Exact Version Syntax #

The core ideas of RxJava (observable streams, operators, thread scheduling, subscription lifecycle) haven't changed much between versions. Start by understanding these concepts, then dive into how the 1.x implementation handles them—you'll get more value than struggling with build errors.

内容的提问来源于stack exchange，提问作者soNesso