Gradle - Allow not using the -b parameter #631
Merged
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.
Resolves #583
Backgroud
-b flag is depracated and will be removed in Gradle 8.
The problem
There are 2 path parameters provided to the user:
rootDir
andbuildFile
.Currently, the Jenkins Artifactory plugin concatenates them to 1 path variable and passes it to Gradle as the following:
gradle clean aP -b <rootDir>/<buildFile>
.No matter what, it always provides the -b parameter to Gradle.
The solution
Use the -b parameter for
buildFile
and-p
parameter forrootDir
:gradle clean ap -b <buildFile> -p <rootDir>
.This way, when the
buildFile
parameter doesn't being provided, the -b flag is not in use.Users who want to migrate to Gradle 8, just need to make sure to not provide the
buildFile
parameter, because it same as running gradle with -b.