Eclipse Community Forums: Buckminster » An internal error occurred during: "Refreshing external folders"

Help

Home

Home » Eclipse Projects » Buckminster » An internal error occurred during: "Refreshing external folders"

Show: Today's Messages :: Show Polls :: Message Navigator

An internal error occurred during: "Refreshing external folders" [message #558153]

Fri, 10 September 2010 07:15

Thorsten Meinl
Messages: 83
Registered: July 2009

Member

Hi all,

After upgrading to the latest headless Buckminster I'm getting errors
such as

ERROR: An internal error occurred during: "Refreshing external folders".
java.lang.NullPointerException
at
org.eclipse.jdt.internal.core.ExternalFoldersManager$Refresh Job.run(ExternalFoldersManager.java:387)
at org.eclipse.core.internal.jobs.Worker.run(Worker.java:54)

when building in Hudson. This looks identical to
https://bugs.eclipse.org/bugs/show_bug.cgi?id=321358
However, this bug is about Eclipse 3.7 so I'm wondering why I'm getting
the error with 3.6? Also Buckminster the build inside the Eclipse IDE
(3.6.0) still works fine.

Cheers,

Thorsten

Report message to a moderator

Re: An internal error occurred during: "Refreshing external folders" [message #558157 is a reply to message #558153]

Fri, 10 September 2010 07:22

Thorsten Meinl
Messages: 83
Registered: July 2009

Member

More info on this: I have an older headless Buckminster that is working
and the important difference seems to be

org.eclipse.jdt.core_3.6.0.v_A58.jar vs.
org.eclipse.jdt.core_3.6.1.v_A66_R36x.jar

Report message to a moderator

Re: An internal error occurred during: "Refreshing external folders" [message #558315 is a reply to message #558153]

Sat, 11 September 2010 02:31

Peter Kullmann
Messages: 190
Registered: July 2009

Senior Member

I have the same errors from time to time but I think the builds are
still ok. I didn't investigate further because I have no external
folders (I think). What are external folders anyway?

Best regards,
Peter

Thorsten Meinl schrieb:
> Hi all,
>
> After upgrading to the latest headless Buckminster I'm getting errors
> such as
>
> ERROR: An internal error occurred during: "Refreshing external folders".
> java.lang.NullPointerException
> at
> org.eclipse.jdt.internal.core.ExternalFoldersManager$Refresh Job.run(ExternalFoldersManager.java:387)
> at org.eclipse.core.internal.jobs.Worker.run(Worker.java:54)
>
> when building in Hudson. This looks identical to
> https://bugs.eclipse.org/bugs/show_bug.cgi?id=321358
> However, this bug is about Eclipse 3.7 so I'm wondering why I'm getting
> the error with 3.6? Also Buckminster the build inside the Eclipse IDE
> (3.6.0) still works fine.
>
> Cheers,
>
> Thorsten

Report message to a moderator

Re: An internal error occurred during: "Refreshing external folders" [message #558334 is a reply to message #558315]

Sat, 11 September 2010 05:52

Thorsten Meinl
Messages: 83
Registered: July 2009

Member

Am 11.09.2010 08:31, schrieb Peter Kullmann:
> I have the same errors from time to time but I think the builds are
> still ok. I didn't investigate further because I have no external
> folders (I think). What are external folders anyway?
External folders are used if you let Hudson checkout the sources and let
Buckminster import these projects via an appropriate CQUERY.
Unfortunately, in my case these error messages also prevent the
workspace from being built, so it's a more serious problem.
I worked around the problem by first installing org.eclipse.jdt.core in
version 3.6.0 into headless Buckminster and after that
org.eclipse.buckminster.pde.feature. This works because the latter
depends on a version range of jdt. The faulty 3.6.1-version is installed
because the Buckminster-US ships it.

Thorsten

Report message to a moderator

Re: An internal error occurred during: "Refreshing external folders" [message #633748 is a reply to message #558334]

Tue, 19 October 2010 04:58

Silvano
Messages: 1
Registered: October 2010

Junior Member

I had the same issue too after the most recent Eclipse update. I started refreshing my projects one by one until I found the one which was raising the NPE, Closing and reopening the proj resolved the problem in my case.

Silvano

Report message to a moderator

Previous Topic:	URL parse doesn't find link?
Next Topic:	NPE in P2Materializer

Goto Forum:

-=] Back to Top [=-

[ Syndicate this forum (XML) ] [

]

Current Time: Sat May 25 20:01:02 EDT 2013