![]() |
|
|
|
|
Change By:
|
Frédéric Camblor
(04/Oct/12 4:25 PM)
|
|
Summary:
|
Root
When using gradlew, root
build script field is
never
not
used
to locate gradlew
|
|
Priority:
|
Critical
Minor
|
|
Description:
|
It seems "root build script"
field
is
always omitted
not really well taken when using gradlew
.
For instance, I have a git repository having a foo/build.gradle script.
I then set "root build script" to "${WORKSPACE}/foo/"
I'm using gradlew.
I would like to
either
execute
{code}
${WORKSPACE}/foo/gradlew
{code}
_or_ execute
But for now, it is some sort of :
{code}
${WORKSPACE}/gradlew -p ${WORKSPACE}/foo
{code}
But for now, it is :
{code}
${WORKSPACE}/
I think we should define
gradlew
{code}
which is executed, not using foo/build.gradle script.
Not that it isn't related
location (relative
to
gradlew since when using a gradle installation
checked out root repository) because for the moment
,
it remains
the
same.
I tried
only way
to
put ${WORKSPACE}/foo/build.gradle in "Build file" field as a
workaround
, but it didn't worked either (build script
the problem
is
taken, but with -b, not -p which seems reasonable)
to put gradlew in the root scm hierarchy
|
|
|
|
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
|
