MyEclipse: IN-Workspace Mode gkgunda - Apr 29, 2012 - 03:23 AM Post subject: IN-Workspace Mode
Hello,
Am using MEB 10.0.02 and Websphere 8. When i tried to deploy my application using enhanced mode, the application is deployed sucessfully. Since hot code deployment is not supported am trying to deploy on the server after updating the connector to use IN-Workspace mode. When i tried to add the EAR to deployment the "Add Deployment" runs for ever, it always says Deploying EAR to Websphere ..... Creating Administrator Proxy and i dont see any other logs.
Thanks
Gopi
Here is my installation summary for MEB
*** Date:
Saturday, April 28, 2012 8:19:28 PM MDT
** System properties:
OS=WindowsVista
OS version=6.1.0
Java version=1.6.0_13
*** MyEclipse details:
MyEclipse Blue Edition
Version: 10.0 Blue
Build id: 10.0-Blue-20111028
Eclipse startup command=-os
win32
-ws
win32
-arch
x86
-showsplash
-launcher
C:\MyEclipse Blue Edition\MyEclipse Blue Edition 10\myeclipse-blue.exe
-name
Myeclipse-blue
--launcher.library
C:\MyEclipse Blue Edition\MyEclipse Blue Edition 10\../Common/plugins/org.eclipse.equinox.launcher.i18n.win32.win32.x86_3.2.0.v201103301700\eclipse_3215.dll
-startup
C:\MyEclipse Blue Edition\MyEclipse Blue Edition 10\../Common/plugins/org.eclipse.equinox.launcher_1.2.0.v20110502.jar
-install
C:\MyEclipse Blue Edition\MyEclipse Blue Edition 10
-configuration
C:\MyEclipse Blue Edition\MyEclipse Blue Edition 10\configuration
-vm
C:\MyEclipse Blue Edition\Common\binary\com.sun.java.jdk.win32.x86_1.6.0.013\jre\bin\client\jvm.dllsupport-swapna - Apr 30, 2012 - 07:49 AM Post subject:
Gopi,
Sorry that you are seeing this issue.
Can you please update to the latest version 10.1 to take advantage of the several fixes we made to the in-workspace mode and check if the issue exists ? Go to MyEclipse Configuration Center > Software > Software Updates Available > MyEclipse Blue 10.1. Select , apply the changes, follow the wizard and restart the IDE when it prompts.
If you are still seeing the issue, please clear the deployment log contents, replicate the issue and paste the deployment log here for us to investigate further.