build(samples): Link the Android sample's Gradle files to the SDK build's

gradle.properties, gradlew, gradle/wrapper and
gradle/gradle-daemon-jvm.properties are now symlinks to the SDK build's
files. Both builds pick the same daemon JDK and JVM arguments, so they
can share a daemon, and the sample reads the SDK version from the
versionName property instead of parsing the root file.

The copied gradle.properties had drifted from the root one (-Xmx6g and
CrashOnOutOfMemoryError instead of -Xmx8g and HeapDumpOnOutOfMemoryError).

Dependabot also scans the sample build, so the Develocity plugins in its
settings stay current.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

Author: runningcode

.github/dependabot.yml

@@ -7,7 +7,10 @@ registries:
     password: dummy # Required by dependabot
 updates:
   - package-ecosystem: "gradle"
-    directory: "/"
+    # The Android sample is a separate build that the root build doesn't include.
+    directories:
+      - "/"
+      - "/sentry-samples/sentry-samples-android"
     registries:
       - gradle-plugin-portal
     schedule:

sentry-samples/sentry-samples-android/README.md

@@ -15,14 +15,15 @@ or open the `sentry-samples/sentry-samples-android` directory in Android Studio
 
 The sample is a separate Gradle build that includes the SDK build, so changes to the SDK show up in the next build of the sample, with nothing to publish first.
 The SDK build doesn't include the sample, so `./gradlew` from the repository root doesn't build, lint or format it.
+`gradle.properties`, `gradlew`, `gradle/wrapper` and `gradle/gradle-daemon-jvm.properties` are symlinks to the SDK build's, so both builds use the same Gradle, JDK and settings.
 
 You can also apply the [Sentry Android Gradle Plugin](https://github.com/getsentry/sentry-android-gradle-plugin) (SAGP) when building (not applied by default):
 
 ```
 ./gradlew -p sentry-samples/sentry-samples-android installDebug -PuseSagp
 ```
 
-In Android Studio, add `useSagp=` (empty value) to the sample's `gradle.properties`, or pass `-PuseSagp` as a Gradle project property.
+In Android Studio, add `useSagp=` (empty value) to `gradle.properties`, or pass `-PuseSagp` as a Gradle project property.
 
 For LLM-driven verification, use `adb` to inspect and interact with the running emulator. Compose-based screens often expose stable
 `Modifier.testTag()` values, which can be used with the UI hierarchy dump to locate controls reliably.

sentry-samples/sentry-samples-android/build.gradle.kts

@@ -18,7 +18,8 @@ plugins {
   alias(libs.plugins.sqldelight)
 }
 
-val sentryVersion = libs.versions.sentry.get()
+// gradle.properties links to the SDK build's, so this is the SDK version.
+val sentryVersion = providers.gradleProperty("versionName").get()
 
 if (providers.gradleProperty("useSagp").isPresent) {
   apply(plugin = "io.sentry.android.gradle")

sentry-samples/sentry-samples-android/gradle.properties

@@ -0,0 +1 @@
+../../gradle.properties

sentry-samples/sentry-samples-android/gradle.properties

@@ -0,0 +1 @@
+../../../gradle/gradle-daemon-jvm.properties

sentry-samples/sentry-samples-android/gradle/gradle-daemon-jvm.properties

@@ -0,0 +1 @@
+../../../gradle/wrapper

sentry-samples/sentry-samples-android/gradle/wrapper

@@ -44,27 +44,13 @@ develocity {
   }
 }
 
-// Gradle reads gradle.properties only for the build it belongs to, so read the SDK version from the
-// SDK build's file.
-val sentryVersion: String =
-  providers
-    .fileContents(layout.settingsDirectory.file("../../gradle.properties"))
-    .asText
-    .map { java.util.Properties().apply { load(it.reader()) }.getProperty("versionName") }
-    .get()
-
 dependencyResolutionManagement {
   repositories {
     google()
     mavenCentral()
     mavenLocal()
   }
-  versionCatalogs {
-    create("libs") {
-      from(files("../../gradle/libs.versions.toml"))
-      version("sentry", sentryVersion)
-    }
-  }
+  versionCatalogs { create("libs") { from(files("../../gradle/libs.versions.toml")) } }
 }
 
 rootProject.name = "sentry-samples-android"