hudson.maven

Interface MavenBuildProxy2

All Superinterfaces:

MavenBuildProxy

All Known Implementing Classes:

AbstractMavenBuilder.FilterImpl, MavenBuild.ProxyImpl2, MavenBuildProxy2.Filter

public interface MavenBuildProxy2
extends MavenBuildProxy

A part of MavenBuildProxy that's used internally for aggregated build. Fired and consumed internally and not exposed to plugins.

Author:

Kohsuke Kawaguchi

Nested Class Summary

Nested Classes

Modifier and Type	Interface and Description
static class	MavenBuildProxy2.Filter<CORE extends MavenBuildProxy2> Filter for MavenBuildProxy2.

Nested classes/interfaces inherited from interface hudson.maven.MavenBuildProxy

MavenBuildProxy.BuildCallable<V,T extends Throwable>

Method Summary

Modifier and Type	Method and Description
void	appendLastLog() Maven produces additional error message after the module build is done.
void	end() Notifies that the build has left a module.
void	start() Notifies that the build has entered a module.

Methods inherited from interface hudson.maven.MavenBuildProxy

execute, executeAsync, getArtifactsDir, getMavenBuildInformation, getMilliSecsSinceBuildStart, getModuleSetRootDir, getProjectRootDir, getRootDir, getTimestamp, isArchivingDisabled, isSiteArchivingDisabled, queueArchiving, registerAsAggregatedProjectAction, registerAsProjectAction, registerAsProjectAction, setExecutedMojos, setResult

Method Detail

start

void start()

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.)

end

void end()

Notifies that the build has left a module.

appendLastLog

void appendLastLog()

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.