Bug 328550 - NPE when refreshing external folders
Summary: NPE when refreshing external folders
Status: VERIFIED DUPLICATE of bug 321358
Alias: None
Product: JDT
Classification: Eclipse Project
Component: Core (show other bugs)
Version: 3.6.1   Edit
Hardware: PC Windows 7
: P3 minor (vote)
Target Milestone: 3.7 M2   Edit
Assignee: Jay Arthanareeswaran CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-10-24 12:53 EDT by Jon Steinich CLA
Modified: 2010-12-07 07:20 EST (History)
4 users (show)

See Also:

Attachments
workspace log file (92.98 KB, text/plain)
2010-10-24 18:08 EDT, Jon Steinich CLA 		no flags Details
View All 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 Jon Steinich CLA 2010-10-24 12:53:53 EDT 
Build Identifier: M20100909-0800

I have a workspace of 10+ projects all using and svn and one of them is an Android client project.

The following message appears when refreshing or building:

An internal error occurred during: "Refreshing external folders".
java.lang.NullPointerException

I have a different workspace that only has a couple of simple projects in and I don't get the error there.
After closing the Android client project, the error stopped occurring; however, it no longer occurs after re-opening either.

Reproducible: Sometimes
Comment 1 Remy Suen CLA 2010-10-24 15:14:44 EDT 
(In reply to comment #0)
> An internal error occurred during: "Refreshing external folders".
> java.lang.NullPointerException

Please attach your workspace's log file (workspace/.metadata/.log) to this bug.
Comment 2 Jon Steinich CLA 2010-10-24 18:08:20 EDT 
Created attachment 181603 [details]
workspace log file
Comment 3 Remy Suen CLA 2010-10-24 18:12:44 EDT 
(In reply to comment #0)
> After closing the Android client project, the error stopped occurring; however,
> it no longer occurs after re-opening either.

Since it only occurred with an Android project, it could be some issue with the way the classpaths are defined that is conflicting with JDT.
Comment 4 Ayushman Jain CLA 2010-10-25 02:12:15 EDT 
Jay, this might be related to the android bug http://code.google.com/p/android/issues/detail?id=7850&q=adt&colspec=ID%20Type%20Status%20Owner%20Summary%20Stars#c7 , which manifests in a different form in bug 325829.
Comment 5 Olivier Thomann CLA 2010-10-25 09:13:40 EDT 
Even if this is a bug in Android, we should still be more resilient.
Comment 6 Jon Steinich CLA 2010-11-19 10:25:40 EST 
After some more observation, it seems that this may not be specific to Android projects.

However, it does seem to be related to invalid source locations as Remy pointed out.
I didn't fully test it, but it seemed that having any project with a jar reference that doesn't have a valid source location could cause the issue.
Comment 7 Jay Arthanareeswaran CLA 2010-11-22 03:06:12 EST 
This is not an android specific problem and same as bug 321358, which is fixed both for 3.7 and 3.6.2. An explanation has been added under bug 321358, comment 27.

*** This bug has been marked as a duplicate of bug 321358 ***
Comment 8 Satyam Kandula CLA 2010-12-07 03:53:26 EST 
Verified for 3.7M4 using build I20101205-2000