[
https://jira.codehaus.org/browse/MCHANGES-272?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=297064#comment-297064
]
Christian Schulte commented on MCHANGES-272:
--------------------------------------------
I would like to be able to enable the release profile when building snapshots
(e.g. for testing the release build or for deploying snapshots publicly). Just
like 'mvn deploy' automatically chooses a repository to upload to based on the
kind of artifact acted upon, I would like to avoid having to invoke maven
differently based on the kind of artifact acted upon when enabling the release
profile. The current behavior of the 'changes-check' goal makes this
impossible, since it will fail the build when building a snapshot for which no
matching release version is found in the 'changes.xml' file or for which no
release date is found which makes no sense for snapshots, IMHO. Therefore, the
goal should automatically skip itself, when building a snapshot.
> Please add an option to the 'changes-check' goal to allow skipping release
> date checks of snapshot versions.
> ------------------------------------------------------------------------------------------------------------
>
> Key: MCHANGES-272
> URL: https://jira.codehaus.org/browse/MCHANGES-272
> Project: Maven 2.x Changes Plugin
> Issue Type: New Feature
> Affects Versions: 2.6
> Reporter: Christian Schulte
> Assignee: Benson Margulies
> Priority: Trivial
> Attachments: MCHANGES-272.patch
>
>
> The 'changes-check' goal treats snapshot versions the same way as release
> versions by removing the '-SNAPSHOT' suffix prior to checking the release
> date. Please add an option to the 'changes-check' goal to allow skipping
> snapshot versions.
--
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
