Bug 138419 - IllegalArgumentException when compiling swt
Summary: IllegalArgumentException when compiling swt
Status: RESOLVED WORKSFORME
Alias: None
Product: JDT
Classification: Eclipse Project
Component: Core (show other bugs)
Version: 3.2   Edit
Hardware: PC Windows 2000
: P3 major (vote)
Target Milestone: 3.2 RC2   Edit
Assignee: Frederic Fusier CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2006-04-25 12:19 EDT by Grant Gayed CLA
Modified: 2006-04-25 13:56 EDT (History)
0 users

See Also:

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Grant Gayed CLA 2006-04-25 12:19:42 EDT 
3.2 0425 nightly build

- connect to dev.eclipse.org
- retrieve the org.eclipse.swt project
- in the Resource perspective:
  -> select the project's .classpath_win32 file, right-click -> Copy
  -> select the org.eclipse.swt.project, right-click -> Paste
  -> in the rename dialog set the value to .classpath
- this compiles SWT for win32, and at the end writes the following to .log:

!ENTRY org.eclipse.jdt.core 4 4 2006-04-25 11:54:39.093
!MESSAGE Background Indexer Crash Recovery
!STACK 0
java.lang.IllegalArgumentException
	at org.eclipse.jdt.core.Signature.appendTypeSignature(Signature.java:2359)
	at org.eclipse.jdt.core.Signature.appendTypeSignature(Signature.java:2266)
	at org.eclipse.jdt.core.Signature.toCharArray(Signature.java:2245)
	at org.eclipse.jdt.internal.core.search.indexing.BinaryIndexer.addBinaryAnnotation(BinaryIndexer.java:148)
	at org.eclipse.jdt.internal.core.search.indexing.BinaryIndexer.indexDocument(BinaryIndexer.java:654)
	at org.eclipse.jdt.internal.core.search.JavaSearchParticipant.indexDocument(JavaSearchParticipant.java:74)
	at org.eclipse.jdt.internal.core.search.indexing.IndexManager.indexDocument(IndexManager.java:322)
	at org.eclipse.jdt.internal.core.search.indexing.AddJarFileToIndex.execute(AddJarFileToIndex.java:197)
	at org.eclipse.jdt.internal.core.search.processing.JobManager.run(JobManager.java:372)
	at java.lang.Thread.run(Thread.java:566)
Comment 1 Philipe Mulet CLA 2006-04-25 12:48:26 EDT 
+1 for 3.2RC2
Comment 2 Frederic Fusier CLA 2006-04-25 13:15:13 EDT 
I cannot reproduce this IAE. Note that this can only happen while reading 1.5 binary files...
Do you have a JRE 1.5 as default JRE libraries?
Or perhaps did you start eclipse using a 1.5 VM? If so, which one?
Comment 3 Grant Gayed CLA 2006-04-25 13:49:27 EDT 
Good question <g>.  I usually live in the linux world, so I haven't looked into this lately on my win2000 machine.  Here's what java -version said:

java version "1.5.0-beta"
Java(TM) 2 Runtime Environment, Standard Edition (build 1.5.0-beta-b32c)
Java HotSpot(TM) Client VM (build 1.5.0-beta-b32c, mixed mode)

So my case is probably invalid given that this is a beta vm.  I downloaded the IBM 1.5.0 from IBM's internal site and it does not show this error.
Comment 4 Frederic Fusier CLA 2006-04-25 13:56:06 EDT 
Thanks, so close as WORKSFORME