[JBoss JIRA] (JBTIS-1008) Provide OpenShift 3 support feature in Integration Stack Target Platform
by Aurélien Pupier (JIRA)
[ https://issues.jboss.org/browse/JBTIS-1008?page=com.atlassian.jira.plugin... ]
Aurélien Pupier edited comment on JBTIS-1008 at 12/22/16 9:42 AM:
------------------------------------------------------------------
I found a workaround few minutes ago. When using "Installation" mode for the Target platform, it works.
I provided a PR with this new TP and with updated how-to: https://github.com/fusesource/fuseide/pull/794
i think that we will go with this limitation of not using a "software site" neither a "directory"
was (Author: aurelien.pupier):
I found a workaround few minutes ago. When using "Installation" mode for the Target platform, it works.
I provided a PR with this new TP and with updated how-to: https://github.com/fusesource/fuseide/pull/794
> Provide OpenShift 3 support feature in Integration Stack Target Platform
> ------------------------------------------------------------------------
>
> Key: JBTIS-1008
> URL: https://issues.jboss.org/browse/JBTIS-1008
> Project: JBoss Tools Integration Stack
> Issue Type: Feature Request
> Components: target-platform
> Affects Versions: 4.4.1.CR2-TP
> Reporter: Aurélien Pupier
> Assignee: Paul Leacu
> Attachments: screenshot-1.png
>
>
> My goal is to be able to leverage OpenShift 3 and CDK integration.
> I think that the required feature is org.jboss.tools.openshift.feature
> [~adietish]Can you confirm that it is the right feature?
> *Reason:* Leverage OpenShift 3 and CDK integration.
> *Project page/sources:*
> *Version:* 3.3.1
> *License and owner:* EPL
> *Original p2 repo:*
> *JBoss mirror:*
> *Include Sources:* Yes
> *Affected JBoss Tools components:* .devstudiois
> *Include in JBDS:* Yes (DevtsudioIS)
> *Type of dependency:* distribution
> *List of bundles added/removed:*
> {code}
> {code}
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
7 years, 5 months
[JBoss JIRA] (JBTIS-1008) Provide OpenShift 3 support feature in Integration Stack Target Platform
by Aurélien Pupier (JIRA)
[ https://issues.jboss.org/browse/JBTIS-1008?page=com.atlassian.jira.plugin... ]
Aurélien Pupier commented on JBTIS-1008:
----------------------------------------
I found a workaround few minutes ago. When using "Installation" mode for the Target platform, it works.
I provided a PR with this new TP and with updated how-to: https://github.com/fusesource/fuseide/pull/794
> Provide OpenShift 3 support feature in Integration Stack Target Platform
> ------------------------------------------------------------------------
>
> Key: JBTIS-1008
> URL: https://issues.jboss.org/browse/JBTIS-1008
> Project: JBoss Tools Integration Stack
> Issue Type: Feature Request
> Components: target-platform
> Affects Versions: 4.4.1.CR2-TP
> Reporter: Aurélien Pupier
> Assignee: Paul Leacu
> Attachments: screenshot-1.png
>
>
> My goal is to be able to leverage OpenShift 3 and CDK integration.
> I think that the required feature is org.jboss.tools.openshift.feature
> [~adietish]Can you confirm that it is the right feature?
> *Reason:* Leverage OpenShift 3 and CDK integration.
> *Project page/sources:*
> *Version:* 3.3.1
> *License and owner:* EPL
> *Original p2 repo:*
> *JBoss mirror:*
> *Include Sources:* Yes
> *Affected JBoss Tools components:* .devstudiois
> *Include in JBDS:* Yes (DevtsudioIS)
> *Type of dependency:* distribution
> *List of bundles added/removed:*
> {code}
> {code}
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
7 years, 5 months
[JBoss JIRA] (JBTIS-1008) Provide OpenShift 3 support feature in Integration Stack Target Platform
by Paul Leacu (JIRA)
[ https://issues.jboss.org/browse/JBTIS-1008?page=com.atlassian.jira.plugin... ]
Paul Leacu commented on JBTIS-1008:
-----------------------------------
Since the full fuse TP builds okay it seems to be more related to WIndows? I did see this which seems relevant to your screen capture:
ttps://bugs.eclipse.org/bugs/show_bug.cgi?id=434959
> Provide OpenShift 3 support feature in Integration Stack Target Platform
> ------------------------------------------------------------------------
>
> Key: JBTIS-1008
> URL: https://issues.jboss.org/browse/JBTIS-1008
> Project: JBoss Tools Integration Stack
> Issue Type: Feature Request
> Components: target-platform
> Affects Versions: 4.4.1.CR2-TP
> Reporter: Aurélien Pupier
> Assignee: Paul Leacu
> Attachments: screenshot-1.png
>
>
> My goal is to be able to leverage OpenShift 3 and CDK integration.
> I think that the required feature is org.jboss.tools.openshift.feature
> [~adietish]Can you confirm that it is the right feature?
> *Reason:* Leverage OpenShift 3 and CDK integration.
> *Project page/sources:*
> *Version:* 3.3.1
> *License and owner:* EPL
> *Original p2 repo:*
> *JBoss mirror:*
> *Include Sources:* Yes
> *Affected JBoss Tools components:* .devstudiois
> *Include in JBDS:* Yes (DevtsudioIS)
> *Type of dependency:* distribution
> *List of bundles added/removed:*
> {code}
> {code}
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
7 years, 5 months
[JBoss JIRA] (JBIDE-23660) CDK Server adapter should have an option to configure stop command
by Ricardo Martinelli Oliveira (JIRA)
Ricardo Martinelli Oliveira created JBIDE-23660:
---------------------------------------------------
Summary: CDK Server adapter should have an option to configure stop command
Key: JBIDE-23660
URL: https://issues.jboss.org/browse/JBIDE-23660
Project: Tools (JBoss Tools)
Issue Type: Enhancement
Components: cdk
Affects Versions: 4.4.2.Final
Reporter: Ricardo Martinelli Oliveira
CDK Server adapter lets configure the vagrant startup options. There should have an option to do the same in the stop.
Why?
It seems that CDK Server adapter uses _vagrant destroy_ to stop CDK, but using that option has its drawbacks, like for example:
* If I'm stopping it to save resources, then I'm loosing all my job in it.
* All images already pulled will be lost, so I cannot work offline
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
7 years, 5 months
[JBoss JIRA] (JBTIS-1008) Provide OpenShift 3 support feature in Integration Stack Target Platform
by Aurélien Pupier (JIRA)
[ https://issues.jboss.org/browse/JBTIS-1008?page=com.atlassian.jira.plugin... ]
Aurélien Pupier updated JBTIS-1008:
-----------------------------------
Attachment: screenshot-1.png
> Provide OpenShift 3 support feature in Integration Stack Target Platform
> ------------------------------------------------------------------------
>
> Key: JBTIS-1008
> URL: https://issues.jboss.org/browse/JBTIS-1008
> Project: JBoss Tools Integration Stack
> Issue Type: Feature Request
> Components: target-platform
> Affects Versions: 4.4.1.CR2-TP
> Reporter: Aurélien Pupier
> Assignee: Paul Leacu
> Attachments: screenshot-1.png
>
>
> My goal is to be able to leverage OpenShift 3 and CDK integration.
> I think that the required feature is org.jboss.tools.openshift.feature
> [~adietish]Can you confirm that it is the right feature?
> *Reason:* Leverage OpenShift 3 and CDK integration.
> *Project page/sources:*
> *Version:* 3.3.1
> *License and owner:* EPL
> *Original p2 repo:*
> *JBoss mirror:*
> *Include Sources:* Yes
> *Affected JBoss Tools components:* .devstudiois
> *Include in JBDS:* Yes (DevtsudioIS)
> *Type of dependency:* distribution
> *List of bundles added/removed:*
> {code}
> {code}
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
7 years, 5 months
[JBoss JIRA] (JBTIS-1008) Provide OpenShift 3 support feature in Integration Stack Target Platform
by Aurélien Pupier (JIRA)
[ https://issues.jboss.org/browse/JBTIS-1008?page=com.atlassian.jira.plugin... ]
Aurélien Pupier commented on JBTIS-1008:
----------------------------------------
[~pleacu] There might be an issue with the Target Platform or the way I consume it, the new features requires to have one bundle in exploded mode ( org.eclipse.cdt.core.win32.x86_64 ) otherwise we hit a JVM crash as I reported in [JBDS-4227]
usually I'm using the TP as directory folder but in this case the bundle is jar.
I tried to configure my local TP as an update site but I have several errors:
!screenshot-1.png|thumbnail!
Do you know if it is an issue with the generated TP which should have the jar exploded? or if it is the way that I'm consuming the TP?
> Provide OpenShift 3 support feature in Integration Stack Target Platform
> ------------------------------------------------------------------------
>
> Key: JBTIS-1008
> URL: https://issues.jboss.org/browse/JBTIS-1008
> Project: JBoss Tools Integration Stack
> Issue Type: Feature Request
> Components: target-platform
> Affects Versions: 4.4.1.CR2-TP
> Reporter: Aurélien Pupier
> Assignee: Paul Leacu
> Attachments: screenshot-1.png
>
>
> My goal is to be able to leverage OpenShift 3 and CDK integration.
> I think that the required feature is org.jboss.tools.openshift.feature
> [~adietish]Can you confirm that it is the right feature?
> *Reason:* Leverage OpenShift 3 and CDK integration.
> *Project page/sources:*
> *Version:* 3.3.1
> *License and owner:* EPL
> *Original p2 repo:*
> *JBoss mirror:*
> *Include Sources:* Yes
> *Affected JBoss Tools components:* .devstudiois
> *Include in JBDS:* Yes (DevtsudioIS)
> *Type of dependency:* distribution
> *List of bundles added/removed:*
> {code}
> {code}
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
7 years, 5 months
[JBoss JIRA] (JBDS-4227) JVM crash in development when launching the CDK server
by Aurélien Pupier (JIRA)
[ https://issues.jboss.org/browse/JBDS-4227?page=com.atlassian.jira.plugin.... ]
Aurélien Pupier updated JBDS-4227:
----------------------------------
Attachment: ErrorsWhenUsingsUpdateSite.png
> JVM crash in development when launching the CDK server
> ------------------------------------------------------
>
> Key: JBDS-4227
> URL: https://issues.jboss.org/browse/JBDS-4227
> Project: Red Hat JBoss Developer Studio (devstudio)
> Issue Type: Bug
> Components: cdk, openshift
> Affects Versions: 10.2.0.GA
> Reporter: Aurélien Pupier
> Assignee: Rob Stryker
> Attachments: ErrorsWhenUsingsUpdateSite.png, hs_err_pid13472.log, hs_err_pid6816.log, hs_err_pid7936.log
>
>
> When I'm trying to develop new features and i'm using the CDK server adapter, every time i try to launch the CDK server, the JVm is crashing
> {noformat}
> Java frames: (J=compiled Java code, j=interpreted, Vv=VM code)
> j org.eclipse.cdt.utils.pty.PTY.openMaster(Z)Ljava/lang/String;+0
> j org.eclipse.cdt.utils.pty.PTY.<init>(Z)V+39
> j org.eclipse.cdt.utils.pty.PTY.<init>(Lorg/eclipse/cdt/utils/pty/PTY$Mode;)V+13
> j org.jboss.tools.openshift.cdk.server.core.internal.adapter.controllers.VagrantLaunchUtility.callProcess(Ljava/lang/String;[Ljava/lang/String;Ljava/io/File;Ljava/util/Map;Z)Ljava/lang/Process;+84
> j org.jboss.tools.openshift.cdk.server.core.internal.adapter.controllers.VagrantLaunchUtility.callInteractive(Lorg/eclipse/wst/server/core/IServer;Ljava/lang/String;Ljava/lang/String;Lorg/eclipse/debug/core/ILaunchConfiguration;)Ljava/lang/Process;+31
> j org.jboss.tools.openshift.cdk.server.core.internal.adapter.controllers.VagrantLaunchUtility.callInteractive(Lorg/eclipse/wst/server/core/IServer;Ljava/lang/String;Ljava/lang/String;)Ljava/lang/Process;+18
> j org.jboss.tools.openshift.cdk.server.core.internal.adapter.controllers.CDKLaunchController.launch(Lorg/eclipse/debug/core/ILaunchConfiguration;Ljava/lang/String;Lorg/eclipse/debug/core/ILaunch;Lorg/eclipse/core/runtime/IProgressMonitor;)V+489
> j org.jboss.ide.eclipse.as.wtp.core.server.launch.ControllableServerLaunchConfiguration.launch(Lorg/eclipse/debug/core/ILaunchConfiguration;Ljava/lang/String;Lorg/eclipse/debug/core/ILaunch;Lorg/eclipse/core/runtime/IProgressMonitor;)V+10
> j org.eclipse.debug.internal.core.LaunchConfiguration.launch(Ljava/lang/String;Lorg/eclipse/core/runtime/IProgressMonitor;ZZ)Lorg/eclipse/debug/core/ILaunch;+847
> j org.eclipse.debug.internal.core.LaunchConfiguration.launch(Ljava/lang/String;Lorg/eclipse/core/runtime/IProgressMonitor;Z)Lorg/eclipse/debug/core/ILaunch;+5
> j org.eclipse.debug.internal.core.LaunchConfiguration.launch(Ljava/lang/String;Lorg/eclipse/core/runtime/IProgressMonitor;)Lorg/eclipse/debug/core/ILaunch;+4
> j org.eclipse.wst.server.core.internal.Server.startImpl2(Ljava/lang/String;Lorg/eclipse/core/runtime/IProgressMonitor;)V+91
> j org.eclipse.wst.server.core.internal.Server.startImpl(Ljava/lang/String;Lorg/eclipse/core/runtime/IProgressMonitor;)Lorg/eclipse/core/runtime/IStatus;+87
> j org.eclipse.wst.server.core.internal.Server$StartJob.run(Lorg/eclipse/core/runtime/IProgressMonitor;)Lorg/eclipse/core/runtime/IStatus;+9
> j org.eclipse.core.internal.jobs.Worker.run()V+23
> {noformat}
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
7 years, 5 months
[JBoss JIRA] (JBDS-4227) JVM crash in development when launching the CDK server
by Aurélien Pupier (JIRA)
[ https://issues.jboss.org/browse/JBDS-4227?page=com.atlassian.jira.plugin.... ]
Aurélien Pupier commented on JBDS-4227:
---------------------------------------
yeah found!!
I'm using a local cached TP on which the org.eclipse.cdt.core.win32.x86-64 is in jar and not unpacked in a folder. If I import the project in the workspace, it is working.
Unfortunately, when I try to use the folder as an update site instead of just a folder, i have several errors reported:
!ErrorsWhenUsingsUpdateSite.png|thumbnail!
> JVM crash in development when launching the CDK server
> ------------------------------------------------------
>
> Key: JBDS-4227
> URL: https://issues.jboss.org/browse/JBDS-4227
> Project: Red Hat JBoss Developer Studio (devstudio)
> Issue Type: Bug
> Components: cdk, openshift
> Affects Versions: 10.2.0.GA
> Reporter: Aurélien Pupier
> Assignee: Rob Stryker
> Attachments: ErrorsWhenUsingsUpdateSite.png, hs_err_pid13472.log, hs_err_pid6816.log, hs_err_pid7936.log
>
>
> When I'm trying to develop new features and i'm using the CDK server adapter, every time i try to launch the CDK server, the JVm is crashing
> {noformat}
> Java frames: (J=compiled Java code, j=interpreted, Vv=VM code)
> j org.eclipse.cdt.utils.pty.PTY.openMaster(Z)Ljava/lang/String;+0
> j org.eclipse.cdt.utils.pty.PTY.<init>(Z)V+39
> j org.eclipse.cdt.utils.pty.PTY.<init>(Lorg/eclipse/cdt/utils/pty/PTY$Mode;)V+13
> j org.jboss.tools.openshift.cdk.server.core.internal.adapter.controllers.VagrantLaunchUtility.callProcess(Ljava/lang/String;[Ljava/lang/String;Ljava/io/File;Ljava/util/Map;Z)Ljava/lang/Process;+84
> j org.jboss.tools.openshift.cdk.server.core.internal.adapter.controllers.VagrantLaunchUtility.callInteractive(Lorg/eclipse/wst/server/core/IServer;Ljava/lang/String;Ljava/lang/String;Lorg/eclipse/debug/core/ILaunchConfiguration;)Ljava/lang/Process;+31
> j org.jboss.tools.openshift.cdk.server.core.internal.adapter.controllers.VagrantLaunchUtility.callInteractive(Lorg/eclipse/wst/server/core/IServer;Ljava/lang/String;Ljava/lang/String;)Ljava/lang/Process;+18
> j org.jboss.tools.openshift.cdk.server.core.internal.adapter.controllers.CDKLaunchController.launch(Lorg/eclipse/debug/core/ILaunchConfiguration;Ljava/lang/String;Lorg/eclipse/debug/core/ILaunch;Lorg/eclipse/core/runtime/IProgressMonitor;)V+489
> j org.jboss.ide.eclipse.as.wtp.core.server.launch.ControllableServerLaunchConfiguration.launch(Lorg/eclipse/debug/core/ILaunchConfiguration;Ljava/lang/String;Lorg/eclipse/debug/core/ILaunch;Lorg/eclipse/core/runtime/IProgressMonitor;)V+10
> j org.eclipse.debug.internal.core.LaunchConfiguration.launch(Ljava/lang/String;Lorg/eclipse/core/runtime/IProgressMonitor;ZZ)Lorg/eclipse/debug/core/ILaunch;+847
> j org.eclipse.debug.internal.core.LaunchConfiguration.launch(Ljava/lang/String;Lorg/eclipse/core/runtime/IProgressMonitor;Z)Lorg/eclipse/debug/core/ILaunch;+5
> j org.eclipse.debug.internal.core.LaunchConfiguration.launch(Ljava/lang/String;Lorg/eclipse/core/runtime/IProgressMonitor;)Lorg/eclipse/debug/core/ILaunch;+4
> j org.eclipse.wst.server.core.internal.Server.startImpl2(Ljava/lang/String;Lorg/eclipse/core/runtime/IProgressMonitor;)V+91
> j org.eclipse.wst.server.core.internal.Server.startImpl(Ljava/lang/String;Lorg/eclipse/core/runtime/IProgressMonitor;)Lorg/eclipse/core/runtime/IStatus;+87
> j org.eclipse.wst.server.core.internal.Server$StartJob.run(Lorg/eclipse/core/runtime/IProgressMonitor;)Lorg/eclipse/core/runtime/IStatus;+9
> j org.eclipse.core.internal.jobs.Worker.run()V+23
> {noformat}
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
7 years, 5 months
[JBoss JIRA] (JBDS-4227) JVM crash in development when launching the CDK server
by Aurélien Pupier (JIRA)
[ https://issues.jboss.org/browse/JBDS-4227?page=com.atlassian.jira.plugin.... ]
Aurélien Pupier updated JBDS-4227:
----------------------------------
Attachment: hs_err_pid6816.log
> JVM crash in development when launching the CDK server
> ------------------------------------------------------
>
> Key: JBDS-4227
> URL: https://issues.jboss.org/browse/JBDS-4227
> Project: Red Hat JBoss Developer Studio (devstudio)
> Issue Type: Bug
> Components: cdk, openshift
> Affects Versions: 10.2.0.GA
> Reporter: Aurélien Pupier
> Assignee: Rob Stryker
> Attachments: hs_err_pid13472.log, hs_err_pid6816.log, hs_err_pid7936.log
>
>
> When I'm trying to develop new features and i'm using the CDK server adapter, every time i try to launch the CDK server, the JVm is crashing
> {noformat}
> Java frames: (J=compiled Java code, j=interpreted, Vv=VM code)
> j org.eclipse.cdt.utils.pty.PTY.openMaster(Z)Ljava/lang/String;+0
> j org.eclipse.cdt.utils.pty.PTY.<init>(Z)V+39
> j org.eclipse.cdt.utils.pty.PTY.<init>(Lorg/eclipse/cdt/utils/pty/PTY$Mode;)V+13
> j org.jboss.tools.openshift.cdk.server.core.internal.adapter.controllers.VagrantLaunchUtility.callProcess(Ljava/lang/String;[Ljava/lang/String;Ljava/io/File;Ljava/util/Map;Z)Ljava/lang/Process;+84
> j org.jboss.tools.openshift.cdk.server.core.internal.adapter.controllers.VagrantLaunchUtility.callInteractive(Lorg/eclipse/wst/server/core/IServer;Ljava/lang/String;Ljava/lang/String;Lorg/eclipse/debug/core/ILaunchConfiguration;)Ljava/lang/Process;+31
> j org.jboss.tools.openshift.cdk.server.core.internal.adapter.controllers.VagrantLaunchUtility.callInteractive(Lorg/eclipse/wst/server/core/IServer;Ljava/lang/String;Ljava/lang/String;)Ljava/lang/Process;+18
> j org.jboss.tools.openshift.cdk.server.core.internal.adapter.controllers.CDKLaunchController.launch(Lorg/eclipse/debug/core/ILaunchConfiguration;Ljava/lang/String;Lorg/eclipse/debug/core/ILaunch;Lorg/eclipse/core/runtime/IProgressMonitor;)V+489
> j org.jboss.ide.eclipse.as.wtp.core.server.launch.ControllableServerLaunchConfiguration.launch(Lorg/eclipse/debug/core/ILaunchConfiguration;Ljava/lang/String;Lorg/eclipse/debug/core/ILaunch;Lorg/eclipse/core/runtime/IProgressMonitor;)V+10
> j org.eclipse.debug.internal.core.LaunchConfiguration.launch(Ljava/lang/String;Lorg/eclipse/core/runtime/IProgressMonitor;ZZ)Lorg/eclipse/debug/core/ILaunch;+847
> j org.eclipse.debug.internal.core.LaunchConfiguration.launch(Ljava/lang/String;Lorg/eclipse/core/runtime/IProgressMonitor;Z)Lorg/eclipse/debug/core/ILaunch;+5
> j org.eclipse.debug.internal.core.LaunchConfiguration.launch(Ljava/lang/String;Lorg/eclipse/core/runtime/IProgressMonitor;)Lorg/eclipse/debug/core/ILaunch;+4
> j org.eclipse.wst.server.core.internal.Server.startImpl2(Ljava/lang/String;Lorg/eclipse/core/runtime/IProgressMonitor;)V+91
> j org.eclipse.wst.server.core.internal.Server.startImpl(Ljava/lang/String;Lorg/eclipse/core/runtime/IProgressMonitor;)Lorg/eclipse/core/runtime/IStatus;+87
> j org.eclipse.wst.server.core.internal.Server$StartJob.run(Lorg/eclipse/core/runtime/IProgressMonitor;)Lorg/eclipse/core/runtime/IStatus;+9
> j org.eclipse.core.internal.jobs.Worker.run()V+23
> {noformat}
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
7 years, 5 months
[JBoss JIRA] (JBDS-4227) JVM crash in development when launching the CDK server
by Aurélien Pupier (JIRA)
[ https://issues.jboss.org/browse/JBDS-4227?page=com.atlassian.jira.plugin.... ]
Aurélien Pupier commented on JBDS-4227:
---------------------------------------
I have the exact same error with latest JVM: https://issues.jboss.org/secure/attachment/12414274/hs_err_pid6816.log
> JVM crash in development when launching the CDK server
> ------------------------------------------------------
>
> Key: JBDS-4227
> URL: https://issues.jboss.org/browse/JBDS-4227
> Project: Red Hat JBoss Developer Studio (devstudio)
> Issue Type: Bug
> Components: cdk, openshift
> Affects Versions: 10.2.0.GA
> Reporter: Aurélien Pupier
> Assignee: Rob Stryker
> Attachments: hs_err_pid13472.log, hs_err_pid6816.log, hs_err_pid7936.log
>
>
> When I'm trying to develop new features and i'm using the CDK server adapter, every time i try to launch the CDK server, the JVm is crashing
> {noformat}
> Java frames: (J=compiled Java code, j=interpreted, Vv=VM code)
> j org.eclipse.cdt.utils.pty.PTY.openMaster(Z)Ljava/lang/String;+0
> j org.eclipse.cdt.utils.pty.PTY.<init>(Z)V+39
> j org.eclipse.cdt.utils.pty.PTY.<init>(Lorg/eclipse/cdt/utils/pty/PTY$Mode;)V+13
> j org.jboss.tools.openshift.cdk.server.core.internal.adapter.controllers.VagrantLaunchUtility.callProcess(Ljava/lang/String;[Ljava/lang/String;Ljava/io/File;Ljava/util/Map;Z)Ljava/lang/Process;+84
> j org.jboss.tools.openshift.cdk.server.core.internal.adapter.controllers.VagrantLaunchUtility.callInteractive(Lorg/eclipse/wst/server/core/IServer;Ljava/lang/String;Ljava/lang/String;Lorg/eclipse/debug/core/ILaunchConfiguration;)Ljava/lang/Process;+31
> j org.jboss.tools.openshift.cdk.server.core.internal.adapter.controllers.VagrantLaunchUtility.callInteractive(Lorg/eclipse/wst/server/core/IServer;Ljava/lang/String;Ljava/lang/String;)Ljava/lang/Process;+18
> j org.jboss.tools.openshift.cdk.server.core.internal.adapter.controllers.CDKLaunchController.launch(Lorg/eclipse/debug/core/ILaunchConfiguration;Ljava/lang/String;Lorg/eclipse/debug/core/ILaunch;Lorg/eclipse/core/runtime/IProgressMonitor;)V+489
> j org.jboss.ide.eclipse.as.wtp.core.server.launch.ControllableServerLaunchConfiguration.launch(Lorg/eclipse/debug/core/ILaunchConfiguration;Ljava/lang/String;Lorg/eclipse/debug/core/ILaunch;Lorg/eclipse/core/runtime/IProgressMonitor;)V+10
> j org.eclipse.debug.internal.core.LaunchConfiguration.launch(Ljava/lang/String;Lorg/eclipse/core/runtime/IProgressMonitor;ZZ)Lorg/eclipse/debug/core/ILaunch;+847
> j org.eclipse.debug.internal.core.LaunchConfiguration.launch(Ljava/lang/String;Lorg/eclipse/core/runtime/IProgressMonitor;Z)Lorg/eclipse/debug/core/ILaunch;+5
> j org.eclipse.debug.internal.core.LaunchConfiguration.launch(Ljava/lang/String;Lorg/eclipse/core/runtime/IProgressMonitor;)Lorg/eclipse/debug/core/ILaunch;+4
> j org.eclipse.wst.server.core.internal.Server.startImpl2(Ljava/lang/String;Lorg/eclipse/core/runtime/IProgressMonitor;)V+91
> j org.eclipse.wst.server.core.internal.Server.startImpl(Ljava/lang/String;Lorg/eclipse/core/runtime/IProgressMonitor;)Lorg/eclipse/core/runtime/IStatus;+87
> j org.eclipse.wst.server.core.internal.Server$StartJob.run(Lorg/eclipse/core/runtime/IProgressMonitor;)Lorg/eclipse/core/runtime/IStatus;+9
> j org.eclipse.core.internal.jobs.Worker.run()V+23
> {noformat}
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
7 years, 5 months