Re: Waiting for virtual machine to exit...

From: Ulrich Köster (ulric..bjectstyle.org)
Date: Sat Aug 14 2004 - 08:05:54 EDT

  • Next message: Ulrich Köster: "Re: Framework with EOModel and custom classes"

    Hi Dominique,

    is the "Refresh Workspace automatically" option enabled?

    Ulrich

    Am 10.08.2004 um 15:04 schrieb Schoenenberger Dominique:

    > I don't have the "Waiting for virtual machine to exit..." but with the
    > 1.1.0.77 beta 2, I have "[v.1.1-dev May 25 2004] Error saving plist]."
    > error alert panel (I don't have it with the beta 1).
    >
    > When I save a file, the alert appears and I have to click on one or
    > two ok button of such alert. When I compile, they are 10 of such
    > poping up...
    >
    > What plist this message is talking about ?
    >
    > Dominique
    >
    >> -----Original Message-----
    >> From: Ulrich Köster [mailto:ulric..bjectstyle.org]
    >> Sent: Monday, August 09, 2004 8:58 PM
    >> To: woproject-de..bjectstyle.org
    >> Subject: Re: Waiting for virtual machine to exit...
    >>
    >>
    >> Hi Dominique,
    >>
    >> I've seen it on Windows and Mac, with and without subproject,
    >> with version
    >> control and without version control.
    >>
    >> I'm still looking for the bit to reproduce it. Without it,
    >> it's tough to fix
    >> it.
    >>
    >> A how to reproduce the problem would be helpful.
    >>
    >>
    >> ----- Original Message -----
    >> From: "Schoenenberger Dominique" <dominique.schoenenberge..agra.com>
    >> To: "Ulrich Köster" <ulric..bjectstyle.org>;
    >> <woproject-de..bjectstyle.org>
    >> Sent: Monday, August 09, 2004 2:16 PM
    >> Subject: RE: Waiting for virtual machine to exit...
    >>
    >>
    >>
    >> I install the WOLips 1.1.0.77 beta 2.
    >>
    >> First, I tried to not change my .project and my .classpath
    >> (point 2 and 3 in
    >> my last email):
    >>
    >> The "Waiting for virtual machine to exit..." message remains for some
    >> projects. I suspect it's related to project having sub-projects.
    >>
    >> I changed the .project (point 2 in my last mail).
    >>
    >> I have many messages and error messages when I compile my
    >> project (Clean +
    >> build):
    >> In which log?
    >>
    >> 1) "Could not find the main class. Program will exit"
    >> 2) "[v.1.1-dev May 25 2004] Error saving plist]." (new to beta 2)
    >>
    >> May25 is that from your application?
    >>
    >> When I save a file, I have the message 2). Is this message
    >> related to the
    >> fact I'm using Clearcase and some of the file are read-only
    >> (I'm on Windows)
    >> ?
    >>
    >> I can now launch my application.
    >>
    >> How to install automatically when you change something in the
    >> sources ?
    >> The build is invoked automatically. No need to install before
    >> it goes to
    >> deployment.
    >>
    >> Ulrich
    >>
    >>> -----Original Message-----
    >>> From: Ulrich Köster [mailto:ulric..bjectstyle.org]
    >>> Sent: Saturday, August 07, 2004 9:59 AM
    >>> To: WOLips <woproject-de..bjectstyle.org>
    >>> Subject: Re: Waiting for virtual machine to exit...
    >>>
    >>>
    >>> Hi Dominique,
    >>>
    >>> Am 06.08.2004 um 22:19 schrieb Schoenenberger Dominique:
    >>>
    >>>> I also had the problem but it's solved now.
    >>>> I found first it works with new projects created from
    >>> scratch. Then I
    >>>> try to make my old projects working:
    >>>>
    >>>> I don't know exactly how but hereafter some action I performed:
    >>>>
    >>>> 1) I change the way of compiling. I use now "external tool" in the
    >>>> tool bar (this seems not necessary for new projects...). I had to
    >>>> change the ant home for the old projects.
    >>>>
    >>>> 2) I had a message "Could not find the main class. Program will
    >>>> exit". To solve this I changed my old project ".project" file:
    >>>>
    >>>> replace
    >>>> <name>org.eclipse.jdt.core.javabuilder</name>
    >>>> with
    >>>>
    >>> <name>org.objectstyle.wolips.incrementalbuilder</name>
    >>>>
    >>>> replace (for framework)
    >>>>
    >>> <nature>org.objectstyle.wolips.antframeworknature</nature>
    >>>> with
    >>>>
    >>> <nature>org.objectstyle.wolips.incrementalframeworknature</nature>
    >>>>
    >>>> or for application
    >>>> replace
    >>>>
    >>> <nature>org.objectstyle.wolips.antapplicationnature</nature>
    >>>> with
    >>>>
    >>> <nature>org.objectstyle.wolips.incrementalapplicationnature</nature>
    >>>
    >>> For sure, switching the builder hides the problem. You could
    >>> use the ui
    >>> for that task. Open the context menu for the project and choose
    >>> properties. The WOLips build page has everything you need for that.
    >>>>
    >>>> 3) I changed the .classpath. I had explicit path to the jar
    >>> files in
    >>>> my old .classpath and I change it like this:
    >>>>
    >>>> replace
    >>>> <classpathentry kind="var"
    >>>>
    >>> path="NEXT_ROOT/Library/Frameworks/JavaEOAccess.framework/Resources/
    >>>> Java/javaeoaccess.jar"/>
    >>>> <classpathentry kind="var"
    >>>>
    >>>
    >> path="NEXT_ROOT/Library/Frameworks/JavaEOControl.framework/Resources/
    >>>> Java/javaeocontrol.jar"/>
    >>>> <classpathentry kind="var"
    >>>>
    >>> path="NEXT_ROOT/Library/Frameworks/JavaFoundation.framework/Re
    >>> sources/
    >>>> Java/javafoundation.jar"/>
    >>>>
    >>>> with
    >>>> <classpathentry kind="con"
    >>>>
    >>>
    >> path="org.objectstyle.wolips.WO_CLASSPATH/JavaEOAccess/JavaEOControl/
    >>>> JavaFoundation"/>
    >>>
    >>> Ever tried the classpath container?
    >>>
    >>>>
    >>>> 4) I removed some
    >>>> workspace\.metadata\.plugins\org.eclipse.debug.core\.launches:
    >>>>
    >>>> For example, I have 2 launch configurations for the same
    >>> project: With
    >>>> one (the old one) I have the "Waiting for virtual machine
    >>> to exit..."
    >>>> message and with the other one (new created, shorter) it's ok.
    >>>>
    >>>>
    >>>> Now all is compiling but my Wonder project doesn't start correctly
    >>>> because it failed to initialize...
    >>>
    >>> Any output?
    >>>
    >>> Ulrich
    >>>
    >>>>
    >>>> Dominique
    >>>>
    >>>>> -----Original Message-----
    >>>>> From: Christian Mittendorf
    >> [mailto:christian.mittendor..reenet.de]
    >>>>> Sent: Thursday, July 29, 2004 4:11 PM
    >>>>> To: WOLips
    >>>>> Subject: Re: Waiting for virtual machine to exit...
    >>>>>
    >>>>>
    >>>>> Hello,
    >>>>>
    >>>>> this problem does still appear on my machine using version
    >>>>> "eclipse_3_0_0 1.1.0.75".
    >>>>>
    >>>>> Christian
    >>>>>
    >>>>> On 27.07.2004, at 21:01, ulrich köster wrote:
    >>>>>
    >>>>>> Hi,
    >>>>>>
    >>>>>> the problem is that the virtual machine used by the ant
    >>> run does not
    >>>>>> complete sometimes. Turning the build off (with the
    >> toggle button)
    >>>>>> does not
    >>>>>> solve the problem.
    >>>>>> Eclipse continues to build your classes but does not build
    >>>>> the woa or
    >>>>>> framework.
    >>>>>>
    >>>>>> It may work for a while. At least when you change your
    >>>>> eomodel you're
    >>>>>> in
    >>>>>> trouble.
    >>>>>>
    >>>>>> Does this problem occur with the latest version in the cvs?
    >>>>>>
    >>>>>> Ulrich
    >>>>>>
    >>>>>> ----- Original Message -----
    >>>>>> From: "Shelli D. Orton" <shelli.orto..mode.com>
    >>>>>> To: "Geoff Hopson" <ghopso..ac.com>
    >>>>>> Cc: <woproject-de..bjectstyle.org>
    >>>>>> Sent: Tuesday, July 27, 2004 8:36 PM
    >>>>>> Subject: RE: Waiting for virtual machine to exit...
    >>>>>>
    >>>>>>
    >>>>>>> I turned the toggle off and I can do a build without
    >> it hanging.
    >>>>>>>
    >>>>>>> Thanks!!
    >>>>>>>
    >>>>>>> Shelli
    >>>>>>>
    >>>>>>>> -----Original Message-----
    >>>>>>>> From: Geoff Hopson [mailto:ghopso..ac.com]
    >>>>>>>> Sent: Tuesday, July 27, 2004 11:51 AM
    >>>>>>>> To: Shelli D. Orton
    >>>>>>>> Cc: woproject-de..bjectstyle.org
    >>>>>>>> Subject: Re: Waiting for virtual machine to exit...
    >>>>>>>>
    >>>>>>>>
    >>>>>>>> The button is on the toolbar in the WOLIps perspective,
    >>>>> as opposed to
    >>>>>>>> on the menus.
    >>>>>>>>
    >>>>>>>> I also had this error, and following the same email you
    >>>>> found, I was
    >>>>>>>> able to get a build done.
    >>>>>>>>
    >>>>>>>> I subsequent changed all my build files to use the incremental
    >>>>>>>> builder
    >>>>>>>> as opposed to the ant builder (poke around, you'll find
    >>> it - build
    >>>>>>>> properties or something), and that fixed a few things
    >>>>> when I saved a
    >>>>>>>> file and didn't see it in the build (eg changed a html
    >>>>> file, and the
    >>>>>>>> change not pushed through).
    >>>>>>>>
    >>>>>>>> I have since put the 'toggle WOBuild' button back on, and
    >>>>> have not
    >>>>>>>> had
    >>>>>>>> any issues.
    >>>>>>>>
    >>>>>>>> So maybe the problem is using the ant builder with
    >>> toggle wobuild?
    >>>>>>>> Dunno, just speculating.
    >>>>>>>>
    >>>>>>>> HTH,
    >>>>>>>> Geoff
    >>>>>>>>
    >>>>>>>> On 27 Jul 2004, at 17:00, Shelli D. Orton wrote:
    >>>>>>>>
    >>>>>>>>> I have recently upgraded to Eclipse 3.0.0 and am using WOLips
    >>>>>> 1.1.0.71.
    >>>>>>>>> When I try to compile an WO app project, the build seems
    >>>>> to hang and
    >>>>>>>>> the
    >>>>>>>>> message "Waiting for virtual machine to exit..." is
    >>> displayed. I
    >>>>>>>>> found a
    >>>>>>>>> post on this mailing list where someone was having the
    >>>>> same problem
    >>>>>>>>> and the
    >>>>>>>>> posted workaround was:
    >>>>>>>>>
    >>>>>>>>> ----
    >>>>>>>>>
    >>>>>>>>> This issue is present in the final version of Eclipse 3.
    >>>>> what I did
    >>>>>>>>> to
    >>>>>>>>> work around it was:
    >>>>>>>>>
    >>>>>>>>>
    >>>>>>>>> 1) Make sure the "Toggle WOBuild" button is NOT clicked.
    >>>>>>>>> 2) I go to Run -> External Tools -> Run As -> Ant
    >>> Build until it
    >>>>>>>>> gives
    >>>>>>>>> me the same message "Waiting for virtual machine to
    >>>>> exit... " and I
    >>>>>>>>> click Cancel
    >>>>>>>>> 3) Click on Project -> Clean, select "Clean all projects" and
    >>>>>>>>> "Start a
    >>>>>>>>> build immediately" and click OK
    >>>>>>>>> 4) I click on the Run button and it runs perfectly
    >>>>>>>>>
    >>>>>>>>>
    >>>>>>>>> I am guessing this is a WOLips bug? At least the
    >>>>> workaround lets me
    >>>>>>>>> test
    >>>>>>>>> my app. :)
    >>>>>>>>>
    >>>>>>>>> ----
    >>>>>>>>>
    >>>>>>>>> I've looked in Windows -> Preferences and Project ->
    >>>>> Preferences and
    >>>>>>>>> could
    >>>>>>>>> not find a "Toggle WOBuild" button. Where does this
    >>>>> button exist?
    >>>>>> Has
    >>>>>>>>> anyone else run into this problem and found a solution?
    >>>>>>>>>
    >>>>>>>>> Thanks for any help.
    >>>>>>>>>
    >>>>>>>>> Shelli
    >>>>>>>>>
    >>>>>>>>
    >>>>>>>
    >>>>>>
    >>>>>>
    >>>>>
    >>>>>
    >>>
    >>>
    >>
    >>



    This archive was generated by hypermail 2.0.0 : Sat Aug 14 2004 - 08:02:53 EDT