[JBoss JIRA] (ERT-623) Evaluate combination of Docker images of LS (from Che?) with LSP4E
by Florent Benoit (JIRA)
[ https://issues.jboss.org/browse/ERT-623?page=com.atlassian.jira.plugin.sy... ]
Florent Benoit commented on ERT-623:
------------------------------------
Please note that as we're switching to sidecar LS, new images would run lsp automatically
> 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] (ERT-623) Evaluate combination of Docker images of LS (from Che?) with LSP4E
by Florent Benoit (JIRA)
[ https://issues.jboss.org/browse/ERT-623?page=com.atlassian.jira.plugin.sy... ]
Florent Benoit commented on ERT-623:
------------------------------------
[~mickael_istria]I think by default images are configured to be "daemon"
so you need to override the entrypoint/cmd if you want to do docker run
for example for the centos .net image you'll have to run ./launch.sh as well
> 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] (ERT-623) Evaluate combination of Docker images of LS (from Che?) with LSP4E
by Mickael Istria (JIRA)
[ https://issues.jboss.org/browse/ERT-623?page=com.atlassian.jira.plugin.sy... ]
Mickael Istria commented on ERT-623:
------------------------------------
Thanks [~flbe]. So do I get it right that if I do a `docker run` on such image, I get a LS running which I can interact with over stdio?
> 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] (ERT-623) Evaluate combination of Docker images of LS (from Che?) with LSP4E
by Florent Benoit (JIRA)
[ https://issues.jboss.org/browse/ERT-623?page=com.atlassian.jira.plugin.sy... ]
Florent Benoit commented on ERT-623:
------------------------------------
1. Can an image like https://github.com/eclipse/che-dockerfiles/blob/master/recipes/centos_dot... be used as a regular Docker image independently of Che?
--> yes, there is no "che specific" inside the image
2. What is the typical communication channel used between client and LS? Can stdio be used?
--> stdio can be used (in Che5/6 there is a proxy injected in the image that is doing stdio calls)
also I know some images are using socat to map stdio over a listening port
> 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-25833) OpenShift ITests: Create ITests for deploying various docker image to OpenShift
by Josef Kopriva (JIRA)
[ https://issues.jboss.org/browse/JBIDE-25833?page=com.atlassian.jira.plugi... ]
Josef Kopriva updated JBIDE-25833:
----------------------------------
Sprint: devex #148 April 2018 (was: devex #147 April 2018)
> OpenShift ITests: Create ITests for deploying various docker image to OpenShift
> -------------------------------------------------------------------------------
>
> Key: JBIDE-25833
> URL: https://issues.jboss.org/browse/JBIDE-25833
> Project: Tools (JBoss Tools)
> Issue Type: Task
> Components: integration-tests, openshift
> Affects Versions: 4.5.3.AM3
> Reporter: Josef Kopriva
> Assignee: Josef Kopriva
> Fix For: 4.6.0.AM1
>
>
> Try images like:
> - saturnism/spring-boot-helloworld-ui (this create a long resource name, check validation, modify resource name)
> - sonatype/nexus (check environment variables in the wizard, ports and that it is working via browser)
> - try image with underscore (forbidden character in resource name), it should be replaced
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 11 months
[JBoss JIRA] (JBTIS-1218) Eclipse will not change to alternate JDK with Spring Boot project.
by Hiram Chirino (JIRA)
Hiram Chirino created JBTIS-1218:
------------------------------------
Summary: Eclipse will not change to alternate JDK with Spring Boot project.
Key: JBTIS-1218
URL: https://issues.jboss.org/browse/JBTIS-1218
Project: JBoss Tools Integration Stack
Issue Type: Bug
Reporter: Hiram Chirino
Feed back from [~egetchel] in a recent Fuse enablement session:
This seems specific to JBDS 11.x as it is not a problem in 10. Typical scenario - I start a new project in Eclipse and it defaults to a JRE enviornment. This gets picked up at runtime. I add the JDK to Eclipse. Normally, I can go into the project configuration and change the compile and runtime to use the new JDK. In Eclipse 11, we could not find any option to do this, and no matter what we did, running the Spring Boot project still defaulted back to the JRE. The only way to force Eclipse to use the JDK was to go into Eclipse and delete the reference to the JRE, so that only a single JDK existed.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 11 months
[JBoss JIRA] (JBTIS-1217) Creating a Fuse project in JBDS on lower resolutions does not render input fields
by Hiram Chirino (JIRA)
Hiram Chirino created JBTIS-1217:
------------------------------------
Summary: Creating a Fuse project in JBDS on lower resolutions does not render input fields
Key: JBTIS-1217
URL: https://issues.jboss.org/browse/JBTIS-1217
Project: JBoss Tools Integration Stack
Issue Type: Bug
Reporter: Hiram Chirino
[~egetchel] commented in a recent Fuse enablement that:
We have run into this issue during numerous workshops. JBDS running from within Virtual Box or KVM (Agile Integration Workshop) renders JDBS at a low resolution. The input boxes for creating a Spring Boot project do not render correctly, leaving the users stuck.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 11 months
[JBoss JIRA] (ERT-623) Evaluate combination of Docker images of LS (from Che?) with LSP4E
by Roland Grunberg (JIRA)
[ https://issues.jboss.org/browse/ERT-623?page=com.atlassian.jira.plugin.sy... ]
Roland Grunberg commented on ERT-623:
-------------------------------------
Do you mean with usage of the Eclipse Docker Tooling plugins (under Linux Tools Project) ? If yes, I think this could certainly be done. It might lead to exposing some things as API.
If the messages are sent over stdio I think it should be fine.
> 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