You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Jake Fear (JIRA)" <ji...@codehaus.org> on 2008/12/12 21:09:19 UTC
[jira] Commented: (MCHANGELOG-81) Unparseable date exception if the
date format is other than yyyy-MM-dd for the date range
[ http://jira.codehaus.org/browse/MCHANGELOG-81?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=157876#action_157876 ]
Jake Fear commented on MCHANGELOG-81:
-------------------------------------
I'm getting the same message, but my stack trace points to a different location for the date parsing.
[INFO] Generating changed sets xml to: /m2/p4src/soe/Platform/AppEng/main/projects/website/uram/target/changelog.xml
[ERROR] ParseException Caught
java.text.ParseException: Unparseable date: "2008/12/10 12:44:00"
at java.text.DateFormat.parse(DateFormat.java:335)
at org.apache.maven.scm.util.AbstractConsumer.parseDate(AbstractConsumer.java:106)
at org.apache.maven.scm.util.AbstractConsumer.parseDate(AbstractConsumer.java:68)
at org.apache.maven.scm.provider.perforce.command.changelog.PerforceChangeLogConsumer.processGetRevision(PerforceChangeLogConsumer.java:217)
at org.apache.maven.scm.provider.perforce.command.changelog.PerforceChangeLogConsumer.consumeLine(PerforceChangeLogConsumer.java:147)
at org.apache.maven.scm.provider.perforce.command.changelog.PerforceChangeLogCommand.executeChangeLogCommand(PerforceChangeLogCommand.java:77)
at org.apache.maven.scm.command.changelog.AbstractChangeLogCommand.executeCommand(AbstractChangeLogCommand.java:101)
at org.apache.maven.scm.command.AbstractCommand.execute(AbstractCommand.java:58)
at org.apache.maven.scm.provider.perforce.PerforceScmProvider.changelog(PerforceScmProvider.java:159)
at org.apache.maven.scm.provider.AbstractScmProvider.changeLog(AbstractScmProvider.java:250)
at org.apache.maven.plugin.changelog.ChangeLogReport.generateChangeSetsFromSCM(ChangeLogReport.java:464)
at org.apache.maven.plugin.changelog.ChangeLogReport.getChangedSets(ChangeLogReport.java:393)
at org.apache.maven.plugin.changelog.ChangeLogReport.executeReport(ChangeLogReport.java:340)
at org.apache.maven.reporting.AbstractMavenReport.generate(AbstractMavenReport.java:98)
at org.apache.maven.plugins.site.ReportDocumentRenderer.renderDocument(ReportDocumentRenderer.java:139)
at org.apache.maven.doxia.siterenderer.DefaultSiteRenderer.renderModule(DefaultSiteRenderer.java:269)
at org.apache.maven.doxia.siterenderer.DefaultSiteRenderer.render(DefaultSiteRenderer.java:101)
at org.apache.maven.plugins.site.SiteMojo.renderLocale(SiteMojo.java:129)
at org.apache.maven.plugins.site.SiteMojo.execute(SiteMojo.java:96)
at org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:451)
at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:558)
at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle(DefaultLifecycleExecutor.java:499)
at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:478)
at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:330)
at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:291)
at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:142)
at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:336)
at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:129)
at org.apache.maven.cli.MavenCli.main(MavenCli.java:287)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:585)
at org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315)
at org.codehaus.classworlds.Launcher.launch(Launcher.java:255)
at org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430)
at org.codehaus.classworlds.Launcher.main(Launcher.java:375)
> Unparseable date exception if the date format is other than yyyy-MM-dd for the date range
> -----------------------------------------------------------------------------------------
>
> Key: MCHANGELOG-81
> URL: http://jira.codehaus.org/browse/MCHANGELOG-81
> Project: Maven 2.x Changelog Plugin
> Issue Type: Bug
> Affects Versions: 2.1
> Environment: Perforce SCM
> Reporter: Sudharma Rao
> Priority: Critical
>
> Getting following error if the date format is other than yyyy-MM-dd as in case of Perforce SCM
> Embedded error: An error has occurred during changelog command :
> Unparseable date: "2008/02/08 01:01:01"
> Following is the plugin configuration and I'm using Perforce SCM.
> <plugin>
> <groupId>org.apache.maven.plugins</groupId>
> <artifactId>maven-changelog-plugin</artifactId>
> <configuration>
> <dateFormat>yyyy/MM/dd HH:mm:ss</dateFormat>
> <type>date</type>
> <dates>
> <date implementation="java.lang.String">2008/02/08 01:01:01</date>
> <date implementation="java.lang.String">2008/02/01 01:01:01</date>
> </dates>
> </configuration>
> </plugin>
> Cause:
> The date format is hardcoded to "yyyy-MM-dd" at line 572 in org/apache/maven/plugin/changelog/ChangeLogReport.java
> Solution:
> The SCM plugin uses ' <userDateFormat>yyyy/MM/dd HH:mm:ss</userDateFormat>' for the start and end date. The Changelog plugin doesn't use this. Please make it use either 'userDateFormat' or 'dateFormat' for parsing date.
--
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