[
https://jira.codehaus.org/browse/MCHANGES-230?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=345676#comment-345676
]
Philip Maher commented on MCHANGES-230:
---------------------------------------
Yep, no doubt that this could get really complicated to handle builds across
time zones. For my use case I was just hoping for something simple, based on
the current time and timezone of the JRE running the job. If a release
happened on a CI box overnight it may or may not pass based on when the goal
was called in the overall process. I'm personally fine with either outcome. I
usually wait a few minutes on my manual releases if it is near midnight just so
I can get the right date on the changes.xml. For situations where releases are
being done by CI, someone would probably would be better off doing some things
with maven properties to ensure the right date is stamped on the changes.xml at
which point you would not need to enable this validation.
> Add ability for changes-check to validate that the changes.xml release date
> is the day of the release
> -----------------------------------------------------------------------------------------------------
>
> Key: MCHANGES-230
> URL: https://jira.codehaus.org/browse/MCHANGES-230
> Project: Maven Changes Plugin
> Issue Type: New Feature
> Components: changes.xml
> Affects Versions: 2.4
> Reporter: Philip Maher
>
> I like the functionality included in the changes-check in MCHANGES-140. It
> would be nice, in addition to checking the format of the date, if an option
> could be added to have it check to see if the date of the release in the
> changes.xml is the current date when the goal is run. I would like to be
> able to have release:prepare or release:perform fail if the changes.xml did
> not have the right day. This definitely should be an option that is off by
> default.
--
This message was sent by Atlassian JIRA
(v6.1.6#6162)
