Yes, you need to update the expected output in 'userguideOutput'.

- In automated testing, the userguideOutput is compared against the actual
output of executing the gradle command
- When generating the userguide, the userguideOutput is included as-is (no
tests are run at this time).


On Tue, Jul 8, 2014 at 2:17 PM, KARR, DAVID <dk0...@att.com> wrote:

> In my revisions of the userguide, I ended up changing a sample command
> line, and some lines in the associated "build.gradle" and
> "gradle.properties" files.  I expected that when I rebuilt the userguide,
> it would rerun the command line and regenerate the output.  For some reason
> this isn't happening.  I searched in the tree for a file containing the
> output I'm getting, and I found
> "subprojects/docs/src/samples/userguideOutput", which appears to contain
> the output files from the sample build scripts.  These are checked in, not
> generated at build time, so perhaps this build process isn't as automated
> as I thought.  Am I going to have to manually rerun the command line and
> replace the output file?
>
> ---------------------------------------------------------------------
> To unsubscribe from this list, please visit:
>
>     http://xircles.codehaus.org/manage_email
>
>
>


-- 
Darrell (Daz) DeBoer
http://www.gradleware.com

Reply via email to