Internal Error Occurred During Refreshing External Folders
CommunityMarketplaceEventsPlanet EclipseNewsletterVideosParticipateReport a BugForumsMailing ListsWikiIRCHow to ContributeWorking GroupsAutomotiveInternet of ThingsLocationTechLong-Term SupportPolarSysScienceOpenMDM Toggle navigation Bugzilla – Bug235777 internal error Refreshing external folders Last modified: 2011-03-29 09:08:37 EDT Home | New | Browse | Search | [?] | Reports | Requests | Help | Log In [x] | Forgot Password Login: [x] | Terms of Use | Copyright Agent First Last Prev Next This bug is not in your last search results. Bug235777 - internal error Refreshing external folders Summary: internal error Refreshing external folders Status: NEW Product: JDT Classification: Eclipse Component: Core Version: 3.4 Hardware: PC Windows XP Importance: P3 normal with 1 vote (vote) TargetMilestone: --- Assigned To: JDT-Core-Inbox QA Contact: URL: Whiteboard: Keywords: needinfo Depends on: Blocks: Show dependency tree Reported: 2008-06-05 05:11 EDT by Juergen Weber Modified: 2011-03-29 09:08 EDT (History) CC List: 3 users (show) mauromol philippe_mulet s.maratea 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 Juergen Weber 2008-06-05 05:11:56 EDT Build ID: I20080530-1730 When I refreshed a project I got the error message: An internal error occurred during: ""Refreshing external folders"". Element not found: /.org.eclipse.jdt.core.external.folders/.link3/src/org/apache/axis2/corba. I found no way to make the error go away from within Eclipse. What finally helped, was to remove an sourcepath="/AXIS2_HOME/modules/corba/src" entry from .classpath. The user should be given a way to repair this from within Eclipse. Comment 1 Jerome Lanneluc 2008-06-05 05:38:19 EDT Was the .metadata modified (by you or any other mean)? Comment 2 Juergen Weber 2008-06-05 13:55:48 EDT (In reply to comment #1) > Was the .metadata modified (by you or any other mean)? > No, I don't think so. I failed to mentio
here for a quick overview of the site Help Center Detailed answers to any questions you might have Meta Discuss the workings and policies of this site About Us Learn more about Stack Overflow the company Business Learn more about hiring developers or posting ads with us Stack Overflow Questions Jobs Documentation Tags Users Badges Ask Question x Dismiss Join the Stack Overflow Community Stack Overflow is a community of 4.7 million programmers, just like you, helping each other. Join them; it only takes a minute: Sign up eclipse An internal error occurred during: “Refreshing external folders”. java.lang.NullPointerException up vote 1 down vote favorite 1 I'm using Eclipse Helios. I get the following error randomly shows in my workspace. An internal error occurred during: "Refreshing https://bugs.eclipse.org/bugs/show_bug.cgi?id=235777 external folders". java.lang.NullPointerException I've tried: - clean the project using menu Project > Clean .. - close and reopen workspace - restart eclipse but none of these can resolved the problem. How do I resolve this problem? eclipse ide share|improve this question edited Sep 18 '13 at 3:41 asked Sep 16 '13 at 7:34 nametal 3011212 1 @JonathonReinhart That's definitely a different problem. In my case, the error message shows in popup window instead of console, that's not compile/logic error. –nametal http://stackoverflow.com/questions/18822585/eclipse-an-internal-error-occurred-during-refreshing-external-folders-java-l Sep 16 '13 at 7:41 Look at the .log file in the workspace .metadata folder to see if there is a message there. –greg-449 Sep 16 '13 at 9:13 @nametal You're right - I got a bit trigger-happy on the close. I've retracted my vote. –Jonathon Reinhart Sep 16 '13 at 17:09 @JonathonReinhart anyway, does anyone face the same problem?? can you give me the solution, please.. –nametal Sep 17 '13 at 8:50 I have seen that before but it never seems to break anything that I have noticed. My theory is it may have to do with versions of Subclipse prior to 1.7 and the new working copy format. I could be wrong though, I have never been able to track that one down even with the error log view. –Snowman Sep 18 '13 at 4:00 add a comment| 1 Answer 1 active oldest votes up vote 0 down vote Even though it was the old post, this answer will helpful for someone. Try to close and open the project, refreshed project get fixed the NullPointerException in my case. Even though error is not getting fixed, close the project -> close eclipse -> open eclipse -> open project may fix your NullPointerException. share|improve this answer edited Feb 3 at 5:46 answered Feb 3 at 5:21 AppHouze 12829 add a comment| Your Answer draft saved draft discarded Sign up or log in Sign
here for a quick overview of the site Help Center Detailed answers to any questions you might have Meta Discuss the workings and policies of this site About Us Learn more about Stack Overflow the company Business http://stackoverflow.com/questions/8309203/how-to-avoid-refreshing-external-folders-in-android-development-in-eclipse Learn more about hiring developers or posting ads with us Stack Overflow Questions Jobs Documentation Tags Users Badges Ask Question x Dismiss Join the Stack Overflow Community Stack Overflow is a community of 4.7 million programmers, just like you, helping each other. Join them; it only takes a minute: Sign up How to avoid “Refreshing external Folders” in Android development in Eclipse up vote 21 down vote favorite 13 I am having this annoying problem internal error which takes 10-20 seconds and sometimes more every time my android project is refreshed or rebuilt. I searched for android forums and also in stackoverflow and but solutions does not make sense. Please give me the solution or link to it. My android project depends on two external java libs and android libs. Tell me if you need more info. Earlier I asked this question and it solved the problem by removing 'source attachment'. But internal error occurred I believe it is not a good solution because I need source to be attached with jar. It helps while debugging, code browsing. If source is not attached then, your breakpoint stops there and you can't go in readable source. Better Solution Needed. Is there a launcher option? which disables when app launched. or build options? java android eclipse share|improve this question edited Jan 7 '15 at 10:32 Marcin Orlowski 42k65287 asked Nov 29 '11 at 10:26 abcdknocked abcd 110115 2 For Better Solution see Governa's answer. It's what you're looking for. Consider checking it as best answer. –Mario Kutlev Mar 18 '13 at 14:43 BTW, there is another option. Instead of waiting for completion of the process, one can switch to Progress tab and press stop button (with red rect). This terminates the refreshing process but next steps, such as launching, will run normally (instantly). –Stan Sep 15 '13 at 17:52 add a comment| 5 Answers 5 active oldest votes up vote 20 down vote accepted The reason for this is that you have attached source with your dependent jars. Just the remove the source from the class path. This how it can be done. Right click on the project -> Select Build Path -> Configure Build Path.. -> Select Libraries Select the Source attachment and Remove button will highlig