- 
    
Improvement
 - 
    Resolution: Fixed
 - 
    
Major
 - 
    1.448
 
Currently, in a Maven Project, fingerprints are generated for all build artifacts (created and used).
In a freestyle project, you can manually select files to be fingerprinted using the Fingerprinter publisher.
This needs to be possible for Maven Projects, too.
Consider for example a Maven project that uses post-build steps to create additional artifacts. You can archive them (without them being fingerprinted), but you cannot choose to fingerprint them.
Looking at hudson.tasks.Fingerprinter, I see no reason why this publisher should not be available for configuration.
If you enter the publisher by hand into the config.xml of a job, it works (until you reconfig that job, of course), so this seems to be a display issue. One small drawback: two fingerprintActions are included.
Tasks:
- make Fingerprinter available for Maven projects
 - prevent Fingerprinter from always creating a new FingerprintAction (i.e. let it check for any existing FingerprintActions (like MavenFingerprinter does))
 
the second part is trivial, I can create a pull request for that.
- depends on
 - 
                    
JENKINS-17606 Copy Artifact's fingerprinting creates second hudson.tasks.Fingerprinter_-FingerprintAction section with just the artifacts copied
-         
 - Closed
 
 -         
 
- is duplicated by
 - 
                    
JENKINS-18615 Add option do disable fingerprinting for maven jobs
-         
 - Resolved
 
 -         
 
- is related to
 - 
                    
JENKINS-19712 [Fingerprint] Excessive Heap consumption during "Waiting for Jenkins to finish collecting data"
-         
 - Open
 
 -         
 - 
                    
JENKINS-11814 Maven artifact fingerprints are computed and recorded twice
-         
 - Resolved
 
 -