[MCHANGES-140] Create a changes check mojo

• Type: New Feature
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: 2.1
• Fix Version/s: 2.4
• Component/s: announcement
• Flags: Patch
• Assignee: Dennis Lundberg
• Reporter: Justin Edelson
• Created: 25/Nov/08 17:29
• Updated: 08/Apr/15 08:03
• Resolved: 16/Dec/10 17:23

Description

I meant to submit this for inclusion in changes 2.1, but I guess I just missed it (2.1.1maybe?).

We use the attached goal as part of release:prepare to ensure that the changes.xml has correct content before a release is done (changes:announcement-generate) is executed during release:perform.

It really does two things:
1) Ensures that the current version is represented in the changes.xml file (no special logic to do this, it's just in AnnouncementMjojo.getLatestRelease()).
2) Ensures that the current version's release date isn't "TBD" or "tbd". This could be easily changed to be "in SVN" through configuration. If you want to make this the default and I'll add config to our organizational pom to use "tbd", fine with me.

Since using this goal, we've eliminated a cause of release failures, so that's something...

Issue Links

• is duplicated by: MCHANGES-209 Checking the changes.xml file for release date and current version and fail if it is not