You are viewing a plain text version of this content. The canonical link for it is here.

Posted to issues@maven.apache.org by "Dennis Lundberg (JIRA)" <ji...@codehaus.org> on 2010/12/15 20:36:59 UTC

[jira] Updated: (MCHANGES-209) Checking the changes.xml file for release date and current version and fail if it is not

     [ http://jira.codehaus.org/browse/MCHANGES-209?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Dennis Lundberg updated MCHANGES-209:
-------------------------------------

    Component/s: changes.xml

> Checking the changes.xml file for release date and current version and fail if it is not
> ----------------------------------------------------------------------------------------
>
>                 Key: MCHANGES-209
>                 URL: http://jira.codehaus.org/browse/MCHANGES-209
>             Project: Maven 2.x Changes Plugin
>          Issue Type: New Feature
>          Components: changes.xml
>         Environment: all
>            Reporter: Karl Heinz Marbaise
>
> I would like to know if anybody has thought about the possibility to do some checks on the changes.xml file during a release process or before.
> My ideas are as follows:
> First check if a release entry does exist which contains a date of today (day of release) and a version which is relationship with the pom from where the changes-plugin is used. 

-- 
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