> On Dec 14, 2015, at 7:12 PM, Josh Elser <[email protected]> wrote:
>
> Hi,
>
> I've been playing around with yetus-0.1.0 RC1 on Accumulo (Maven-based Java
> project). I started doing something like the following:
>
> `cd accumulo.git; test-patch test-patch --jenkins --basedir=.
> --project=Accumulo --plugins='all' ~/ACCUMULO-XXXX.patch`
>
> This was going great, saw lots of plugins running. After my patch was
> applied, I noticed it that I stopped seeing output and CPU usage went way
> down. Best as I understand it: Yetus (with things inbetween these steps)
> built the Javadocs, applied the patch, and then calculated the diff of the
> patch. This ended up creating +500MB files (when I stopped it) because of the
> generated Javadocs being included in the diff calculation.
>
> I'd like to figure out what went wrong (if it's a bug or user-error) and how
> to look into this further. Any suggestions?
That is… interesting. Is there a personality to go with the project or
just using raw settings as on the command line?
I want to see if I can duplicate it.
