Make project relocatable by using relative paths in the OSGi test task #2920
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…in the OSGi test task.
runningcode
reviewed
Feb 21, 2023
Co-authored-by: Nelson Osacky <nelson@osacky.com>
Co-authored-by: Nelson Osacky <nelson@osacky.com>
runningcode
approved these changes
Feb 21, 2023
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Make classpath elements and sources use relative paths, instead of the default absolute paths. This makes the build more cacheable when the checkout locations are different on the file system.
I discovered this while trying Gradle Enterprise, and a public build scan that shows everything comes from the cache is here.