Summary: | Creating a Java project from existing source fails because of "Unhandled event loop exception": ArrayIndexOutOfBoundsException | ||||||
---|---|---|---|---|---|---|---|
Product: | [Eclipse Project] JDT | Reporter: | Martin Burger <m> | ||||
Component: | Core | Assignee: | Jerome Lanneluc <jerome_lanneluc> | ||||
Status: | VERIFIED FIXED | QA Contact: | |||||
Severity: | normal | ||||||
Priority: | P3 | ||||||
Version: | 3.1 | ||||||
Target Milestone: | 3.2 M2 | ||||||
Hardware: | PC | ||||||
OS: | Windows XP | ||||||
Whiteboard: | |||||||
Attachments: |
|
Description
Martin Burger
2005-07-29 11:58:55 EDT
Created attachment 25468 [details] Log file mentioned in comment 1. The complete trace taken from {workspace}\.metadata\.log That's because of the follwing entry in the .classpath file: <classpathentry excluding="" including="plugin.jelly|plugin.properties|project.properties|project.xml|" kind="src" path="."> </classpathentry> If I remove that entry, I can open the project. I think the last '|' is the problem. If I remove only that character, the error does not occur. The .classpath file is generated by "maven eclipse" (http://maven.apache.org/reference/plugins/eclipse/). With Eclipse 3.0.x that was not a problem. I created an issue in project maven-eclipse-plugin: http://jira.codehaus.org/browse/MPECLIPSE-96 But Eclipse 3.0.1 ignored that pipe character, so perhaps Eclipse 3.1 should ignore it, too: .classpath files working with earlier versions of Eclipse should work because of backward compatibility, shouldn't? Changed ClasspathEntry#decodePatterns(...) to ignore empty patterns. Added regression test ClasspathTests#testEmptyInclusionPattern*() Verified in I20050920-0010 for 3.2M2 |