In, why use over Gradle's javaexec?

wenslayer's Avatar


17 Dec, 2015 09:29 PM

Hi there, more of an implementation choice question, but I'm curious why you chose to use the Ant mechanism to call the jar, as opposed to using Gradle's native javaexec method. Did you try earlier, but were thwarted in some way (output processing, parallelization, etc.)?
Thanks for your insight.

  1. Support Staff 1 Posted by Yennick Trevels on 19 Dec, 2015 11:24 AM

    Yennick Trevels's Avatar

    No specific reason actually. I think it's more related to the fact that this javaexec task was added in Gradle 0.9 and probably not that well documented by the time we started GradleFx (using Gradle 1.0-milestone3), therefore not knowing about its existence.

Reply to this discussion

Internal reply

Formatting help / Preview (switch to plain text) No formatting (switch to Markdown)

Attaching KB article:


Attached Files

You can attach files up to 10MB

If you don't have an account yet, we need to confirm you're human and not a machine trying to post spam.

Keyboard shortcuts


? Show this help
ESC Blurs the current field

Comment Form

r Focus the comment reply box
^ + ↩ Submit the comment

You can use Command ⌘ instead of Control ^ on Mac