You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Leif Nelson (JIRA)" <ji...@codehaus.org> on 2008/11/14 18:40:15 UTC
[jira] Created: (MCHANGES-131) It would be nice if the announcement
plugin bound to the validate phase to make sure changes.xml exists and has
the proper versions in it.
It would be nice if the announcement plugin bound to the validate phase to make sure changes.xml exists and has the proper versions in it.
------------------------------------------------------------------------------------------------------------------------------------------
Key: MCHANGES-131
URL: http://jira.codehaus.org/browse/MCHANGES-131
Project: Maven 2.x Changes Plugin
Issue Type: Wish
Components: announcement
Reporter: Leif Nelson
When using the announcement-generate goal in concert with the release plugin, it would be nice if the announcement plugin was invoked in the validate phase. When doing a release:prepare release:perform, the announcement plugin will cause the build to fail "after" the poms have been committed and the version has been tagged, if you forget to update the changes.xml file. If the announcement plugin bound to the validate phase, it would be called during the release:prepare step, and could force the release to fail during validate (if changes.xml wasn't config'd right) "before" the commit/tagging operations were completed. This would be a nice feature. :-)
Thanks!
--
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
[jira] Closed: (MCHANGES-131) It would be nice if the announcement
plugin bound to the validate phase to make sure changes.xml exists and has
the proper versions in it.
Posted by "Dennis Lundberg (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MCHANGES-131?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Dennis Lundberg closed MCHANGES-131.
------------------------------------
Resolution: Not A Bug
The announcement goals are not bound to any phase by default. That's because different users have different requirements for which phase, if any, they want them to be bound to.
You can easily bind it yourself using an execution.
You can also use the "changes:changes-validate" goal to verify that your changes.xml file is valid.
> It would be nice if the announcement plugin bound to the validate phase to make sure changes.xml exists and has the proper versions in it.
> ------------------------------------------------------------------------------------------------------------------------------------------
>
> Key: MCHANGES-131
> URL: http://jira.codehaus.org/browse/MCHANGES-131
> Project: Maven 2.x Changes Plugin
> Issue Type: Wish
> Components: announcement
> Reporter: Leif Nelson
>
> When using the announcement-generate goal in concert with the release plugin, it would be nice if the announcement plugin was invoked in the validate phase. When doing a release:prepare release:perform, the announcement plugin will cause the build to fail "after" the poms have been committed and the version has been tagged, if you forget to update the changes.xml file. If the announcement plugin bound to the validate phase, it would be called during the release:prepare step, and could force the release to fail during validate (if changes.xml wasn't config'd right) "before" the commit/tagging operations were completed. This would be a nice feature. :-)
> Thanks!
--
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