Bug 39075 - Source attachment path should be absolute
Summary: Source attachment path should be absolute
Status: RESOLVED DUPLICATE of bug 38531
Alias: None
Product: JDT
Classification: Eclipse Project
Component: Core (show other bugs)
Version: 3.0   Edit
Hardware: PC Windows 2000
: P3 blocker (vote)
Target Milestone: 3.0 M2   Edit
Assignee: Philipe Mulet CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2003-06-18 11:41 EDT by Wassim Melhem CLA
Modified: 2003-06-19 17:51 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 Wassim Melhem CLA 2003-06-18 11:41:53 EDT
Build: I-20030618
When I import plug-ins into my workspace, I get a number of the following JDT 
core error messages:

Source Attachment path should be absolute:""
java.lang.IllegalArgumentException
at org.eclipse.jdt.core.JavaCore.newLibraryEntry(JavaCore.java:2362)
at org.eclipse.jdt.core.JavaCore.getResolvedClasspathEntry(JavaCore.java:1804)
at org.eclipse.jdt.internal.core.JavaProject.getResolvedClasspath
(JavaProject.java:1533)
at org.eclipse.jdt.internal.core.JavaProject.getResolvedClasspath
(JavaProject.java:1476)
at org.eclipse.jdt.internal.core.JavaProject.getResolvedClasspath
(JavaProject.java:1452)
at org.eclipse.jdt.core.JavaCore.updateVariableValues(JavaCore.java:3244)
at org.eclipse.jdt.core.JavaCore.setClasspathVariables(JavaCore.java:3053)
at org.eclipse.jdt.core.JavaCore.setClasspathVariable(JavaCore.java:3025)
at 
org.eclipse.jdt.internal.launching.JavaClasspathVariablesInitializer.setJREVaria
ble(JavaClasspathVariablesInitializer.java:102)
at 
org.eclipse.jdt.internal.launching.JavaClasspathVariablesInitializer.initialize
(JavaClasspathVariablesInitializer.java:79)
at org.eclipse.jdt.core.JavaCore$2.run(JavaCore.java:1054)
at org.eclipse.core.internal.runtime.InternalPlatform.run
(InternalPlatform.java:1015)
at org.eclipse.core.runtime.Platform.run(Platform.java:420)
at org.eclipse.jdt.core.JavaCore.getClasspathVariable(JavaCore.java:1049)
at org.eclipse.jdt.core.JavaCore.getResolvedVariablePath(JavaCore.java:1840)
at org.eclipse.jdt.core.JavaCore.getResolvedClasspathEntry(JavaCore.java:1758)
at org.eclipse.jdt.internal.core.JavaProject.getResolvedClasspath
(JavaProject.java:1533)
at org.eclipse.jdt.internal.core.JavaProject.getResolvedClasspath
(JavaProject.java:1476)
at org.eclipse.jdt.internal.core.JavaProject.getResolvedClasspath
(JavaProject.java:1452)
at org.eclipse.jdt.internal.core.DeltaProcessor.initializeRoots
(DeltaProcessor.java:1240)
at org.eclipse.jdt.internal.core.JavaModelOperation.execute
(JavaModelOperation.java:362)
at org.eclipse.jdt.internal.core.JavaModelOperation.run
(JavaModelOperation.java:704)
at org.eclipse.core.internal.resources.Workspace.run(Workspace.java:1595)
at org.eclipse.jdt.core.JavaCore.run(JavaCore.java:2809)
at org.eclipse.jdt.core.JavaCore.setClasspathContainer(JavaCore.java:2934)
at org.eclipse.jdt.internal.launching.JREContainerInitializer.initialize
(JREContainerInitializer.java:51)
at org.eclipse.jdt.core.JavaCore$1.run(JavaCore.java:934)
at org.eclipse.core.internal.runtime.InternalPlatform.run
(InternalPlatform.java:1015)
at org.eclipse.core.runtime.Platform.run(Platform.java:420)
at org.eclipse.jdt.core.JavaCore.getClasspathContainer(JavaCore.java:929)
at org.eclipse.jdt.internal.core.JavaProject.getResolvedClasspath
(JavaProject.java:1544)
at org.eclipse.jdt.internal.core.JavaProject.getResolvedClasspath
(JavaProject.java:1476)
at org.eclipse.jdt.internal.core.JavaProject.getResolvedClasspath
(JavaProject.java:1452)
at org.eclipse.jdt.internal.core.JavaElement.getElementInfo
(JavaElement.java:301)
at org.eclipse.jdt.internal.core.JavaElement.getChildren(JavaElement.java:254)
at org.eclipse.jdt.internal.core.Openable.hasChildren(Openable.java:275)
at org.eclipse.jdt.ui.StandardJavaElementContentProvider.hasChildren
(StandardJavaElementContentProvider.java:241)
at org.eclipse.jface.viewers.AbstractTreeViewer.isExpandable
(AbstractTreeViewer.java:1069)
at org.eclipse.jface.viewers.AbstractTreeViewer.updatePlus
(AbstractTreeViewer.java:1485)
at org.eclipse.jface.viewers.AbstractTreeViewer.createTreeItem
(AbstractTreeViewer.java:327)
at org.eclipse.jface.viewers.AbstractTreeViewer$1.run
(AbstractTreeViewer.java:309)
at org.eclipse.swt.custom.BusyIndicator.showWhile(BusyIndicator.java:69)
at org.eclipse.jface.viewers.AbstractTreeViewer.createChildren
(AbstractTreeViewer.java:295)
at org.eclipse.jface.viewers.AbstractTreeViewer$5.run
(AbstractTreeViewer.java:741)
at org.eclipse.jface.viewers.StructuredViewer.preservingSelection
(StructuredViewer.java:801)
at org.eclipse.jface.viewers.AbstractTreeViewer.inputChanged
(AbstractTreeViewer.java:732)
at org.eclipse.jface.viewers.ContentViewer.setInput(ContentViewer.java:238)
at org.eclipse.jface.viewers.StructuredViewer.setInput
(StructuredViewer.java:991)
at org.eclipse.jdt.internal.ui.packageview.PackageExplorerPart.createPartControl
(PackageExplorerPart.java:303)
at org.eclipse.ui.internal.PartPane$4.run(PartPane.java:141)
at org.eclipse.core.internal.runtime.InternalPlatform.run
(InternalPlatform.java:1015)
at org.eclipse.core.runtime.Platform.run(Platform.java:420)
at org.eclipse.ui.internal.PartPane.createChildControl(PartPane.java:137)
at org.eclipse.ui.internal.ViewPane.createChildControl(ViewPane.java:211)
at org.eclipse.ui.internal.PartPane.createControl(PartPane.java:186)
at org.eclipse.ui.internal.ViewPane.createControl(ViewPane.java:190)
at org.eclipse.ui.internal.PartTabFolder.createPartTab(PartTabFolder.java:252)
at org.eclipse.ui.internal.PartTabFolder.createControl(PartTabFolder.java:224)
at org.eclipse.ui.internal.PartSashContainer.createControl
(PartSashContainer.java:192)
at org.eclipse.ui.internal.PerspectivePresentation.activate
(PerspectivePresentation.java:96)
at org.eclipse.ui.internal.Perspective.onActivate(Perspective.java:718)
at org.eclipse.ui.internal.WorkbenchPage.onActivate(WorkbenchPage.java:1748)
at org.eclipse.ui.internal.WorkbenchWindow$7.run(WorkbenchWindow.java:1601)
at org.eclipse.swt.custom.BusyIndicator.showWhile(BusyIndicator.java:69)
at org.eclipse.ui.internal.WorkbenchWindow.setActivePage
(WorkbenchWindow.java:1588)
at org.eclipse.ui.internal.WorkbenchWindow.restoreState
(WorkbenchWindow.java:1462)
at org.eclipse.ui.internal.Workbench.restoreState(Workbench.java:1244)
at org.eclipse.ui.internal.Workbench.access$9(Workbench.java:1204)
at org.eclipse.ui.internal.Workbench$12.run(Workbench.java:1122)
at org.eclipse.core.internal.runtime.InternalPlatform.run
(InternalPlatform.java:1015)
at org.eclipse.core.runtime.Platform.run(Platform.java:420)
at org.eclipse.ui.internal.Workbench.openPreviousWorkbenchState
(Workbench.java:1074)
at org.eclipse.ui.internal.Workbench.init(Workbench.java:851)
at org.eclipse.ui.internal.Workbench.run(Workbench.java:1354)
at org.eclipse.core.internal.boot.InternalBootLoader.run
(InternalBootLoader.java:858)
at org.eclipse.core.boot.BootLoader.run(BootLoader.java:461)
at java.lang.reflect.Method.invoke(Native Method)
at org.eclipse.core.launcher.Main.basicRun(Main.java:291)
at org.eclipse.core.launcher.Main.run(Main.java:747)
at org.eclipse.core.launcher.Main.main(Main.java:583)
Comment 1 Wassim Melhem CLA 2003-06-19 12:28:45 EDT
Raising severity to blocker as I can't even open my workspace anymore.
Every time I launch Eclipse, and "autobuild kicks in", my log fills up with 
thousands of these entries, all with the message "Source Attachment path should 
be absolute:""", but with varying stack traces.
My log file expands to hundreds of MB, before I have to terminate the workbench 
manually.
Comment 2 Wassim Melhem CLA 2003-06-19 12:36:26 EDT
The only thing that is different about this particular workspace is the fact 
that the JRE I'm compiling with does not have source attached.  I've used this 
JRE for a while now, but only recently has the lack of source been upsetting 
JDT core that much.
Comment 3 Philipe Mulet CLA 2003-06-19 17:48: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)
Comment 4 Philipe Mulet CLA 2003-06-19 17:51:26 EDT

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