facebook

JUnit in debug mode gets vm error

  1. MyEclipse IDE
  2.  > 
  3. WebSphere Development
Viewing 6 posts - 1 through 6 (of 6 total)
  • Author
    Posts
  • #293425 Reply

    Don Fair
    Member

    Hi,
    I have tried thiis with both 6.6 and now 7.0
    When try to run a Junit test in debug mode I get the vm error. Other applications run fine in debug mode. Only the Junit fails. Can you help?

    Thanks

    #293441 Reply

    Loyal Water
    Member

    Hi,
    Can you please paste the error that you ran into.

    Also, can you paste the installation details available under MyEclipse > Installation Summary > Installation Details.

    #293442 Reply

    Don Fair
    Member

    I posted the configuration on the first post. It was removed. Here it is again
    Hope it stays this time.

    #293469 Reply

    Loyal Water
    Member

    dhf,
    I had removed the details that you has posted because they were of no help and were messing up the UI. I wanted the details under MyEclipse > Installation Summary > Installation Details like I had pointed out earlier.

    I got the pm you sent me. Can you just try to run junit tests or launch a java application from just a normal eclipse install (without MyEclipse). Does that work?

    #293470 Reply

    Don Fair
    Member

    I have run JUnit tests in MyEclipse as long as it is a standard application. However, if it is an Enterprise application then they fail. The Enterprise application is setup by MyEclipse.

    *** Date:
    Tuesday, January 13, 2009 4:12:42 PM EST

    ** System properties:
    OS=WindowsXP
    OS version=5.1
    Java version=1.5.0_11

    *** MyEclipse details:
    MyEclipse Enterprise Workbench
    Version: 6.6.0
    Build id: 6.6.0-20081015

    *** Eclipse details:
    MyEclipse Enterprise Workbench

    Version: 6.6.0
    Build id: 6.6.0-20081015

    Eclipse Platform

    Version: 3.3.3.r33x_r20080129-_19UEl7Ezk_gXF1kouft
    Build id: M20080221-1800

    Eclipse RCP

    Version: 3.3.3.r33x_r20080129-8y8eE9UEUWI6qujeED0xT7bc
    Build id: M20080221-1800

    Eclipse Java Development Tools

    Version: 3.3.2.r33x_r20080129-7o7jE7_EDhYDiyVEnjb1pFd7ZGD7
    Build id: M20080221-1800

    Eclipse Plug-in Development Environment

    Version: 3.3.3.r33x_r20080129-7N7M5DQVIA_6oJsEFkEL
    Build id: M20080221-1800

    Eclipse Project SDK

    Version: 3.3.3.r33x_r20080129-7M7J7LB-u3aphGW6o3_VmiVfGXWO
    Build id: M20080221-1800

    Eclipse Graphical Editing Framework

    Version: 3.3.2.v20080129
    Build id: 20080221-1602

    Eclipse startup command=-os
    win32
    -ws
    win32
    -arch
    x86
    -showsplash
    -launcher
    C:\Program Files\MyEclipse 6.6\eclipse\eclipse.exe
    -name
    Eclipse
    –launcher.library
    C:\Program Files\MyEclipse 6.6\eclipse\plugins\org.eclipse.equinox.launcher.win32.win32.x86_1.0.3.R33x_v20080118\eclipse_1023.dll
    -startup
    C:\Program Files\MyEclipse 6.6\eclipse\plugins\org.eclipse.equinox.launcher_1.0.1.R33x_v20080118.jar
    -exitdata
    e3c_4c
    -clean
    -vm
    C:\Program Files\MyEclipse 6.6\jre\bin\javaw.exe

    #293607 Reply

    Loyal Water
    Member

    Don,
    I just checked with the dev team. Enterprise Applications are meta-projects, they are not meant to have code under them. That code belongs in the modules that belong to the Enterprise Project

Viewing 6 posts - 1 through 6 (of 6 total)
Reply To: JUnit in debug mode gets vm error

You must be logged in to post in the forum log in