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... HTH, Hervé [1] http://maven.apache.org/ref/2.2.1/ [2] http://maven.apache.org/ref/3.0/ Le mercredi 17 mai 2017, 10:43:20 CEST Paul Hammant a écrit : > 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 trying to work out what a phase listener would look like, and thought > that the closed API to something that participates in the phase traversal > is MavenMonitor. Advice please? > > - Paul > > On Fri, May 12, 2017 at 6:01 AM, Paul Hammant <[email protected]> wrote: > > 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 documentation for that is here http://maven.apache.org/ref/2. > > 2.1/maven-monitor/ and that doesn't say much, except to direct the user > > to subversion (where the plugin still resides). > > > > In use a few versions can be downloaded* - meaning even if I could make my > > own version of Maven monitor, I would struggle to get it used exclusively > > through the entire 'mvn' invocation. > > > > Advice ? > > > > * e.g.the build for maven-monitor-2.2.1 downloads v2.0.5 AND v2.0.9 of > > itself. Different projects are going to download/use multiple different > > versions of course. > > > > - Paul --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
