Hervé,
Maven Monitor was a Maven 2 artifact [1]
> It was dropped in Maven 3 "as an artifact": code was moved to maven-core
> during the Great Refactoring (TM) [2]
>
>
Thanks - it's a total red herring to chase that component then.
> Then you'll see that EventMonitor has been deprecated, in
Maven Monitor was a Maven 2 artifact [1]
It was dropped in Maven 3 "as an artifact": code was moved to maven-core
during the Great Refactoring (TM) [2]
Then you'll see that EventMonitor has been deprecated, in favor of EventSpy in
Maven 3.0.2 I think: we should probably improve the javadoc...
Given the version spread of Maven-Monitor above (v2.0.5 and v2.0.9 needed
to build v2.2.1) I'd love to get some advice to how to attach breakpoints
in use to see the pertinent methods invoked during a build. I mean I've
attached breakpoints and then done mvnDebug but the breakpoints are not hit.
I''m looking to make a build radiator. Something like this -
https://www.stevefenton.co.uk/wp-content/uploads/2015/07/cruiser.jpg
I don't want to scrape logs to detect maven phase changes, and
corresponding pass/fail, I want to use a plugin. I think that plugin
is Maven-monitor
Online