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

Consider adding GradleRunner#run() as an unopinionated alternative to build() #41

Open
lacasseio opened this issue Feb 13, 2021 · 1 comment

Comments

@lacasseio
Copy link
Member

The methods build() and buildAndFail() and opinionated on the outcome of the build. We should introduce run() which would be unopinionated on the state of the build. Users would have to validate the outcome.

The major reason against this API is there is no real valid reason to execute a Gradle build without expectation. For example, if we just want to execute task :foo, if we don't care about the outcome... would :foo execute successfully or not. Most likely, we would use build() so :foo is executed successfully, to the extent of what success means in the context.

@lacasseio lacasseio added this to the 1.4 milestone Feb 13, 2021
@lacasseio
Copy link
Member Author

There is a good chance we may not want to solve this issue unless we have a real use case.

@lacasseio lacasseio modified the milestones: 1.4, 1.5 Mar 9, 2021
@lacasseio lacasseio modified the milestones: 1.5, 1.6 Apr 10, 2021
@lacasseio lacasseio removed this from the 1.7 milestone Jan 17, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant