[
https://issues.apache.org/jira/browse/SCM-291?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17960925#comment-17960925
]
ASF GitHub Bot commented on SCM-291:
------------------------------------
jira-importer commented on issue #509:
URL: https://github.com/apache/maven-scm/issues/509#issuecomment-2964599973
**[Emmanuel
Venisse](https://issues.apache.org/jira/secure/ViewProfile.jspa?name=evenisse)**
commented
yyyy-MM-dd HH:mm:ssZ format is used by default now as it work in cvs 1.11 too
If a cvs can't use this format, he'll can define an other one in
cvs-settings.xml
> Errors during date parsing with cvs version 1.12.12.
> ----------------------------------------------------
>
> Key: SCM-291
> URL: https://issues.apache.org/jira/browse/SCM-291
> Project: Maven SCM (Moved to GitHub Issues)
> Issue Type: Bug
> Components: maven-scm-provider-cvs
> Affects Versions: 1.0-beta-4
> Environment: Linux Suse 10
> CVS 1.12.12
> Reporter: johann angeli
> Assignee: Emmanuel Venisse
> Priority: Major
> Fix For: 1.0-rc1
>
>
> The changelog plugin used with cvs client 1.12.12, failed with the following
> error :
> >> [ERROR] cvs [log aborted]: Can't parse date/time:
> >> `2007-02-20T12:15:51+0100'
> The problem comes from the cvs client version 1.12.12 that doesn't seem any
> more to support the specified time format (yyyy-MM-dd'T'HH:mm:ssZ).
> Tests made with changelog and cvs client version 1.11.6 are ok. Older
> versions of changelog, prior to issue SCM-177, and cvs client version 1.12.12
> work also correctly.
> The problem is solved by replacing the format "yyyy-MM-dd'T'HH:mm:ssZ" by
> this one "yyyy-MM-dd HH:mm:ssZ" in class AbstractCvsChangeLogCommand.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
