Bug 39125 - Exception in log after running ant
Summary: Exception in log after running ant
Status: RESOLVED DUPLICATE of bug 38531
Alias: None
Product: JDT
Classification: Eclipse Project
Component: Core (show other bugs)
Version: 2.1   Edit
Hardware: PC Windows XP
: P3 normal (vote)
Target Milestone: 3.0 M2   Edit
Assignee: JDT-Core-Inbox CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2003-06-19 10:59 EDT by Michael Valenta CLA
Modified: 2003-06-19 17:54 EDT (History)
0 users

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Michael Valenta CLA 2003-06-19 10:59:18 EDT
I got 2 of the following exception in log after running Ant. The outpu of the 
Ant build was a zip file.

java.lang.IllegalArgumentException
at java.lang.Throwable.<init>(Throwable.java)
at org.eclipse.jdt.core.JavaCore.newLibraryEntry(JavaCore.java)
at org.eclipse.jdt.core.JavaCore.getResolvedClasspathEntry(JavaCore.java:1804)
at org.eclipse.jdt.internal.core.JavaProject.getResolvedClasspath
(JavaProject.java)
at org.eclipse.jdt.internal.core.JavaProject.getResolvedClasspath
(JavaProject.java)
at org.eclipse.jdt.internal.core.JavaProject.computeExpandedClasspath
(JavaProject.java)
at org.eclipse.jdt.internal.core.JavaProject.getExpandedClasspath
(JavaProject.java:1079)
at 
org.eclipse.jdt.internal.core.builder.NameEnvironment.computeClasspathLocations
(NameEnvironment.java:81)
at org.eclipse.jdt.internal.core.builder.NameEnvironment.<init>
(NameEnvironment.java:38)
at org.eclipse.jdt.internal.core.builder.JavaBuilder.initializeBuilder
(JavaBuilder.java:431)
at org.eclipse.jdt.internal.core.builder.JavaBuilder.build
(JavaBuilder.java:111)
at org.eclipse.core.internal.events.BuildManager$2.run(BuildManager.java:427)
at org.eclipse.core.internal.runtime.InternalPlatform.run
(InternalPlatform.java)
at org.eclipse.core.runtime.Platform.run(Platform.java)
at org.eclipse.core.internal.events.BuildManager.basicBuild
(BuildManager.java:125)
at org.eclipse.core.internal.events.BuildManager.basicBuild
(BuildManager.java:181)
at org.eclipse.core.internal.events.BuildManager.basicBuild
(BuildManager.java:191)
at org.eclipse.core.internal.events.BuildManager$1.run(BuildManager.java:151)
at org.eclipse.core.internal.runtime.InternalPlatform.run
(InternalPlatform.java)
at org.eclipse.core.runtime.Platform.run(Platform.java)
at org.eclipse.core.internal.events.BuildManager.basicBuild
(BuildManager.java:165)
at org.eclipse.core.internal.events.BuildManager.basicBuildLoop
(BuildManager.java:243)
at org.eclipse.core.internal.events.BuildManager.build(BuildManager.java:212)
at org.eclipse.core.internal.resources.Workspace.endOperation
(Workspace.java:884)
at org.eclipse.core.internal.resources.Resource.refreshLocal
(Resource.java:1160)
at org.eclipse.core.resources.ant.RefreshLocalTask.execute
(RefreshLocalTask.java:77)
at org.apache.tools.ant.Task.perform(Task.java:341)
at org.apache.tools.ant.Target.execute(Target.java:309)
at org.apache.tools.ant.Target.performTasks(Target.java:336)
at org.apache.tools.ant.Project.executeTarget(Project.java:1339)
at org.eclipse.ant.internal.core.ant.InternalAntRunner.run
(InternalAntRunner.java:569)
at org.eclipse.ant.internal.core.ant.InternalAntRunner.run
(InternalAntRunner.java:365)
at java.lang.reflect.AccessibleObject.invokeV(AccessibleObject.java:199)
at java.lang.reflect.Method.invoke(Method.java:252)
at org.eclipse.ant.core.AntRunner.run(AntRunner.java:341)
at org.eclipse.ant.ui.internal.launchConfigurations.AntLaunchDelegate$1.run
(AntLaunchDelegate.java:186)
at java.lang.Thread.run(Thread.java:801)
Comment 1 Michael Valenta CLA 2003-06-19 11:13:23 EDT
This is a duplicate of bug 38572. I'm leaving it separate because it would be 
nice if there were not 100+ exceptions logged for the same error. I had to 
wait about 10 minutes for Eclipse to come up because I have debugging enabled. 
Perhaps you could write one log entry and silently swallow the others since 
they don't really add much.
Comment 2 Philipe Mulet CLA 2003-06-19 17:54:24 EDT
We have addressed this issue in our latest patch posted at:
http://dev.eclipse.org/viewcvs/index.cgi/%7Echeckout%7E/jdt-core-
home/r3.0/main.html#updates

(the logging is issued when the offending API is incorrectly used, but we made 
it more tolerant since use case is still valid)


*** This bug has been marked as a duplicate of 38531 ***