Thank you. Yes, I was able to find it. It was not in the stacktrace, but there was a single line above the report which gave me info as to why it failed.
Thx, Will *Will STEVENS* Lead Developer *CloudOps* *| *Cloud Solutions Experts 420 rue Guy *|* Montreal *|* Quebec *|* H3J 1S6 w cloudops.com *|* tw @CloudOps_ On Fri, Aug 29, 2014 at 11:40 AM, Marcus <shadow...@gmail.com> wrote: > They don't? I've always been able to find something in the maven output > pointing to a line with trailing spaces or something. It just isn't the > very last thing it prints. If you're not compiling multi-threaded (e.g. > mvn -T C1.5) then it's usually 100 or so lines up, above the report. If you > ARE multithreaded, it can be anywhere. > > > On Fri, Aug 29, 2014 at 9:11 AM, Will Stevens <wstev...@cloudops.com> > wrote: > > > How are we supposed to verify and fix the cloudstack-checkstyle errors? > > The stack traces do not give any feedback at all for where the error > > occurred so it is basically impossible to have a good code/test/fix cycle > > with it. > > > > Any ideas??? > > > > *Will STEVENS* > > Lead Developer > > > > *CloudOps* *| *Cloud Solutions Experts > > 420 rue Guy *|* Montreal *|* Quebec *|* H3J 1S6 > > w cloudops.com *|* tw @CloudOps_ > > >
