dependency graph. This functionality is enabled through a feature flag,
hudson.tasks.Fingerprinter.enableFingerprintsInDependencyGraph, which is off
by default.

- Rebuild the dependency graph as part of each fingerprint action.
  Fingerprinter.buildDependencyGraph adds information to the dependency graph
  for projects found in fingerprint records. Since the dependency graph is
  based on project, once a relationship is established between two projects,
  we can skip scanning subsequent builds of the projects. Entries in the
  graph added by the fingerprinter action will never automatically trigger
  downstream builds.

   core/src/main/java/hudson/tasks/Fingerprinter.java

- When reporting dependency changes, don't consider builds that no longer
  exist. This handles issues when projects are renamed, and new projects are
  created using the same name, causing the change to point to incorrect
  builds.

   core/src/main/java/hudson/model/AbstractBuild.java

- Tests.

   test/src/test/java/hudson/tasks/FingerprinterTest.java

Previously, array was copied 3 times, now only once.

Dependency

Just import changes, from hudson.model.Jenkins -> jenkins.model.Jenkins,
and Javadoc comments.
Signed-off-by: NNigel Magnay <nigel.magnay@gmail.com>

Signed-off-by: NNigel Magnay <nigel.magnay@gmail.com>

Pull individual Dependencys out of DependencyGroups we see in
BuildTrigger.execute and make sure to actually kick those builds off
as well, so that we can have two different dependencies (say, for
different parameters) from one upstream project to a single downstream
project.

Maven2/3 jobs using Maven3 in console output.
With Maven3 the output format for mojos has changed:
- Add a new Maven3MojoNote and use it in MavenConsoleAnnotator.
- This is sufficient for Freestyle jobs running Maven2 or 3 and Maven2/3
  jobs running Maven 2.
- Maven2/3 jobs running Maven 3 are using ExecutionEventLogger for
  printing start of mojo execution to console.

fix link to javadoc in maven modules, archiving test javadoc test too , still need to display link to test javadoc

build

tasks.Mailer          from,subject,failureOnly,charset 1.10
model.Project         slave                            1.60
model.Descriptor      properties                       1.62
model.Slave           command,localFS                  1.69
model.AbstractProject enableRemoteTrigger              1.77
model.FingerprintMap  core                             1.91
If anyone still has very old XML with these, OldDataMonitor will
still handle it (as unreadable data instead of old data, and
with a bit more noise in the log).