You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "John Casey (JIRA)" <ji...@codehaus.org> on 2009/06/09 19:38:42 UTC

[jira] Closed: (MNG-4168) String index out of range: 43807

     [ http://jira.codehaus.org/browse/MNG-4168?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

John Casey closed MNG-4168.
---------------------------

      Assignee: John Casey
    Resolution: Fixed

This appears to have gone away after I withdrew the POM transformations code. Since we don't have a viable solution for POM transformations, it won't be likely to come up again in this release.

> String index out of range: 43807
> --------------------------------
>
>                 Key: MNG-4168
>                 URL: http://jira.codehaus.org/browse/MNG-4168
>             Project: Maven 2
>          Issue Type: Bug
>    Affects Versions: 2.2.0
>         Environment: Apache Maven 2.2.0-RC2 (r771494; 2009-05-05 01:25:54+0200)
> Java version: 1.5.0_17
> Default locale: fr_FR, platform encoding: Cp1252
> OS name: "windows xp" version: "5.1" arch: "x86" Family: "windows"
>            Reporter: Arnaud Heritier
>            Assignee: John Casey
>             Fix For: 2.2.0
>
>
> the issue occurs with the versions:display-plugin-updates. It throws :
> {code}
> [INFO] [versions:display-plugin-updates]
> [INFO] ------------------------------------------------------------------------
> [ERROR] FATAL ERROR
> [INFO] ------------------------------------------------------------------------
> [INFO] String index out of range: 43807
> [INFO] ------------------------------------------------------------------------
> [INFO] Trace
> java.lang.StringIndexOutOfBoundsException: String index out of range: 43807
>         at java.lang.StringBuffer.charAt(StringBuffer.java:163)
>         at org.codehaus.mojo.versions.rewriting.ModifiedPomXMLEventReader.c(ModifiedPomXMLEventReader.java:444)
>         at org.codehaus.mojo.versions.rewriting.ModifiedPomXMLEventReader.hasNext(ModifiedPomXMLEventReader.java:369)
>         at org.codehaus.mojo.versions.DisplayPluginUpdatesMojo.findPluginsWithVersionsSpecified(DisplayPluginUpdatesMojo.java:471)
>         at org.codehaus.mojo.versions.DisplayPluginUpdatesMojo.execute(DisplayPluginUpdatesMojo.java:247)
>         at org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:483)
>         at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:678)
>         at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeStandaloneGoal(DefaultLifecycleExecutor.java:553)
>         at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:523)
>         at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:371)
>         at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:332)
>         at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:181)
>         at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:356)
>         at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:137)
>         at org.apache.maven.cli.MavenCli.main(MavenCli.java:356)
>         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)
> {code}
> I'll try to isolate the problem to see if it's due to the pom or to the maven version.

-- 
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