Hi Scott, thanks for your suggestions.
It turns out it wasn't a Maven or caching problem: everything made
more sense in the morning. My issue was Arquillian not running the
tests on the correct deployments, which explains why the log messages
weren't being triggered as the configuration wouldn't ma
> I'm starting to wonder if actually sometimes Maven runs my integration
> tests using a previous SNAPSHOT build, which would be missing both the
> logs and the fix, and in those cases it could either fail or not (as
> it wasn't always reproduced).
>
> Anyone else ever seen such an issue?
>
I wor
The build just failed once again; the log messages *are missing*, and
my Maven cache was empty.
On 9 July 2015 at 23:29, Sanne Grinovero wrote:
> I'm attempting to debug a subtle issue which I can only reproduce
> occasionally; to do so, I've been adding some improved logging to a
> module A, whi
