You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Florian Brunner (JIRA)" <ji...@codehaus.org> on 2011/05/12 14:12:22 UTC
[jira] Created: (MCHANGES-240) Support: version="${poject.version}"
date="${buildDate}"
Support: version="${poject.version}" date="${buildDate}"
--------------------------------------------------------
Key: MCHANGES-240
URL: http://jira.codehaus.org/browse/MCHANGES-240
Project: Maven 2.x Changes Plugin
Issue Type: Bug
Components: changes.xml
Affects Versions: 2.4
Reporter: Florian Brunner
Priority: Critical
Currently the plugin requires a release version which is equal to ${poject.version} without "-SNAPSHOT".
Currently the changes.xml doesn't get filtered.
The actual version is only known when you do a relase (e.g. using the Maven Release Plugin).
It's then when you specify if you change e.g. from version 1.1.2 to 1.1.3 or 1.2.0
Keeping this in sync with the changes.xml is currently a manual process which has to be done immediatly before releasing and is thus very error prone (especially if you're releasing every day or every other day in a hot phase of the project)!
For this reason
<release version="${poject.version}"...
should be supported.
The same is true for the release date. You only know the exact date, when you're actually releasing.
Consider to provide the property ${buildDate}.
Provide a hook into the Maven Release Plugin, to add a new release element (after tagging, when the version gets updated to the next SNAPSHOT version):
<release version="${poject.version}" date="${buildDate}" description="Subsequent release">
</release>
--
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] (MCHANGES-240) Support: version="${poject.version}"
date="${buildDate}"
Posted by "Dennis Lundberg (JIRA)" <ji...@codehaus.org>.
[ https://jira.codehaus.org/browse/MCHANGES-240?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=296991#comment-296991 ]
Dennis Lundberg commented on MCHANGES-240:
------------------------------------------
I think this issue has merits. There are currently some manual work that needs to be done when using a changes.xml file. It would be nice if it could be more automatic.
> Support: version="${poject.version}" date="${buildDate}"
> --------------------------------------------------------
>
> Key: MCHANGES-240
> URL: https://jira.codehaus.org/browse/MCHANGES-240
> Project: Maven 2.x Changes Plugin
> Issue Type: Bug
> Components: changes.xml
> Affects Versions: 2.4
> Reporter: Florian Brunner
> Priority: Critical
>
> Currently the plugin requires a release version which is equal to ${poject.version} without "-SNAPSHOT".
> Currently the changes.xml doesn't get filtered.
> The actual version is only known when you do a relase (e.g. using the Maven Release Plugin).
> It's then when you specify if you change e.g. from version 1.1.2 to 1.1.3 or 1.2.0
> Keeping this in sync with the changes.xml is currently a manual process which has to be done immediatly before releasing and is thus very error prone (especially if you're releasing every day or every other day in a hot phase of the project)!
> For this reason
> <release version="${poject.version}"...
> should be supported.
> The same is true for the release date. You only know the exact date, when you're actually releasing.
> Consider to provide the property ${buildDate}.
> Provide a hook into the Maven Release Plugin, to add a new release element (after tagging, when the version gets updated to the next SNAPSHOT version):
> <release version="${poject.version}" date="${buildDate}" description="Subsequent release">
> </release>
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://jira.codehaus.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (MCHANGES-240) Support:
version="${poject.version}" date="${buildDate}"
Posted by "Dennis Lundberg (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MCHANGES-240?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=266535#action_266535 ]
Dennis Lundberg commented on MCHANGES-240:
------------------------------------------
The process should not be error prone. The current version of the plugin already checks that the version in changes.xml is in sync with the version in the POM.
Using the changes-check goal you can make sure that a valid date has been entered in the changes.xml file.
> Support: version="${poject.version}" date="${buildDate}"
> --------------------------------------------------------
>
> Key: MCHANGES-240
> URL: http://jira.codehaus.org/browse/MCHANGES-240
> Project: Maven 2.x Changes Plugin
> Issue Type: Bug
> Components: changes.xml
> Affects Versions: 2.4
> Reporter: Florian Brunner
> Priority: Critical
>
> Currently the plugin requires a release version which is equal to ${poject.version} without "-SNAPSHOT".
> Currently the changes.xml doesn't get filtered.
> The actual version is only known when you do a relase (e.g. using the Maven Release Plugin).
> It's then when you specify if you change e.g. from version 1.1.2 to 1.1.3 or 1.2.0
> Keeping this in sync with the changes.xml is currently a manual process which has to be done immediatly before releasing and is thus very error prone (especially if you're releasing every day or every other day in a hot phase of the project)!
> For this reason
> <release version="${poject.version}"...
> should be supported.
> The same is true for the release date. You only know the exact date, when you're actually releasing.
> Consider to provide the property ${buildDate}.
> Provide a hook into the Maven Release Plugin, to add a new release element (after tagging, when the version gets updated to the next SNAPSHOT version):
> <release version="${poject.version}" date="${buildDate}" description="Subsequent release">
> </release>
--
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] (MCHANGES-240) Support: version="${poject.version}"
date="${buildDate}"
Posted by "Benson Margulies (JIRA)" <ji...@codehaus.org>.
[ https://jira.codehaus.org/browse/MCHANGES-240?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=296985#comment-296985 ]
Benson Margulies commented on MCHANGES-240:
-------------------------------------------
Dennis, seems like you don't like this idea at all. Should this JIRA be closed?
> Support: version="${poject.version}" date="${buildDate}"
> --------------------------------------------------------
>
> Key: MCHANGES-240
> URL: https://jira.codehaus.org/browse/MCHANGES-240
> Project: Maven 2.x Changes Plugin
> Issue Type: Bug
> Components: changes.xml
> Affects Versions: 2.4
> Reporter: Florian Brunner
> Priority: Critical
>
> Currently the plugin requires a release version which is equal to ${poject.version} without "-SNAPSHOT".
> Currently the changes.xml doesn't get filtered.
> The actual version is only known when you do a relase (e.g. using the Maven Release Plugin).
> It's then when you specify if you change e.g. from version 1.1.2 to 1.1.3 or 1.2.0
> Keeping this in sync with the changes.xml is currently a manual process which has to be done immediatly before releasing and is thus very error prone (especially if you're releasing every day or every other day in a hot phase of the project)!
> For this reason
> <release version="${poject.version}"...
> should be supported.
> The same is true for the release date. You only know the exact date, when you're actually releasing.
> Consider to provide the property ${buildDate}.
> Provide a hook into the Maven Release Plugin, to add a new release element (after tagging, when the version gets updated to the next SNAPSHOT version):
> <release version="${poject.version}" date="${buildDate}" description="Subsequent release">
> </release>
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://jira.codehaus.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira