Package hudson.maven
General Idea
One of the pain points of the freestyle project is that you have to configure a lot of things, such as where to look for test reports, what files to archive, where the findbugs report would go. But if we focus on Maven, we should be able to eliminate much of the configuration, since it introduces more uniform structures. So that's what this plugin does — at the expense of limiting the build tool to Maven, automate much of the configuration.
Implementation Approach
The core idea of the implementation is to monitor what Maven does, so that we can see which mojos are executed with what parameters. In this way, we can tell when/where javadoc is generated, if source code compilation had an error, and access other rich information about the project build process.
To make communication between Hudson JVM and Maven JVM easier, we use the remoting technology that Hudson uses between the controller and the agent. We start a new JVM and bootstraps to the remoting, then use a socket to establish a connection to this process. This part of the code is in the "maven-agent" module. We then bootstrap Maven.
To intercept what's going on in Maven, we extend some key components in Maven, and configure Plexus in such a way that our components are used instead of default ones. Because injected components need to live in a different classloader, they are packaged in a separate "maven-interceptor" module. We also bring in objects (MavenReporters) from plugins via remoting, and distribute intercepted events to these guys. They can then digest information and send it back to Hudson JVM.
In addition to all this, we use embedded Maven to parse POMs, so that we can figure out the structure of the project before we even do a build (this information is used for example to set up dependencies among jobs.) This turns out to be rather fragile (in the presence of profiles that are activated by system property, platform, etc., which makes the effective POM different when in Hudson vs when built for real.)
- 
ClassDescriptionLaunches the maven process.Common part betweenMavenModuleandMavenModuleSet.Indicates that thisActionforMavenBuildcontributes an "aggregated" action toits governing MavenModuleSetBuild.Persisted record of mojo execution.Used during the HTML rendering to cache the index.ChangeLogSetimplementation used forMavenBuild.AbstractMavenProcessFactoryfor Maven 3.AbstractMavenProcessFactoryfor Maven 3.2.xAbstractMavenProcessFactoryfor Maven 3.3.xAbstractMavenProcessFactoryfor Maven 3.5.xAbstractMavenProcessFactoryfor Maven 3.Finds classworlds.jarActionto be associated withMavenModuleSetBuild, which usually displays some aspect of the aggregated results of the module builds (such as aggregated test result, aggregated coverage report, etc.)Provides a hook to change the arguments passed to the maven execution.RunforMavenModule.Callablethat invokes Maven CLI (in process) and drives a build.Remoting proxy interface forMavenReporters to talk toMavenBuildduring the build.MavenBuildProxy.BuildCallable<V,T extends Throwable> MavenBuildProxy.Filter<CORE extends MavenBuildProxy>Filter forMavenBuildProxy.Callablefor invokingMavenBuildProxy.BuildCallableasynchronously.A part ofMavenBuildProxythat's used internally for aggregated build.MavenBuildProxy2.Filter<CORE extends MavenBuildProxy2>Filter forMavenBuildProxy2.Jobthat builds projects based on Maven2.Group ofMavenModules.BuildforMavenModuleSet.will log in theTaskListenerwhen transferFailed and transferSucceededUI for probing Maven process.Can contribute to project actions.Listens to the build execution ofMavenBuild, and normally records some information and exposes thoses inMavenBuildlater.DescriptorforMavenReporter.Information aboutMavenReportthat was executed.AugmentsSurefireReportby executingTestDataPublishers.Generated localization support class.group id + artifact id + version and a flag to know if it's a pluginVersion independent name of a Maven project.Information about Mojo to be executed.Instance will be set toMojoInfo.mojoto avoid NPE in plugins.Action signalling that thisMavenModuleSetneeds a full build on the next run even if it's marked as an incremental build.Contributes additional code into Plexus container when we run Maven.Contributes additional code into Plexus container when we run Maven.Identifier of a specific version of a Maven plugin that consists of groupId, artifactId, and version.Hold on to launched Maven processes so that multiple builds can reuse the same Maven JVM, which leads to improved performance.PublisherforMavenModuleSetBuildto deploy artifacts after a build is fully succeeded.Identify the Host name to use from maven-agent to connect to to Jenkins agent TCP socket.Action which remembers all module which have not been built since the last successful build though they should have been, because they have SCM changes since then.