[ http://jira.codehaus.org/browse/MCHANGELOG-1?page=comments#action_61201 ]
Edwin Punzalan commented on MCHANGELOG-1:
-----------------------------------------
Paul,
if your cvs server is giving a different format, you can set the changelog
configuration and put "yyyy/MM/dd HH:mm:ss" to dateFormat so that it can be
parsed that way. Below is an example:
.....
<reporting>
<plugins>
<plugin>
<groupId>org.codehaus.mojo</groupId>
<artifactId>changelog-maven-plugin</artifactId>
<configuration>
<type>date</type>
<dates>
<date>2006-01-01</date>
</dates>
<dateFormat>yyyy/MM/dd HH:mm:ss</dateFormat>
</configuration>
</plugin>
</plugins>
</reporting>
.....
To the others, especially the reporter, can you verify if this error still
occurs even after changelog has been migrated to use maven-scm? Thanks.
> Changelog report produces (wrongly) empty output
> ------------------------------------------------
>
> Key: MCHANGELOG-1
> URL: http://jira.codehaus.org/browse/MCHANGELOG-1
> Project: Maven 2.x Changelog Plugin
> Type: Bug
> Reporter: Matthew Beermann
> Priority: Critical
> Fix For: 2.0
>
>
> I can confirm that the bug reported in MPCHANGELOG-31 and MPCHANGELOG-38 is
> still alive and well in Maven 2:
> m2 -X changelog:changelog
> <snip>
> [INFO] [changelog:changelog]
> [INFO] Generating changed sets xml to:
> C:\checkouts\system-core\target\changelog.xml
> [DEBUG] Executing CVS command: log -d "2005-09-11<2005-10-12"
> Server is not supporting gzip-file-contents request
> [INFO] ChangeSet between 2005-09-11 and 2005-10-12: 0 entries
> Note that entering the same cvs log command by hand produces perfectly
> normal-looking output, but Maven doesn't like it for whatever reason.
--
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
