Results 1 to 3 of 3

Thread: NPE in STS 2.3.0 on Mac OS 10.6.2

  1. #1
    Join Date
    Sep 2004
    Posts
    127

    Default NPE in STS 2.3.0 on Mac OS 10.6.2

    Yesterday, I started getting NPEs from inside STS, rendering STS practically useless.

    I'm using STS 2.3.0 on Mac OS 10.6.2, and all my projects are Maven-based.

    Installing a fresh copy of STS in a fresh user account resulted in the same problems. I also updated M2Eclipse from their update site at http://m2eclipse.sonatype.org/update-dev/, as recommended in another thread, but to no avail.

    I wouldn't mind reverting to STS 2.2.1 for now, but there seems to be now download available anymore.

    Below, I included the stack trace for the first of many errors from the STS error log view.

    If anyone could help me with this, it would be greatly appreciated. I'd be glad to provide more information if required.

    Thanks,
    Dan


    Code:
    eclipse.buildId=2.3.0.200912171331-RELEASE
    java.version=1.6.0_17
    java.vendor=Apple Inc.
    BootLoader constants: OS=macosx, ARCH=x86, WS=carbon, NL=en_US
    Framework arguments:  -product com.springsource.sts.ide -keyring /Users/test/.eclipse_keyring -showlocation
    Command-line arguments:  -os macosx -ws carbon -arch x86 -product com.springsource.sts.ide -keyring /Users/test/.eclipse_keyring -showlocation
    
    Error
    Wed Jan 27 23:49:02 CET 2010
    Problems occurred when invoking code from plug-in: "org.eclipse.equinox.preferences".
    
    java.lang.NullPointerException
    at org.eclipse.jdt.internal.launching.StandardVMType.generateLibraryInfo(StandardVMType.java:481)
    at org.eclipse.jdt.internal.launching.StandardVMType.getLibraryInfo(StandardVMType.java:122)
    at org.eclipse.jdt.internal.launching.StandardVMType.getDefaultLibraryLocations(StandardVMType.java:290)
    at org.eclipse.jdt.internal.launching.macosx.MacOSXVMInstallType.detectInstallLocation(MacOSXVMInstallType.java:112)
    at org.eclipse.jdt.launching.JavaRuntime.detectEclipseRuntime(JavaRuntime.java:1712)
    at org.eclipse.jdt.launching.JavaRuntime.initializeVMs(JavaRuntime.java:2596)
    at org.eclipse.jdt.launching.JavaRuntime.getVMInstallTypes(JavaRuntime.java:510)
    at org.eclipse.jdt.internal.launching.JREPreferenceModifyListener.preApply(JREPreferenceModifyListener.java:126)
    at org.eclipse.core.internal.preferences.PreferencesService$4.run(PreferencesService.java:445)
    at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42)
    at org.eclipse.core.internal.preferences.PreferencesService.firePreApplyEvent(PreferencesService.java:448)
    at org.eclipse.core.internal.preferences.PreferencesService.applyPreferences(PreferencesService.java:120)
    at org.eclipse.core.internal.resources.ProjectPreferences.read(ProjectPreferences.java:233)
    at org.eclipse.core.internal.resources.ProjectPreferences.updatePreferences(ProjectPreferences.java:299)
    at org.eclipse.core.internal.resources.File.updateMetadataFiles(File.java:405)
    at org.eclipse.core.internal.localstore.RefreshLocalVisitor.visit(RefreshLocalVisitor.java:294)
    at org.eclipse.core.internal.localstore.UnifiedTree.accept(UnifiedTree.java:106)
    at org.eclipse.core.internal.localstore.FileSystemResourceManager.refreshResource(FileSystemResourceManager.java:784)
    at org.eclipse.core.internal.localstore.FileSystemResourceManager.refresh(FileSystemResourceManager.java:768)
    at org.eclipse.core.internal.resources.Resource.refreshLocal(Resource.java:1528)
    at org.maven.ide.eclipse.project.configurator.MavenProjectConfigurator.configure(MavenProjectConfigurator.java:78)
    at org.maven.ide.eclipse.internal.project.DefaultLifecycleMapping.configure(DefaultLifecycleMapping.java:60)
    at org.maven.ide.eclipse.internal.project.ProjectConfigurationManager.updateProjectConfiguration(ProjectConfigurationManager.java:347)
    at org.maven.ide.eclipse.internal.project.ProjectConfigurationManager.configureNewMavenProject(ProjectConfigurationManager.java:269)
    at org.maven.ide.eclipse.internal.project.ProjectConfigurationManager.importProjects(ProjectConfigurationManager.java:165)
    at org.maven.ide.eclipse.wizards.MavenImportWizard$1.runInWorkspace(MavenImportWizard.java:96)
    at org.eclipse.core.internal.resources.InternalWorkspaceJob.run(InternalWorkspaceJob.java:38)
    at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55)

  2. #2
    Join Date
    Aug 2004
    Location
    Duesseldorf, Germany
    Posts
    1,210

    Default

    Hi Dan,

    can you please check your org.eclipse.jdt.launching_3.5.0.v20090527.jar to see if it contains a lib/launchingsupport.jar. If it doesn't or the name is different can you please re-download STS from the website and install again.

    This issue was/is caused by a broken installer.

    HTH

    Christian
    Christian Dupuis
    SpringSource, a division of VMware
    Lead, SpringSource Tools Team
    http://www.springsource.com
    http://twitter.com/cdupuis

  3. #3
    Join Date
    Sep 2004
    Posts
    127

    Thumbs up Solved!

    Thanks a million Christian,

    My org.eclipse.jdt.launching_3.5.0.v20090527.jar did indeed not contain lib/launchingsupport.jar, only lib/launchingsupport.jar.pack.7z.

    I re-installed STS using a fresh installer download and it all works as expected.

    Now back to work..

    Regards,
    Dan

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •