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

Gradle should use its own install as a source for artifact files reuse #10744

Closed
eskatos opened this issue Sep 17, 2019 · 2 comments
Closed

Gradle should use its own install as a source for artifact files reuse #10744

eskatos opened this issue Sep 17, 2019 · 2 comments
Labels

Comments

@eskatos
Copy link
Member

eskatos commented Sep 17, 2019

The Gradle distribution contains artifact files for a number of modules (e.g. asm, http-client, xerces, aws-java, commons-*, kotlin etc...). When a build depends on the same artifacts as shipped with Gradle, downloading the artifact files could be avoided.

This issue is about augmenting artifact reuse, see https://docs.gradle.org/5.6.2/userguide/dependency_cache.html#sub:cache_artifact_reuse

Expected Behavior

Gradle reuses the artifact files from its own install when they match.

Current Behavior

Gradle downloads artifact files that are already bundled in its own install.

Context

#10701

@eskatos eskatos changed the title Gradle should use its own install as a source for artifact files Gradle should use its own install as a source for artifact files reuse Sep 17, 2019
@ljacomet ljacomet added the @jvm label Feb 17, 2020
@stale
Copy link

stale bot commented Feb 16, 2021

This issue has been automatically marked as stale because it has not had recent activity. Given the limited bandwidth of the team, it will be automatically closed if no further activity occurs. If you're interested in how we try to keep the backlog in a healthy state, please read our blog post on how we refine our backlog. If you feel this is something you could contribute, please have a look at our Contributor Guide. Thank you for your contribution.

@stale stale bot added the stale label Feb 16, 2021
@stale
Copy link

stale bot commented Mar 9, 2021

This issue has been automatically closed due to inactivity. If you can reproduce this on a recent version of Gradle or if you have a good use case for this feature, please feel free to reopen the issue with steps to reproduce, a quick explanation of your use case or a high-quality pull request.

@stale stale bot closed this as completed Mar 9, 2021
@wolfs wolfs closed this as not planned Won't fix, can't repro, duplicate, stale Sep 16, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

3 participants