Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Adds a build scan screenshot rendering dynamic dependencies #3916

Merged
merged 1 commit into from
Dec 28, 2017
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Jump to
Jump to file
Failed to load files.
Diff view
Diff view
11 changes: 11 additions & 0 deletions subprojects/docs/src/docs/userguide/dependencyManagement.adoc
Expand Up @@ -93,6 +93,17 @@ Using dynamic versions in a build bears the risk of potentially breaking it. As
</sample>
++++

A link:https://scans.gradle.com/[build scan] can effectively visualize dynamic dependency versions and their respective, selected versions.

+++++
<figure xmlns:xi="http://www.w3.org/2001/XInclude">
<title>Dynamic dependencies in build scan</title>
<imageobject>
<imagedata fileref="img/dependency-management-dynamic-dependency-build-scan.png" width="135mm" />
</imageobject>
</figure>
+++++

By default, Gradle caches dynamic versions of dependencies for 24 hours. The <<sec:controlling_caching,threshold can be configured>> as needed for example if you want to resolve new versions earlier.

===== Declaring a changing version of a binary dependency
Expand Down
Sorry, something went wrong. Reload?
Sorry, we cannot display this file.
Sorry, this file is invalid so it cannot be displayed.