You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Brett Porter (JIRA)" <ji...@codehaus.org> on 2006/03/29 06:07:47 UTC
[jira] Moved: (MCHANGES-18) Report generation fails if there's no
url for the issue management system declared in the pom
[ http://jira.codehaus.org/browse/MCHANGES-18?page=all ]
Brett Porter moved MOJO-71 to MCHANGES-18:
------------------------------------------
Version: (was: 2.0)
Component: (was: changes)
Workflow: jira (was: Maven New)
Key: MCHANGES-18 (was: MOJO-71)
Project: Maven 2.x Changes Plugin (was: Mojo)
> Report generation fails if there's no url for the issue management system declared in the pom
> ---------------------------------------------------------------------------------------------
>
> Key: MCHANGES-18
> URL: http://jira.codehaus.org/browse/MCHANGES-18
> Project: Maven 2.x Changes Plugin
> Type: Bug
> Environment: Win2k, Java 1.4.2_04, Maven 2.0 beta 3, Changes Plugin 2.0 beta 1
> Reporter: Fabrice BELLINGARD
> Assignee: Johnny R. Ruiz III
>
>
> If no issue management system is declared in the pom (or if its url is empty), the report generation fails (cf. stack trace at the end).
> -> This should be possible to generate the report even if no issue management system is declared.
> What's more, even if there's an issue management system specified, the link for JIRA issues is not correct when the changes report is generated (the link to the issue is missing the "url" part, whereas this configuration option is declared to be optional in the doco).
> java.lang.StringIndexOutOfBoundsException: String index out of range: -1
> at java.lang.String.substring(String.java:1444)
> at org.apache.maven.changes.ChangesReportGenerator.parseIssueLink(ChangesReportGenerator.java:211)
> at org.apache.maven.changes.ChangesReportGenerator.constructActions(ChangesReportGenerator.java:114)
> at org.apache.maven.changes.ChangesReportGenerator.constructReleases(ChangesReportGenerator.java:198)
> at org.apache.maven.changes.ChangesReportGenerator.doGenerateReport(ChangesReportGenerator.java:79)
> at org.apache.maven.changes.ChangesMojo.executeReport(ChangesMojo.java:110)
> at org.apache.maven.reporting.AbstractMavenReport.generate(AbstractMavenReport.java:117)
> at org.apache.maven.doxia.DoxiaMojo.generateReportsPages(DoxiaMojo.java:807)
> at org.apache.maven.doxia.DoxiaMojo.execute(DoxiaMojo.java:321)
> at org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:417)
> at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:554)
> at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeStandaloneGoal(DefaultLifecycleExecutor.java:517)
> at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:498)
> at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:307)
> at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:149)
> at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:217)
> at org.apache.maven.cli.MavenCli.main(MavenCli.java:247)
> 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:324)
> 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)
--
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