2017-10-19 17:45 GMT+02:00 Ivan Kelly :
> >> > 4) Enabling debug for tests
> >> > If there any smarter way to enable debug in tests apart from changing
> and
> >> > not comming log4j.properties ?
> >> Why not just enable DEBUG by default, and exclude the overly noisy
> >> stuff like zookeeper?
> >
>> > 4) Enabling debug for tests
>> > If there any smarter way to enable debug in tests apart from changing and
>> > not comming log4j.properties ?
>> Why not just enable DEBUG by default, and exclude the overly noisy
>> stuff like zookeeper?
> mmm,
> writing a log of debug will slow up tests and m
2017-10-19 17:28 GMT+02:00 Ivan Kelly :
> inline.
>
> > 1) Surefire trimStackTrace can we set to "false" ?
> +1
>
> > 2) Protobuf checkStaleness set to "true" ?
> +1
>
> > 3) Problem with maven compiler plugin
> > even upgrading to latested and greatest version (3.7.0) it always
> considers
> > s
inline.
> 1) Surefire trimStackTrace can we set to "false" ?
+1
> 2) Protobuf checkStaleness set to "true" ?
+1
> 3) Problem with maven compiler plugin
> even upgrading to latested and greatest version (3.7.0) it always considers
> source files "changed" even while running single tests, this sl
Hi,
a bunch of issue in current "dev" environment:
1) Surefire trimStackTrace can we set to "false" ?
By default Surefire trims stacktraces, I always set it to "false" but I
have to keep a mofified local pom
2) Protobuf checkStaleness set to "true" ?
This will allow protoc to skip generaing java
