|
||||||||
|
This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators. For more information on JIRA, see: http://www.atlassian.com/software/jira |
||||||||
You received this message because you are subscribed to the Google Groups "Jenkins Issues" group.
To unsubscribe from this group and stop receiving emails from it, send an email to [email protected].
For more options, visit https://groups.google.com/d/optout.
Hi Francois,
I just discovered that the plugin passes build parameters to gradle as -D options. I'm using parameters to control behavior completely un-related to gradle, so was surprised by this. In fact, I've stopped using the plugin for the time being. It wasn't causing any problems per se, but I didn't want anyone inadvertently affect the gradle invocation in the future by adding a new parameter.
I'm sure there is a good reason build parameters are treated this way, but the use-case isn't obvious to me. Would you mind explaining the rationale behind this?