[JBoss JIRA] (JBIDE-25894) Evaluate providing Java EE support as jdt.ls extensions
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-25894?page=com.atlassian.jira.plugi... ]
Nick Boldt commented on JBIDE-25894:
------------------------------------
Probably too late for 4.5.3.Final so slip to 4.6.x
> Evaluate providing Java EE support as jdt.ls extensions
> -------------------------------------------------------
>
> Key: JBIDE-25894
> URL: https://issues.jboss.org/browse/JBIDE-25894
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: jsp/jsf/xml/html-source-editing
> Reporter: Mickael Istria
> Assignee: Mickael Istria
> Fix For: 4.6.x
>
>
> Jdt-LS relies on JDT for most features.
> WTP and JBoss Tools do extend JDT to provide additional features, such as Jax-RS completion.
> It would be worth investigating whether just adding a few bundles from wtp and JBoss Tools into JDT-LS can turn JDT-LS into a powerful tool for Java EE as well, and to evaluate what must and can be improved to enable it.
> As a good Java EE support requires a good Java support first, it's very likely that extending JDT-LS (on demand) for Java EE is the most productive and efficient way to have a Java EE language-server.
> As Jakarta EE moves to Eclipse.org, there are some discussions to improve JEE tools in Eclipse IDE and in general. So building on top of WebTools/JBoss Tools and allowing webtools/jbosstools to run in JDT-LS wo uld fit in the community mindset and may attract 3rd-party contributors to Eclipse Webtools.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 12 months
[JBoss JIRA] (JBIDE-25894) Evaluate providing Java EE support as jdt.ls extensions
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-25894?page=com.atlassian.jira.plugi... ]
Nick Boldt updated JBIDE-25894:
-------------------------------
Component/s: jsp/jsf/xml/html-source-editing
> Evaluate providing Java EE support as jdt.ls extensions
> -------------------------------------------------------
>
> Key: JBIDE-25894
> URL: https://issues.jboss.org/browse/JBIDE-25894
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: jsp/jsf/xml/html-source-editing
> Reporter: Mickael Istria
> Assignee: Mickael Istria
> Fix For: 4.6.x
>
>
> Jdt-LS relies on JDT for most features.
> WTP and JBoss Tools do extend JDT to provide additional features, such as Jax-RS completion.
> It would be worth investigating whether just adding a few bundles from wtp and JBoss Tools into JDT-LS can turn JDT-LS into a powerful tool for Java EE as well, and to evaluate what must and can be improved to enable it.
> As a good Java EE support requires a good Java support first, it's very likely that extending JDT-LS (on demand) for Java EE is the most productive and efficient way to have a Java EE language-server.
> As Jakarta EE moves to Eclipse.org, there are some discussions to improve JEE tools in Eclipse IDE and in general. So building on top of WebTools/JBoss Tools and allowing webtools/jbosstools to run in JDT-LS wo uld fit in the community mindset and may attract 3rd-party contributors to Eclipse Webtools.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 12 months
[JBoss JIRA] (JBIDE-25894) Evaluate providing Java EE support as jdt.ls extensions
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-25894?page=com.atlassian.jira.plugi... ]
Nick Boldt updated JBIDE-25894:
-------------------------------
Fix Version/s: 4.6.x
(was: 4.5.x)
> Evaluate providing Java EE support as jdt.ls extensions
> -------------------------------------------------------
>
> Key: JBIDE-25894
> URL: https://issues.jboss.org/browse/JBIDE-25894
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: jsp/jsf/xml/html-source-editing
> Reporter: Mickael Istria
> Assignee: Mickael Istria
> Fix For: 4.6.x
>
>
> Jdt-LS relies on JDT for most features.
> WTP and JBoss Tools do extend JDT to provide additional features, such as Jax-RS completion.
> It would be worth investigating whether just adding a few bundles from wtp and JBoss Tools into JDT-LS can turn JDT-LS into a powerful tool for Java EE as well, and to evaluate what must and can be improved to enable it.
> As a good Java EE support requires a good Java support first, it's very likely that extending JDT-LS (on demand) for Java EE is the most productive and efficient way to have a Java EE language-server.
> As Jakarta EE moves to Eclipse.org, there are some discussions to improve JEE tools in Eclipse IDE and in general. So building on top of WebTools/JBoss Tools and allowing webtools/jbosstools to run in JDT-LS wo uld fit in the community mindset and may attract 3rd-party contributors to Eclipse Webtools.
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 12 months
[JBoss JIRA] (JBIDE-25504) Support hot deploy for workspace dependencies for SpringBoot applications on OpenShift
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-25504?page=com.atlassian.jira.plugi... ]
Andre Dietisheim edited comment on JBIDE-25504 at 4/9/18 8:43 AM:
------------------------------------------------------------------
[~jeffmaury] to sum things up for now:
restart & running the new classes only work if I copy the classes (org folder) directly to
* */deployments/BOOT-INF/classes* (folder that contains the classes for the main springboot app)
* OR */deployments/BOOT-INF/lib/* (folder that contains the dependencies of the main springboot app)
It doesn't if I use an intermediary folder (aka I exploded the jar to a folder with the same/different name).
In both cases I can end up overwriting existing files since I cannot copy the classes to some unique intermediary folder. Thoughts?
was (Author: adietish):
[~jeffmaury] to sum things up for now:
restart & running the new classes only work if I copy the classes (org folder) directly to
* */deployments/BOOT-INF/classes* (folder that contains the classes for the main springboot app)
* OR */deployments/BOOT-INF/lib/* (folder that contains the dependencies of the main springboot app)
It doesn't if I use an intermediary folder (aka I exploded the jar to a folder with the same/different name).
In both cases I can end up overwriting existing files since I cannot copy the classes to some intermediary folder. Thoughts?
> Support hot deploy for workspace dependencies for SpringBoot applications on OpenShift
> --------------------------------------------------------------------------------------
>
> Key: JBIDE-25504
> URL: https://issues.jboss.org/browse/JBIDE-25504
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: openshift
> Affects Versions: 4.5.2.AM2
> Reporter: Jeff MAURY
> Assignee: Andre Dietisheim
> Labels: openshift, openshift_v3, server_adapter
> Fix For: 4.5.3.Final
>
> Attachments: springboot-dependencies.zip
>
>
> When a SpringBoot application is being deployed on OpenShift with the server adapter, we should support the following use case:
> * the SpringBoot app has a dependency which is avalailable in the workspace
> * when a modifiction is done on the dependency code, it should be synced to OpenShift by the server adapter
--
This message was sent by Atlassian JIRA
(v7.5.0#75005)
7 years, 12 months