You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Sebastien Brunot (JIRA)" <ji...@codehaus.org> on 2007/03/27 17:50:34 UTC
[jira] Created: (MCHANGELOG-61) Timestamp time is always 00:00:00
resulting to badly sorted list
Timestamp time is always 00:00:00 resulting to badly sorted list
----------------------------------------------------------------
Key: MCHANGELOG-61
URL: http://jira.codehaus.org/browse/MCHANGELOG-61
Project: Maven 2.x Changelog Plugin
Issue Type: Bug
Environment: Maven 2.0.5
Reporter: Sebastien Brunot
The change log report is reporting a time of 00:00:00 for each entry in the "Timestamp" column. The date is correct, but while the time is not, the entries are not ordered as expected.
--
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: (MCHANGELOG-61) Timestamp time is always 00:00:00
resulting to badly sorted list
Posted by "Dennis Lundberg (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MCHANGELOG-61?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Dennis Lundberg closed MCHANGELOG-61.
-------------------------------------
Assignee: Dennis Lundberg
Resolution: Fixed
Fix Version/s: 2.1
Fixed in r543594.
> Timestamp time is always 00:00:00 resulting to badly sorted list
> ----------------------------------------------------------------
>
> Key: MCHANGELOG-61
> URL: http://jira.codehaus.org/browse/MCHANGELOG-61
> Project: Maven 2.x Changelog Plugin
> Issue Type: Bug
> Environment: Maven 2.0.5
> Reporter: Sebastien Brunot
> Assignee: Dennis Lundberg
> Fix For: 2.1
>
>
> The change log report is reporting a time of 00:00:00 for each entry in the "Timestamp" column. The date is correct, but while the time is not, the entries are not ordered as expected.
--
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] Commented: (MCHANGELOG-61) Timestamp time is always 00:00:00
resulting to badly sorted list
Posted by "Dennis Lundberg (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MCHANGELOG-61?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_91174 ]
Dennis Lundberg commented on MCHANGELOG-61:
-------------------------------------------
The times are correct for me when I use <type>date</type>. But when I use <type>range</type> they are all 00:00:00.
I'm using subversion 1.4.3 on Windows.
Adding the following section to the configuration seems to solve this problem for <type>range</type>:
<dateFormat>yyyy-MM-dd HH:mm:ss</dateFormat>
The svn command lines that are used work correctly.
Different versions of the ScmProvider.changeLog(...) methods are called depending on the <type> you have set. When using <type>range</type> the dateFormat parameter are passed along, but when you have <type>date</type> dateFormat is not passed along to maven-scm.
Emmanuel, would it be better to just remove the dateFormat from the calls to maven-scm?
> Timestamp time is always 00:00:00 resulting to badly sorted list
> ----------------------------------------------------------------
>
> Key: MCHANGELOG-61
> URL: http://jira.codehaus.org/browse/MCHANGELOG-61
> Project: Maven 2.x Changelog Plugin
> Issue Type: Bug
> Environment: Maven 2.0.5
> Reporter: Sebastien Brunot
>
> The change log report is reporting a time of 00:00:00 for each entry in the "Timestamp" column. The date is correct, but while the time is not, the entries are not ordered as expected.
--
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] Commented: (MCHANGELOG-61) Timestamp time is always 00:00:00
resulting to badly sorted list
Posted by "Emmanuel Venisse (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MCHANGELOG-61?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_91139 ]
Emmanuel Venisse commented on MCHANGELOG-61:
--------------------------------------------
which changelog plugin version?
cvs, svn, other?
> Timestamp time is always 00:00:00 resulting to badly sorted list
> ----------------------------------------------------------------
>
> Key: MCHANGELOG-61
> URL: http://jira.codehaus.org/browse/MCHANGELOG-61
> Project: Maven 2.x Changelog Plugin
> Issue Type: Bug
> Environment: Maven 2.0.5
> Reporter: Sebastien Brunot
>
> The change log report is reporting a time of 00:00:00 for each entry in the "Timestamp" column. The date is correct, but while the time is not, the entries are not ordered as expected.
--
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] Commented: (MCHANGELOG-61) Timestamp time is always 00:00:00
resulting to badly sorted list
Posted by "Sebastien Brunot (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MCHANGELOG-61?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_91140 ]
Sebastien Brunot commented on MCHANGELOG-61:
--------------------------------------------
We currently use SVN 1.3.2 on linux.
For the changelog plugin version, how can we retrieve it ? We're using maven 2.0.5 which is taking care of downloading the appropriate version of the plugin itself...
> Timestamp time is always 00:00:00 resulting to badly sorted list
> ----------------------------------------------------------------
>
> Key: MCHANGELOG-61
> URL: http://jira.codehaus.org/browse/MCHANGELOG-61
> Project: Maven 2.x Changelog Plugin
> Issue Type: Bug
> Environment: Maven 2.0.5
> Reporter: Sebastien Brunot
>
> The change log report is reporting a time of 00:00:00 for each entry in the "Timestamp" column. The date is correct, but while the time is not, the entries are not ordered as expected.
--
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] Commented: (MCHANGELOG-61) Timestamp time is always 00:00:00
resulting to badly sorted list
Posted by "Sebastien Brunot (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MCHANGELOG-61?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_91206 ]
Sebastien Brunot commented on MCHANGELOG-61:
--------------------------------------------
using <dateFormat>yyyy-MM-dd HH:mm:ss</dateFormat> solves my problem. Maybe this should be the default value and should be documented ?
> Timestamp time is always 00:00:00 resulting to badly sorted list
> ----------------------------------------------------------------
>
> Key: MCHANGELOG-61
> URL: http://jira.codehaus.org/browse/MCHANGELOG-61
> Project: Maven 2.x Changelog Plugin
> Issue Type: Bug
> Environment: Maven 2.0.5
> Reporter: Sebastien Brunot
>
> The change log report is reporting a time of 00:00:00 for each entry in the "Timestamp" column. The date is correct, but while the time is not, the entries are not ordered as expected.
--
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