Package hudson.maven

Class MavenBuildProxy2.Filter<CORE extends MavenBuildProxy2>

java.lang.Object
hudson.maven.MavenBuildProxy.Filter<CORE>
hudson.maven.MavenBuildProxy2.Filter<CORE>
All Implemented Interfaces:
MavenBuildProxy, MavenBuildProxy2, Serializable
Direct Known Subclasses:
AbstractMavenBuilder.FilterImpl
Enclosing interface:
MavenBuildProxy2

public abstract static class MavenBuildProxy2.Filter<CORE extends MavenBuildProxy2> extends MavenBuildProxy.Filter<CORE> implements MavenBuildProxy2
Filter for MavenBuildProxy2. Meant to be useful as the base class for other filters.
See Also:
  • Constructor Details

    • Filter

      protected Filter(CORE core)
  • Method Details

    • start

      public void start()
      Description copied from interface: MavenBuildProxy2
      Notifies that the build has entered a module. Jenkins has a somewhat simplified view of the sequence of events in a Maven build. Namely, a Maven build can be building a particular Maven module, and start and end marks that boundary. Note that Maven can be in a state that it's not building any module, for example when executing an aggregator mojo, and start/end cannot be nested (which right now means a forked lifecycle doesn't result in the event firing.)
      Specified by:
      start in interface MavenBuildProxy2
    • end

      public void end()
      Description copied from interface: MavenBuildProxy2
      Notifies that the build has left a module.
      Specified by:
      end in interface MavenBuildProxy2
    • appendLastLog

      public void appendLastLog()
      Description copied from interface: MavenBuildProxy2
      Maven produces additional error message after the module build is done. So to catch those messages, invoke this method on the last module that was built after all the Maven processing is done, to append last messages to the console output of the module.
      Specified by:
      appendLastLog in interface MavenBuildProxy2