listener.getLogger (as MavenCli). In this manner output is highlighted.

way as MavenCli do.

- integrated the newer release of remoting
- jar caching won't work with class file directory, so plugin
  WEB-INF/classes are now exploded as WEB-INF/lib/classes.jar
  (This should also solve the problem of slow plugin extraction in the
  presene of Anti-virus software on Windows.)
- because the structure of the exploded jar file has changed, I changed
  the up-to-date check timestamp file name to force re-extraction in
  existing installations.

This came up with a conversation with JFrog folks who neede to insert a
custom Plexus component to tweak the behaviour.

This scheme allows the caller to insert additional jar files into the
Maven process.

to determine which test result files belong to the mojo execution

The javadoc of MavenReporter states clearly that preBuild/postBuild is
only once per the entire build, but the previous code was calling it at
the same timing as enter/leaveModule.

This is now fixed.

Previously, a forked life cycle resulted in MavenBuildProxy2.start/end callbacks. When a module X build forks a life cycle and comes back to building module X, end callback from the fork completion made Jenkins believe that it's not building any module, when Maven is actually coming back to building module X.

So if the sequence of mojos that follow the forked mojo produces a lot of output, it can saturate memory (and even if it doesn't, Jenkins fails to capture the entire log for a module.)

This fix also addresses the synchronization problem, so that when we do split the log, we make sure all the output from Maven prior to that indeed arrived to the master.

[JENKINS-11458] Channel.current() is only available from the thread that's executing the remote call, and that's why we saw this original error, when Maven uses a thread pool to call into this method from another worker thread.

[JENKINS-11458] when building with Maven 3, Channel.current() inside FilterImpl sometimes returns null. Therefore pass channel into constructor, thus effectively restoring pre-1.435 behaviour.

- removed duplicated FilterImpl classes

that this feature is now deprecated.

By the time MavenModuleSetBuild.notifyModuleBuild() is called, we need the processing on one module to be completed.