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

fix: error handling for gradle wrapper call #4370

Merged
merged 1 commit into from
Oct 4, 2019

Conversation

maxandersen
Copy link
Member

Why:

  • if something wrong gradle wrapper would just exit withuot info/error.

This change addreses the need by:

  • Use ProcessBuilder to easily direct input/output/error to mvn output
  • Check the error code and warn via error
  • Don't pass empty env to the fork as otherwise JAVA_HOME is not picked
    up.

Note - Generated Gradle builds will still fail but that is due to
#4365 - a separate concern.

Fixes #4321

Why:

 * if something wrong gradle wrapper would just exit withuot info/error.

This change addreses the need by:

 * Use `ProcessBuilder` to easily direct input/output/error to mvn output
 * Check the error code and warn via error
 * Don't pass empty env to the fork as otherwise JAVA_HOME is not picked
   up.

Note - Generated Gradle builds will still fail but that is due to
quarkusio#4365 - a separate concern.

Fixes quarkusio#4321
@aloubyansky aloubyansky added this to the 0.24.0 milestone Oct 4, 2019
@aloubyansky aloubyansky added the triage/waiting-for-ci Ready to merge when CI successfully finishes label Oct 4, 2019
@kenfinnigan kenfinnigan merged commit 7aaa641 into quarkusio:master Oct 4, 2019
@kenfinnigan kenfinnigan removed the triage/waiting-for-ci Ready to merge when CI successfully finishes label Oct 4, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

gradle project generation does not include gradle wrapper
3 participants