An Internal Error Occurred During Initializing Java Tooling . 2

here for a quick overview

Initializing Java Tooling Eclipse Error

of the site Help Center Detailed answers to any questions you initializing java tooling hangs might have Meta Discuss the workings and policies of this site About Us Learn more about Stack Overflow initializing java tooling hangs at 1 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

Initializing Java Tooling Has Encountered A Problem

million programmers, just like you, helping each other. Join them; it only takes a minute: Sign up An internal error occurred during “Initializing Java Tooling.” in Eclipse on startup up vote 6 down vote favorite 1 I am getting this strange error on startup. What could be wrong in my environment? Here is the error : >!ENTRY org.eclipse.core.jobs 4 2 2010-12-30 17:56:32.545 !MESSAGE An internal error occurred during: "Initializing Java Tooling". !STACK 0 org.eclipse.equinox.internal.provisional.frameworkadmin.FrameworkAdminRuntimeException: Not a file url: ../p2/ at org.eclipse.equinox.internal.frameworkadmin.equinox.EquinoxManipulatorImpl.loadWithoutFwPersistentData(EquinoxManipulatorImpl.java:368) at org.eclipse.equinox.internal.frameworkadmin.equinox.EquinoxManipulatorImpl.load(EquinoxManipulatorImpl.java:331) at org.eclipse.pde.internal.core.target.AbstractBundleContainer.getVMArguments(AbstractBundleContainer.java:722) at org.eclipse.pde.internal.core.target.TargetPlatformService.newDefaultTargetDefinition(TargetPlatformService.java:493) at org.eclipse.pde.internal.core.PluginModelManager.initDefaultTargetPlatformDefinition(PluginModelManager.java:458) at org.eclipse.pde.internal.core.PluginModelManager.initializeTable(PluginModelManager.java:428) at org.eclipse.pde.internal.core.PluginModelManager.getWorkspaceModels(PluginModelManager.java:886) at org.eclipse.pde.core.plugin.PluginRegistry.getWorkspaceModels(PluginRegistry.java:176) at org.eclipse.pde.internal.core.SearchablePluginsManager.computeContainerClasspathEntries(SearchablePluginsManager.java:128) at org.eclipse.pde.internal.core.ExternalJavaSearchClasspathContainer.getClasspathEntries(ExternalJavaSearchClasspathContainer.java:29) at org.eclipse.jdt.internal.core.JavaProject.resolveClasspath(JavaProject.java:2584) at org.eclipse.jdt.internal.core.JavaProject.resolveClasspath(JavaProject.java:2679) at org.eclipse.jdt.internal.core.JavaProject.getResolvedClasspath(JavaProject.java:1866) at org.eclipse.jdt.core.JavaCore.initializeAfterLoad(JavaCore

CommunityMarketplaceEventsPlanet EclipseNewsletterVideosParticipateReport a BugForumsMailing ListsWikiIRCHow to ContributeWorking GroupsAutomotiveInternet of ThingsLocationTechLong-Term SupportPolarSysScienceOpenMDM Toggle navigation Bugzilla – Bug283911 An internal error occurred during: "Initializing Java Tooling" Last modified: 2009-07-27 10:30:51 EDT Home | New | Browse initializing java tooling stuck | Search | [?] | Reports | Requests | Help initializing java tooling has encountered problem nullpointerexception | Log In [x] | Forgot Password Login: [x] | Terms of Use | Copyright

Eclipse Initializing Java Tooling Taking A Long Time

Agent First Last Prev Next This bug is not in your last search results. Bug283911 - An internal error occurred during: "Initializing Java Tooling" http://stackoverflow.com/questions/4568297/an-internal-error-occurred-during-initializing-java-tooling-in-eclipse-on-sta Summary: An internal error occurred during: "Initializing Java Tooling" Status: RESOLVED DUPLICATE of bug 276111 Product: JDT Classification: Eclipse Component: UI Version: 3.5 Hardware: PC Windows XP Importance: P3 normal (vote) TargetMilestone: --- Assigned To: JDT-UI-Inbox QA Contact: URL: Whiteboard: Keywords: Depends on: Blocks: Show dependency tree Reported: https://bugs.eclipse.org/bugs/show_bug.cgi?id=283911 2009-07-18 00:45 EDT by Mohsen Saboorian Modified: 2009-07-27 10:30 EDT (History) CC List: 3 users (show) d3rox markus_keller philippe.marschall 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 Mohsen Saboorian 2009-07-18 00:45:50 EDT I'm getting the following exception during normal Eclipse startup. I'm using dropins folder to install two plugins (although it doesn't seem to be related to this issue). -- Error Details -- Date: Sat Jul 18 10:06:10 IRDT 2009 Message: An internal error occurred during: "Initializing Java Tooling". Severity: Error Product: Eclipse 1.2.0.20090618-0904 (org.eclipse.epp.package.jee.product) Plugin: org.eclipse.core.jobs Session Data: eclipse.buildId=I20090611-1540 java.version=1.6.0_07 java.vendor=Sun Microsystems Inc. BootLoader constants: OS=win32, ARCH=x86, WS=win32, NL=en_US Framework arguments: -product org.eclipse.epp.package.jee.product Command-line arguments: -os win32 -ws win32 -arch x86 -product org.eclipse.epp.package.jee.product Exception Stack Trace: java.lang.NullPointerException at org.eclipse.jdt.internal.junit.buildpath.P2Utils.getBundlesFromFile(P2Utils.java:125) at org.eclipse.jdt.internal.junit.buildpath.P2Utils.readBundles(P2Utils.java:69) at org.eclipse.jdt.internal.junit.buildpath.P2Utils.findBundle(P2Utils.java:166) at org.eclipse.jdt.internal.junit.buildpath.BuildPathSupport$JUnitPluginDescription.getLibraryEntry(BuildPathSupport.java:70) at org.eclipse.jdt.internal.junit.buildpath.BuildPathSupport.getJUnit3LibraryEntry(BuildPathSupport.java:162

Container Development KitCloudOpenShift Enterprise by Red HatMobileRed Hat Mobile Application PlatformAccelerated Development and ManagementRed Hat JBoss Data GridRed Hat JBoss Developer StudioRed Hat JBoss Enterprise Application PlatformRed Hat JBoss Web ServerIntegration and AutomationRed Hat JBoss A-MQRed Hat JBoss BRMSRed Hat JBoss BPM SuiteRed Hat JBoss Data VirtualizationRed Hat https://developer.jboss.org/thread/3432 JBoss FuseCommunityDevelopers BlogInsights & news on Red Hat developer tools, platforms and moreEventsFind http://nan-devblog.blogspot.com/2009/12/eclipsehow-to-resolve-initializing-java.html the latest conferences, meetups, and virtual seminarsOpen Source CommunitiesCommunity Projects that Red Hat participates inContent ContributorsShare your knowledge. Contribute content to Red Hat Developers.HelpResourcesImportant technical resources for you in all shapes and sizes: blogs, books, code, videos and more.ForumsWe've extended our popular JBoss.org forums to cover our entire Red Hat portfolio for you.Stack initializing java Overflow Q&AYou already use Stack Overflow, so we'll help you use it to find your best answers.DownloadsHomeNewsContentPlacesPeopleSearchSearchCancelError: You don't have JavaScript enabled. This tool uses JavaScript and much of it will not work correctly without it enabled. Please turn JavaScript back on and reload this page. Please enter a title. You can not post a blank message. Please type your message and try again. More discussions initializing java tooling in Red Hat JBoss Developer Studio All PlacesProductsRed Hat JBoss Developer Studio Interested in participating? Red Hat Developer Product Discussions are open to the public and can be viewed by everyone, but you need to log in to post and participate. Login now! 4 Replies Latest reply on May 31, 2009 1:34 PM by Max Rydahl Andersen "Initializing Java Tooling" java.lang.NullPointerException w Marc Tille May 28, 2009 4:00 PM Hi,A question that is nagging me for some time:How can I convert a project created with JBoss Tools 3.0.0.GA to be able to use it under JBoss Developer Studio 2.0.0.GA ?Version: 3.4.2Build id: M20090211-17003.0.0.GA-R200903141626-H5to JBoss Developer StudioVersion: 2.0.0.GABuild id: R200903141247-H4The problem is that I am getting the following error message:'Initializing Java Tooling' has encountered a problem.an internal error occurred during:"Initializing Java Tooling" java.lang.NullPointerExceptionwhen I want to open the project with JDBS 2.0.0.GA.Many thanks! 13620Views Tags: none (add) This content has been marked as final. Show 4 replies 1. Re: Nick Boldt May 28, 2009 6:29 PM (in response to Marc Tille) Since JBDS 2.0 is built with Eclipse 3.4.2 and JBT 3.0 pieces, it should be seamlessly intercompatible with JBT 3.0 itself. No pun intended.Check your wor

a problem. An internal error occurred during: "Initializing Java Tooling".It's really annoying, after googling several sites, here is a working solution:Delete the following directory: WORKSPACE_HOME/.metadata/.plugins/org.eclipse.core.resources/.project, and restart Eclipse and problem should be solved. Posted by Nan at 7:28 PM Labels: Eclipse 21 comments: Anonymous said... Awesome! This worked for me. March 19, 2010 at 9:44 PM Anonymous said... With this tip I lost my svn information March 25, 2010 at 4:55 AM Anonymous said... Yeas, me too. I lost all my SVN information.Can't find the .location... July 26, 2010 at 11:21 PM Nan said... Sorry for your lost, when i tried this solution,i didn't met the svn problem. July 29, 2010 at 8:31 PM Hiperion said... I had the error with eclipse Helios, I executed eclipse Galileo and then eclipse Helios, there was something corrupted. January 24, 2011 at 1:14 AM tae jun said... I did it..the WorkingSet configuration might be deleted.I'm using helios and i did reconfigure working set.Eclipse works fine.. January 24, 2011 at 2:14 PM HughesMath said... I am using Helios. I made a new workspace and imported the project. June 10, 2011 at 10:57 PM Jeremy said... Thank you, this fix worked perfectly for me! February 4, 2012 at 12:42 AM Anonymous said... It works for me also. Its awesome !!.For the problem with SVN information, select all projects>Team>Share Projects. The problem is resolved February 23, 2012 at 3:24 PM 小鰻 said... It works, thank you. March 23, 2012 at 10:02 AM Anonymous said... Thank you very much! :) April 10, 2012 at 4:00 AM Pepijn said... Cool, it worked. May 2, 2012 at 5:13 PM Anonymous said... I found this post and solved my problem:run eclipse with -clean optione.g. eclipse.exe -cleanSorted! Thanks to: http://www.eclipsezone.com/eclipse/forums/t100720.html May 30, 2012 at 12:05 AM Anonymous said... run eclipse with -clean optionis the option that worked for me, even using MyEcplise10. It worked on 2012-06-18 and got me rid of the error message