[JBoss JIRA] (JBTIS-674) Deprecate 'SOA 5.x Compatibility' tooling
by Paul Leacu (JIRA)
[ https://issues.jboss.org/browse/JBTIS-674?page=com.atlassian.jira.plugin.... ]
Paul Leacu updated JBTIS-674:
-----------------------------
Description:
The SOA 5.x Development tooling shall be marked as deprecated starting with 9.0.0.GA. It shall be removed at JBDSIS 10.0.0.GA (Neon). It consists of:
org.guvnor.tools.feature
org.jboss.tools.esb.feature
org.jboss.tools.jbpm3.feature
org.jboss.tools.jbpm.common.feature
org.jboss.tools.jbpm.convert.feature
The runtime detector features will not be deprecated:
org.jboss.tools.runtime.drools.detector.feature
org.jboss.tools.runtime.esb.detector.feature
org.jboss.tools.runtime.jbpm.detector.feature
FYI - [~apodhrad] [~bbrodt] [~maxandersen] [~ganandan-Redhat] [[~shelly.mcgowan]
was:
The SOA 5.x Development tooling shall be marked as deprecated starting with 9.0.0.GA. It shall be removed at JBDSIS 10.0.0.GA (Neon). It consists of:
org.guvnor.tools.feature
org.jboss.tools.esb.feature
org.jboss.tools.jbpm3.feature
org.jboss.tools.jbpm.common.feature
org.jboss.tools.jbpm.convert.feature
The runtime detector features will not be deprecated:
org.jboss.tools.runtime.drools.detector.feature
org.jboss.tools.runtime.esb.detector.feature
org.jboss.tools.runtime.jbpm.detector.feature
FYI - [~apodhrad] [~bbrodt] [~maxandersen] [~ganandan-Redhat]
> Deprecate 'SOA 5.x Compatibility' tooling
> -----------------------------------------
>
> Key: JBTIS-674
> URL: https://issues.jboss.org/browse/JBTIS-674
> Project: JBoss Tools Integration Stack
> Issue Type: Feature Request
> Components: distribution
> Affects Versions: 9.0.0.GA
> Reporter: Paul Leacu
> Assignee: Paul Leacu
> Fix For: 9.0.0.GA
>
>
> The SOA 5.x Development tooling shall be marked as deprecated starting with 9.0.0.GA. It shall be removed at JBDSIS 10.0.0.GA (Neon). It consists of:
> org.guvnor.tools.feature
> org.jboss.tools.esb.feature
> org.jboss.tools.jbpm3.feature
> org.jboss.tools.jbpm.common.feature
> org.jboss.tools.jbpm.convert.feature
> The runtime detector features will not be deprecated:
> org.jboss.tools.runtime.drools.detector.feature
> org.jboss.tools.runtime.esb.detector.feature
> org.jboss.tools.runtime.jbpm.detector.feature
> FYI - [~apodhrad] [~bbrodt] [~maxandersen] [~ganandan-Redhat] [[~shelly.mcgowan]
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 12 months
[JBoss JIRA] (JBDS-3841) Installer Sets Path for Wrong User
by Denis Golovin (JIRA)
[ https://issues.jboss.org/browse/JBDS-3841?page=com.atlassian.jira.plugin.... ]
Denis Golovin edited comment on JBDS-3841 at 4/19/16 3:00 PM:
--------------------------------------------------------------
Is it windows home or pro/enterprise?
was (Author: dgolovin):
Is it windows home or enterprise?
> Installer Sets Path for Wrong User
> ----------------------------------
>
> Key: JBDS-3841
> URL: https://issues.jboss.org/browse/JBDS-3841
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Bug
> Components: installer
> Affects Versions: 9.x
> Environment: Windows 10
> Reporter: Thomas Mäder
> Assignee: Denis Golovin
> Priority: Blocker
> Fix For: 10.0.0.Alpha1
>
>
> When I run the offline installer from my non-privileged account, I am prompted by UAC for an administrator login. When I enter my admin login and proceed, tools like vagrant, etc. will not be available from the command line in my non-privileged account. It turns out, the necessary path entries were added to the user-specific path of the admin user, not the user starting the installer.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 12 months
[JBoss JIRA] (JBDS-3841) Installer Sets Path for Wrong User
by Denis Golovin (JIRA)
[ https://issues.jboss.org/browse/JBDS-3841?page=com.atlassian.jira.plugin.... ]
Denis Golovin commented on JBDS-3841:
-------------------------------------
Is it windows home or enterprise?
> Installer Sets Path for Wrong User
> ----------------------------------
>
> Key: JBDS-3841
> URL: https://issues.jboss.org/browse/JBDS-3841
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Bug
> Components: installer
> Affects Versions: 9.x
> Environment: Windows 10
> Reporter: Thomas Mäder
> Assignee: Denis Golovin
> Priority: Blocker
> Fix For: 10.0.0.Alpha1
>
>
> When I run the offline installer from my non-privileged account, I am prompted by UAC for an administrator login. When I enter my admin login and proceed, tools like vagrant, etc. will not be available from the command line in my non-privileged account. It turns out, the necessary path entries were added to the user-specific path of the admin user, not the user starting the installer.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 12 months
[JBoss JIRA] (JBIDE-22201) Error contacting OpenShift after CDK is started
by Martin Malina (JIRA)
[ https://issues.jboss.org/browse/JBIDE-22201?page=com.atlassian.jira.plugi... ]
Martin Malina commented on JBIDE-22201:
---------------------------------------
[~hardy.ferentschik], yeah, it's more of a workaround than fix. And no, I did not remove it while CDK was running. I stopped CDK first.
> Error contacting OpenShift after CDK is started
> -----------------------------------------------
>
> Key: JBIDE-22201
> URL: https://issues.jboss.org/browse/JBIDE-22201
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: cdk, openshift
> Affects Versions: 4.3.1.Final
> Reporter: Martin Malina
> Assignee: Rob Stryker
> Priority: Blocker
>
> Today Marian and I started seeing this issue: When we start CDK, it will start and everything seems to work, but an error pops up:
> {code}
> Error contacting OpenShift
> org.jboss.tools.openshift.cdk.server.core.internal.adapter.VagrantPoller$OpenShiftNotReadyPollingException: The CDK VM is up and running, but OpenShift is unreachable at url https://10.1.2.2:8443/healthz/ready
> at org.jboss.tools.openshift.cdk.server.core.internal.adapter.VagrantPoller.checkOpenShiftHealth(VagrantPoller.java:209)
> at org.jboss.tools.openshift.cdk.server.core.internal.adapter.VagrantPoller.checkOpenShiftHealth(VagrantPoller.java:186)
> at org.jboss.tools.openshift.cdk.server.core.internal.adapter.VagrantPoller.onePing(VagrantPoller.java:170)
> at org.jboss.tools.openshift.cdk.server.core.internal.adapter.VagrantPoller.onePingSafe(VagrantPoller.java:150)
> at org.jboss.tools.openshift.cdk.server.core.internal.adapter.VagrantPoller.getCurrentStateSynchronous(VagrantPoller.java:129)
> at org.jboss.tools.openshift.cdk.server.core.internal.adapter.controllers.CDKLaunchController.handleProcessTerminated(CDKLaunchController.java:248)
> at org.jboss.tools.openshift.cdk.server.core.internal.adapter.controllers.CDKLaunchController.access$2(CDKLaunchController.java:240)
> at org.jboss.tools.openshift.cdk.server.core.internal.adapter.controllers.CDKLaunchController$2.run(CDKLaunchController.java:233)
> {code}
> When you actually copy&paste that url into a browser, you will get "ok".
> This happens to me on OS X with CDK 2.0 CR3 (the latest build). Marian is on Linux (Fedora 22).
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 12 months
[JBoss JIRA] (JBIDE-22201) Error contacting OpenShift after CDK is started
by Hardy Ferentschik (JIRA)
[ https://issues.jboss.org/browse/JBIDE-22201?page=com.atlassian.jira.plugi... ]
Hardy Ferentschik commented on JBIDE-22201:
-------------------------------------------
{quote}
FYI, I was able to fix this by removing .vagrant in the Vagrantfile directory.
{quote}
Hmm, that does not sounds like a fix. The _.vagrant_ directory contains metadata of the running VM. Among other things it also contains the Docker certs to connect to the Docker daemon. Removing it while the VM is running does not sounds like a good idea to me.
> Error contacting OpenShift after CDK is started
> -----------------------------------------------
>
> Key: JBIDE-22201
> URL: https://issues.jboss.org/browse/JBIDE-22201
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: cdk, openshift
> Affects Versions: 4.3.1.Final
> Reporter: Martin Malina
> Assignee: Rob Stryker
> Priority: Blocker
>
> Today Marian and I started seeing this issue: When we start CDK, it will start and everything seems to work, but an error pops up:
> {code}
> Error contacting OpenShift
> org.jboss.tools.openshift.cdk.server.core.internal.adapter.VagrantPoller$OpenShiftNotReadyPollingException: The CDK VM is up and running, but OpenShift is unreachable at url https://10.1.2.2:8443/healthz/ready
> at org.jboss.tools.openshift.cdk.server.core.internal.adapter.VagrantPoller.checkOpenShiftHealth(VagrantPoller.java:209)
> at org.jboss.tools.openshift.cdk.server.core.internal.adapter.VagrantPoller.checkOpenShiftHealth(VagrantPoller.java:186)
> at org.jboss.tools.openshift.cdk.server.core.internal.adapter.VagrantPoller.onePing(VagrantPoller.java:170)
> at org.jboss.tools.openshift.cdk.server.core.internal.adapter.VagrantPoller.onePingSafe(VagrantPoller.java:150)
> at org.jboss.tools.openshift.cdk.server.core.internal.adapter.VagrantPoller.getCurrentStateSynchronous(VagrantPoller.java:129)
> at org.jboss.tools.openshift.cdk.server.core.internal.adapter.controllers.CDKLaunchController.handleProcessTerminated(CDKLaunchController.java:248)
> at org.jboss.tools.openshift.cdk.server.core.internal.adapter.controllers.CDKLaunchController.access$2(CDKLaunchController.java:240)
> at org.jboss.tools.openshift.cdk.server.core.internal.adapter.controllers.CDKLaunchController$2.run(CDKLaunchController.java:233)
> {code}
> When you actually copy&paste that url into a browser, you will get "ok".
> This happens to me on OS X with CDK 2.0 CR3 (the latest build). Marian is on Linux (Fedora 22).
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 12 months
[JBoss JIRA] (JBIDE-22201) Error contacting OpenShift after CDK is started
by Alexey Kazakov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-22201?page=com.atlassian.jira.plugi... ]
Alexey Kazakov reassigned JBIDE-22201:
--------------------------------------
Assignee: Rob Stryker
[~rob.stryker] can you please take a look.
cc: [~hardy.ferentschik]
> Error contacting OpenShift after CDK is started
> -----------------------------------------------
>
> Key: JBIDE-22201
> URL: https://issues.jboss.org/browse/JBIDE-22201
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: cdk, openshift
> Affects Versions: 4.3.1.Final
> Reporter: Martin Malina
> Assignee: Rob Stryker
> Priority: Blocker
>
> Today Marian and I started seeing this issue: When we start CDK, it will start and everything seems to work, but an error pops up:
> {code}
> Error contacting OpenShift
> org.jboss.tools.openshift.cdk.server.core.internal.adapter.VagrantPoller$OpenShiftNotReadyPollingException: The CDK VM is up and running, but OpenShift is unreachable at url https://10.1.2.2:8443/healthz/ready
> at org.jboss.tools.openshift.cdk.server.core.internal.adapter.VagrantPoller.checkOpenShiftHealth(VagrantPoller.java:209)
> at org.jboss.tools.openshift.cdk.server.core.internal.adapter.VagrantPoller.checkOpenShiftHealth(VagrantPoller.java:186)
> at org.jboss.tools.openshift.cdk.server.core.internal.adapter.VagrantPoller.onePing(VagrantPoller.java:170)
> at org.jboss.tools.openshift.cdk.server.core.internal.adapter.VagrantPoller.onePingSafe(VagrantPoller.java:150)
> at org.jboss.tools.openshift.cdk.server.core.internal.adapter.VagrantPoller.getCurrentStateSynchronous(VagrantPoller.java:129)
> at org.jboss.tools.openshift.cdk.server.core.internal.adapter.controllers.CDKLaunchController.handleProcessTerminated(CDKLaunchController.java:248)
> at org.jboss.tools.openshift.cdk.server.core.internal.adapter.controllers.CDKLaunchController.access$2(CDKLaunchController.java:240)
> at org.jboss.tools.openshift.cdk.server.core.internal.adapter.controllers.CDKLaunchController$2.run(CDKLaunchController.java:233)
> {code}
> When you actually copy&paste that url into a browser, you will get "ok".
> This happens to me on OS X with CDK 2.0 CR3 (the latest build). Marian is on Linux (Fedora 22).
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 12 months
[JBoss JIRA] (JBDS-3842) Migrating to Eclipse Neon
by Alexey Kazakov (JIRA)
Alexey Kazakov created JBDS-3842:
------------------------------------
Summary: Migrating to Eclipse Neon
Key: JBDS-3842
URL: https://issues.jboss.org/browse/JBDS-3842
Project: Developer Studio (JBoss Developer Studio)
Issue Type: Epic
Components: build
Reporter: Alexey Kazakov
Assignee: Alexey Kazakov
This Epic is for tasks related to Devstudio migration to Eclipse Neon.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 12 months