[
http://jira.codehaus.org/browse/MCHANGES-140?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=199596#action_199596
]
Dennis Lundberg commented on MCHANGES-140:
------------------------------------------
I like this, it adds one more level of checking of the changes.xml file on top
of what "changes-validate" already does.
I would prefer to call the goal "changes-check" instead, because the
"announcement-generate" goal works with more than just changes.xml files. It
can fetch releases from JIRA as well.
What do you think Justin?
> Create an announcement check mojo
> ---------------------------------
>
> Key: MCHANGES-140
> URL: http://jira.codehaus.org/browse/MCHANGES-140
> Project: Maven 2.x Changes Plugin
> Issue Type: Improvement
> Components: announcement
> Affects Versions: 2.1
> Reporter: Justin Edelson
> Attachments: AnnouncementCheckMojo.java
>
>
> 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...
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
