Skip to content
Merged
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
11 changes: 6 additions & 5 deletions dev-guide/versions.md
Original file line number Diff line number Diff line change
Expand Up @@ -18,7 +18,7 @@ changes at HEAD. Unlike the [Dagger release artifacts](#release-artifacts), the
`HEAD-SNAPSHOT` artifacts are updated on each commit to the Dagger codebase.

Dagger's `HEAD-SNAPSHOT` artifacts can be found at
[https://oss.sonatype.org/content/repositories/snapshots/com/google/dagger/](https://oss.sonatype.org/content/repositories/snapshots/com/google/dagger/).
[https://central.sonatype.com/repository/maven-snapshots/com/google/dagger/](https://central.sonatype.com/repository/maven-snapshots/com/google/dagger/).

We don't recommended using the `HEAD-SNAPSHOT` artifacts in production, but it
can be used to test out, verify, or just give feedback on features that are not
Expand All @@ -40,22 +40,23 @@ dependencies {
```

Next, update your plugin and project repositories to include the Sonatype
snapshot url. This usually goes in your top-level `build.gradle` file. For
example:
snapshot url (see
https://central.sonatype.org/publish/publish-portal-snapshots/#consuming-via-gradle).
This usually goes in your top-level `build.gradle` file. For example:

```groovy
// top-level build.gradle file
buildscript {
repositories {
maven {
url "https://oss.sonatype.org/content/repositories/snapshots"
url "https://central.sonatype.com/repository/maven-snapshots"
}
}
}
allprojects {
repositories {
maven {
url "https://oss.sonatype.org/content/repositories/snapshots"
url "https://central.sonatype.com/repository/maven-snapshots"
}
}
}
Expand Down
Loading