Maven 2 & 3

String index out of range: 43807

Details

  • Type: Bug Bug
  • Status: Closed Closed
  • Priority: Major Major
  • Resolution: Fixed
  • Affects Version/s: 2.2.0
  • Fix Version/s: 2.2.0
  • Component/s: None
  • Labels:
    None
  • 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"
  • Complexity:
    Intermediate
  • Number of attachments :
    0

Description

the issue occurs with the versions:display-plugin-updates. It throws :

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

I'll try to isolate the problem to see if it's due to the pom or to the maven version.

Activity

Ascending order - Click to sort in descending order
Hide
Permalink
Arnaud Heritier added a comment -

reproduced with alpha-2, alpha-3 and current trunk (beta-1)

Show
Arnaud Heritier added a comment - reproduced with alpha-2, alpha-3 and current trunk (beta-1)
Hide
Permalink
Arnaud Heritier added a comment -

The issue is only with 2.0.0-RC2. It doesn't exist with 2.0.9 and 2.1.0.

Show
Arnaud Heritier added a comment - The issue is only with 2.0.0-RC2. It doesn't exist with 2.0.9 and 2.1.0.
Hide
Permalink
Brett Porter added a comment -

could this be a pom transformation issue? the versions plugin is doing some pretty specific stuff and may be the better place to fix it even if it is incompatible - depends on whether John's recent changes have helped already

Show
Brett Porter added a comment - could this be a pom transformation issue? the versions plugin is doing some pretty specific stuff and may be the better place to fix it even if it is incompatible - depends on whether John's recent changes have helped already
Hide
Permalink
Arnaud Heritier added a comment -

I opened the issue in the versions plugin at the beginning and Stephen patched the trunk of it to apply a workaround.
I moved it into MNG, to warn us about the change/regression

Show
Arnaud Heritier added a comment - I opened the issue in the versions plugin at the beginning and Stephen patched the trunk of it to apply a workaround. I moved it into MNG, to warn us about the change/regression
Hide
Permalink
John Casey added a comment -

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.

Show
John Casey added a comment - 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.

People

Vote (0)
Watch (0)

Dates

  • Created:
    Updated:
    Resolved:
Atlassian JIRA (v4.4.3#663-r165197) | Report a problem
Powered by a free Atlassian JIRA open source license for Codehaus. Try JIRA - bug tracking software for your team.