Re: Can't Run or Debug any more?

From: Anders Peterson (anders_peterso..ptimatika.se)
Date: Thu Nov 15 2007 - 02:50:09 EST

  • Next message: Stéphan Mertz: "Re: Can't Run or Debug any more?"

    I have the same problem as Pierce T. Wetter III, and I do have project
    dependencies for non-wo-projects. Why should that be a problem?

    My setup is:
    Mac OSX 10.4.10 and eclise 3.3.1.1

    WOLips 4370 works fine, but when I switched to 4638 I can no longer run
    or debug.

    /Anders

    Mike Schrag wrote:
    > Is it possible you have project dependencies in your build path that are
    > not WOLips project natures?
    >
    > ms
    >
    > On Nov 14, 2007, at 5:39 PM, Pierce T. Wetter III wrote:
    >
    >>
    >> Recently my WOLips installation has broken, possibly since I did an
    >> update hoping for Leopard fixes.
    >>
    >> Ok, so I'm running Leopard with 5.3. That was working fine.
    >>
    >> Latest nightly build (as of an hour ago) but I'm not sure when the
    >> problem appeared as it was happening to me yesterday too:
    >>
    >> !ENTRY org.eclipse.core.jobs 4 2 2007-11-14 12:59:15.404
    >> !MESSAGE An internal error occurred during: "Launching iLokManager".
    >> !STACK 0
    >> java.lang.NullPointerException
    >> at
    >> org.objectstyle.wolips.launching.classpath.WORuntimeClasspathProvider.getWOJavaArchive(Unknown
    >> Source)
    >> at
    >> org.objectstyle.wolips.launching.classpath.WORuntimeClasspathProvider.resolveClasspath(Unknown
    >> Source)
    >> at
    >> org.eclipse.jdt.internal.launching.RuntimeClasspathProvider.resolveClasspath(RuntimeClasspathProvider.java:60)
    >>
    >> at
    >> org.eclipse.jdt.launching.JavaRuntime.resolveRuntimeClasspath(JavaRuntime.java:1181)
    >>
    >> at
    >> org.eclipse.jdt.launching.AbstractJavaLaunchConfigurationDelegate.getClasspath(AbstractJavaLaunchConfigurationDelegate.java:417)
    >>
    >> at
    >> org.objectstyle.wolips.launching.delegates.WOJavaLocalApplicationLaunchConfigurationDelegate.getClasspath(Unknown
    >> Source)
    >> at
    >> org.eclipse.jdt.launching.JavaLaunchDelegate.launch(JavaLaunchDelegate.java:71)
    >>
    >> at
    >> org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:766)
    >>
    >> at
    >> org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:608)
    >>
    >> at
    >> org.eclipse.debug.internal.ui.DebugUIPlugin.buildAndLaunch(DebugUIPlugin.java:899)
    >>
    >> at
    >> org.eclipse.debug.internal.ui.DebugUIPlugin$7.run(DebugUIPlugin.java:1102)
    >>
    >> at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55)
    >>
    >> Any ideas?
    >>
    >> Pierce
    >
    >
    >

    This archive was generated by hypermail 2.0.0 : Thu Nov 15 2007 - 02:51:27 EST