[ACCUMULO-3172] mavanagaiata plugin marks releases "dirty"

• Type: Bug
• Status: Resolved
• Priority: Blocker
• Resolution: Fixed
• Fix Version/s: 1.5.3, 1.6.2, 1.7.0
• Component/s: build
• Assignee: Christopher Tubbs
• Reporter: Christopher Tubbs
• Created: 25/Sep/14 21:48
• Updated: 20/Feb/15 22:29
• Resolved: 18/Dec/14 20:58

Description

The mavanagaiata plugin we use to populate the build number in the META-INF/MANIFEST.MF file appends "-dirty" to the git commit hash. I believe this is probably done because the release plugin is adding additional files to the working branch, but I can't be sure.

We should alter the build such that the MANIFEST.MF files don't indicate it was built from a dirty state when it wasn't.

Further, if possible, we should fail the release:prepare goal if it tries to build from a dirty state initially. I know this was a feature of the buildnumber-maven-plugin, but it doesn't appear to be an option for this mavanagaiata one (why did we switch when we added this field back to the manifest files?)

See https://github.com/koraktor/mavanagaiata/issues/34

Issue Links

• is related to: ACCUMULO-3610 Update mavanagaiata plugin to 0.7.1