[JBoss JIRA] (ERT-623) Evaluate combination of Docker images of LS (from Che?) with LSP4E
by Mickael Istria (JIRA)
Mickael Istria created ERT-623:
----------------------------------
Summary: Evaluate combination of Docker images of LS (from Che?) with LSP4E
Key: ERT-623
URL: https://issues.jboss.org/browse/ERT-623
Project: Eclipse Release Train
Issue Type: Enhancement
Reporter: Mickael Istria
LSP4E offers a way to dynamically associate a Launch configuration representing a language server (communicating over stdio) with a content type to enable LS-based edition assistance in editor.
It would be interesting to try this using a Docker Launch Configuration with LSP4E, more particularly, it'd be nice to test the Docker LS images that are created for Eclipse Che.
cc [~rgrunber] : any obvious concern about it?
cc [~flbe] : are the image for Language Server in Che streaming the LS messages over stdio? Or is it using another channel?
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 11 months
[JBoss JIRA] (JBIDE-25923) Started EAP 7.1 Server adapter is replacing deployment and redeploying over and over
by Ondrej Dockal (JIRA)
[ https://issues.jboss.org/browse/JBIDE-25923?page=com.atlassian.jira.plugi... ]
Ondrej Dockal commented on JBIDE-25923:
---------------------------------------
I am going to record some gif file to show that this is really happening.
> Started EAP 7.1 Server adapter is replacing deployment and redeploying over and over
> ------------------------------------------------------------------------------------
>
> Key: JBIDE-25923
> URL: https://issues.jboss.org/browse/JBIDE-25923
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: server
> Affects Versions: 4.5.3.Final
> Environment: Fedora, JBoss EAP 7.1, WildFly 11, 12
> Reporter: Ondrej Dockal
> Assignee: Rob Stryker
> Priority: Critical
>
> When there is specific maven project imported in Project explorer (jbosstools-openshift), Started EAP 7.1 server adapter is printing output where deployment scanner replaces deployment and redeploy over and over again, see part of log:
> {code}
> 15:35:15,824 INFO [org.jboss.as.server] (DeploymentScanner-threads - 2) WFLYSRV0010: Deployed "standalone.v1.xml" (runtime-name : "standalone.v1.xml")
> 15:35:20,855 INFO [org.jboss.as.server.deployment] (MSC service thread 1-8) WFLYSRV0027: Starting deployment of "standalone.xml" (runtime-name: "standalone.xml")
> 15:35:20,855 INFO [org.jboss.as.server.deployment] (MSC service thread 1-7) WFLYSRV0027: Starting deployment of "standalone.v2.xml" (runtime-name: "standalone.v2.xml")
> 15:35:20,856 INFO [org.jboss.as.server.deployment] (MSC service thread 1-8) WFLYSRV0027: Starting deployment of "standalone.last.xml" (runtime-name: "standalone.last.xml")
> 15:35:20,895 INFO [org.jboss.as.server] (DeploymentScanner-threads - 2) WFLYSRV0010: Deployed "standalone.last.xml" (runtime-name : "standalone.last.xml")
> 15:35:20,895 INFO [org.jboss.as.server] (DeploymentScanner-threads - 2) WFLYSRV0010: Deployed "standalone.v2.xml" (runtime-name : "standalone.v2.xml")
> 15:35:20,895 INFO [org.jboss.as.server] (DeploymentScanner-threads - 2) WFLYSRV0010: Deployed "standalone.xml" (runtime-name : "standalone.xml")
> 15:35:25,951 INFO [org.jboss.as.server.deployment] (MSC service thread 1-7) WFLYSRV0028: Stopped deployment standalone.xml (runtime-name: standalone.xml) in 20ms
> 15:35:25,954 INFO [org.jboss.as.server.deployment] (MSC service thread 1-5) WFLYSRV0027: Starting deployment of "standalone.v3.xml" (runtime-name: "standalone.v3.xml")
> 15:35:25,954 INFO [org.jboss.as.server.deployment] (MSC service thread 1-4) WFLYSRV0027: Starting deployment of "standalone.xml" (runtime-name: "standalone.xml")
> 15:35:25,957 INFO [org.jboss.as.server.deployment] (MSC service thread 1-1) WFLYSRV0028: Stopped deployment standalone.last.xml (runtime-name: standalone.last.xml) in 2ms
> 15:35:25,964 INFO [org.jboss.as.server.deployment] (MSC service thread 1-7) WFLYSRV0027: Starting deployment of "standalone.last.xml" (runtime-name: "standalone.last.xml")
> 15:35:26,037 INFO [org.jboss.as.server] (DeploymentScanner-threads - 2) WFLYSRV0016: Replaced deployment "standalone.last.xml" with deployment "standalone.last.xml"
> 15:35:26,038 INFO [org.jboss.as.server] (DeploymentScanner-threads - 2) WFLYSRV0010: Deployed "standalone.v3.xml" (runtime-name : "standalone.v3.xml")
> {code}
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 11 months
[JBoss JIRA] (JBIDE-25923) Started EAP 7.1 Server adapter is replacing deployment and redeploying over and over
by Ondrej Dockal (JIRA)
Ondrej Dockal created JBIDE-25923:
-------------------------------------
Summary: Started EAP 7.1 Server adapter is replacing deployment and redeploying over and over
Key: JBIDE-25923
URL: https://issues.jboss.org/browse/JBIDE-25923
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: server
Affects Versions: 4.5.3.Final
Environment: Fedora, JBoss EAP 7.1, WildFly 11, 12
Reporter: Ondrej Dockal
Assignee: Rob Stryker
Priority: Critical
When there is specific maven project imported in Project explorer (jbosstools-openshift), Started EAP 7.1 server adapter is printing output where deployment scanner replaces deployment and redeploy over and over again, see part of log:
{code}
15:35:15,824 INFO [org.jboss.as.server] (DeploymentScanner-threads - 2) WFLYSRV0010: Deployed "standalone.v1.xml" (runtime-name : "standalone.v1.xml")
15:35:20,855 INFO [org.jboss.as.server.deployment] (MSC service thread 1-8) WFLYSRV0027: Starting deployment of "standalone.xml" (runtime-name: "standalone.xml")
15:35:20,855 INFO [org.jboss.as.server.deployment] (MSC service thread 1-7) WFLYSRV0027: Starting deployment of "standalone.v2.xml" (runtime-name: "standalone.v2.xml")
15:35:20,856 INFO [org.jboss.as.server.deployment] (MSC service thread 1-8) WFLYSRV0027: Starting deployment of "standalone.last.xml" (runtime-name: "standalone.last.xml")
15:35:20,895 INFO [org.jboss.as.server] (DeploymentScanner-threads - 2) WFLYSRV0010: Deployed "standalone.last.xml" (runtime-name : "standalone.last.xml")
15:35:20,895 INFO [org.jboss.as.server] (DeploymentScanner-threads - 2) WFLYSRV0010: Deployed "standalone.v2.xml" (runtime-name : "standalone.v2.xml")
15:35:20,895 INFO [org.jboss.as.server] (DeploymentScanner-threads - 2) WFLYSRV0010: Deployed "standalone.xml" (runtime-name : "standalone.xml")
15:35:25,951 INFO [org.jboss.as.server.deployment] (MSC service thread 1-7) WFLYSRV0028: Stopped deployment standalone.xml (runtime-name: standalone.xml) in 20ms
15:35:25,954 INFO [org.jboss.as.server.deployment] (MSC service thread 1-5) WFLYSRV0027: Starting deployment of "standalone.v3.xml" (runtime-name: "standalone.v3.xml")
15:35:25,954 INFO [org.jboss.as.server.deployment] (MSC service thread 1-4) WFLYSRV0027: Starting deployment of "standalone.xml" (runtime-name: "standalone.xml")
15:35:25,957 INFO [org.jboss.as.server.deployment] (MSC service thread 1-1) WFLYSRV0028: Stopped deployment standalone.last.xml (runtime-name: standalone.last.xml) in 2ms
15:35:25,964 INFO [org.jboss.as.server.deployment] (MSC service thread 1-7) WFLYSRV0027: Starting deployment of "standalone.last.xml" (runtime-name: "standalone.last.xml")
15:35:26,037 INFO [org.jboss.as.server] (DeploymentScanner-threads - 2) WFLYSRV0016: Replaced deployment "standalone.last.xml" with deployment "standalone.last.xml"
15:35:26,038 INFO [org.jboss.as.server] (DeploymentScanner-threads - 2) WFLYSRV0010: Deployed "standalone.v3.xml" (runtime-name : "standalone.v3.xml")
{code}
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 11 months
[JBoss JIRA] (JBIDE-25903) New wizards: pointless Help button
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-25903?page=com.atlassian.jira.plugi... ]
Andre Dietisheim updated JBIDE-25903:
-------------------------------------
Summary: New wizards: pointless Help button (was: OpenShift: Deploy Image to OpenShift - pointless Help button)
> New wizards: pointless Help button
> ----------------------------------
>
> Key: JBIDE-25903
> URL: https://issues.jboss.org/browse/JBIDE-25903
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: docker, openshift
> Affects Versions: 4.5.3.Final
> Environment: F28
> Reporter: Josef Kopriva
> Assignee: Andre Dietisheim
> Priority: Minor
> Fix For: 4.5.x
>
> Attachments: image-2018-04-05-08-19-09-880.png, new-resource-wizard.png
>
>
> !image-2018-04-05-08-19-09-880.png|thumbnail!
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 11 months
[JBoss JIRA] (JBIDE-25903) OpenShift: Deploy Image to OpenShift - pointless Help button
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-25903?page=com.atlassian.jira.plugi... ]
Andre Dietisheim commented on JBIDE-25903:
------------------------------------------
The question-mark button actually exists on a lot of wizard while having no function.
ex. create new resource wizard
!new-resource-wizard.png!
> OpenShift: Deploy Image to OpenShift - pointless Help button
> ------------------------------------------------------------
>
> Key: JBIDE-25903
> URL: https://issues.jboss.org/browse/JBIDE-25903
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: docker, openshift
> Affects Versions: 4.5.3.Final
> Environment: F28
> Reporter: Josef Kopriva
> Assignee: Andre Dietisheim
> Priority: Minor
> Fix For: 4.5.x
>
> Attachments: image-2018-04-05-08-19-09-880.png, new-resource-wizard.png
>
>
> !image-2018-04-05-08-19-09-880.png|thumbnail!
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 11 months