|
||||||||
|
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 jenkinsci-issues+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
While working on a workaround, i found the problem: if the project is not checked out into the workspace directly, but into a subfolder (say: trunk), the gradle wrapper ist started, the project is found and run, but gradle gets bent out of shape w/ regard to its internal root project/ project/ module/ folder setup, and does not find default tasks. Weird. Would expect an error message at least.
When checking out into the workspace directly, everything works fine.