April 2018 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-25895) Make Jax-RS features work headless for integration with JDT-LS

by Jeff MAURY (JIRA)

[ https://issues.jboss.org/browse/JBIDE-25895?page=com.atlassian.jira.plugi... ] Jeff MAURY reassigned JBIDE-25895: ---------------------------------- Assignee: Jeff MAURY > Make Jax-RS features work headless for integration with JDT-LS > -------------------------------------------------------------- > > Key: JBIDE-25895 > URL: https://issues.jboss.org/browse/JBIDE-25895 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: webservices > Reporter: Mickael Istria > Assignee: Jeff MAURY > > JDT-LS can be extended for Java edition. Jax-RS, which contributes completion providers, error markers and hovers should provide those in a headless bundle which doesn't depend on UI to be able to contribute to JDT-LS. > Wizards and other pure UI should be in a dedicated .ui bundle. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-25894) Evaluate providing Java EE support as jdt.ls extensions

by Jeff MAURY (JIRA)

[ https://issues.jboss.org/browse/JBIDE-25894?page=com.atlassian.jira.plugi... ] Jeff MAURY updated JBIDE-25894: ------------------------------- Fix Version/s: 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 > Reporter: Mickael Istria > Fix For: 4.5.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, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-25894) Evaluate providing Java EE support as jdt.ls extensions

by Jeff MAURY (JIRA)

[ https://issues.jboss.org/browse/JBIDE-25894?page=com.atlassian.jira.plugi... ] Jeff MAURY reassigned JBIDE-25894: ---------------------------------- Assignee: Rob Stryker > 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 > Reporter: Mickael Istria > Assignee: Rob Stryker > Fix For: 4.5.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, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23498) Integration tests: should consistently separate v3 from v2

by Josef Kopriva (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23498?page=com.atlassian.jira.plugi... ] Josef Kopriva closed JBIDE-23498. --------------------------------- Assignee: Josef Kopriva Resolution: Out of Date [~adietish] Closing - it is not relevant now, because ITests for v2 has been removed some time ago. > Integration tests: should consistently separate v3 from v2 > ---------------------------------------------------------- > > Key: JBIDE-23498 > URL: https://issues.jboss.org/browse/JBIDE-23498 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.4.2.AM3 > Reporter: Andre Dietisheim > Assignee: Josef Kopriva > Labels: integration_tests, openshift_v2, openshift_v3 > Fix For: 4.5.3.Final > > > org.jboss.tools.openshift.ui.bot.test is not consistently separating v2 from v3 tests (and utils etc.). We should do this so that we can easily remove v2 artifacts once we drop support for v2 -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23498) Integration tests: should consistently separate v3 from v2

by Josef Kopriva (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23498?page=com.atlassian.jira.plugi... ] Josef Kopriva updated JBIDE-23498: ---------------------------------- Fix Version/s: 4.5.3.Final (was: 4.5.x) > Integration tests: should consistently separate v3 from v2 > ---------------------------------------------------------- > > Key: JBIDE-23498 > URL: https://issues.jboss.org/browse/JBIDE-23498 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.4.2.AM3 > Reporter: Andre Dietisheim > Labels: integration_tests, openshift_v2, openshift_v3 > Fix For: 4.5.3.Final > > > org.jboss.tools.openshift.ui.bot.test is not consistently separating v2 from v3 tests (and utils etc.). We should do this so that we can easily remove v2 artifacts once we drop support for v2 -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-25894) Evaluate providing Java EE support as jdt.ls extensions

by Mickael Istria (JIRA)

[ https://issues.jboss.org/browse/JBIDE-25894?page=com.atlassian.jira.plugi... ] Mickael Istria commented on JBIDE-25894: ---------------------------------------- At the moment, it seems like JDT-LS totally ignores possible extensions from existing JDT extension point. It would be quite valuable to honor those in order to provide richer edition experience. > 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 > Reporter: Mickael Istria > > 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, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-25896) Reduce footprint for Headless usage with JDT-LS

by Mickael Istria (JIRA)

Mickael Istria created JBIDE-25896: -------------------------------------- Summary: Reduce footprint for Headless usage with JDT-LS Key: JBIDE-25896 URL: https://issues.jboss.org/browse/JBIDE-25896 Project: Tools (JBoss Tools) Issue Type: Sub-task Components: build Reporter: Mickael Istria JBoss Tools extensions for JDT-LS do consume a lot of disk space. While splitting the bundles into UI/non-UI for usage with JDT-LS, we should evaluate other useless dependencies to get rid of in order to lighten the resulting LS. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-25895) Make Jax-RS features work headless for integration with JDT-LS

by Mickael Istria (JIRA)

Mickael Istria created JBIDE-25895: -------------------------------------- Summary: Make Jax-RS features work headless for integration with JDT-LS Key: JBIDE-25895 URL: https://issues.jboss.org/browse/JBIDE-25895 Project: Tools (JBoss Tools) Issue Type: Sub-task Components: webservices Reporter: Mickael Istria JDT-LS can be extended for Java edition. Jax-RS, which contributes completion providers, error markers and hovers should provide those in a headless bundle which doesn't depend on UI to be able to contribute to JDT-LS. Wizards and other pure UI should be in a dedicated .ui bundle. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-25894) Evaluate providing Java EE support as jdt.ls extensions

by Mickael Istria (JIRA)

[ https://issues.jboss.org/browse/JBIDE-25894?page=com.atlassian.jira.plugi... ] Mickael Istria commented on JBIDE-25894: ---------------------------------------- To workaround the issue with JDT versions, I used the following command which seems to properly install everything at one (from Eclipse Platform zip, nightly build {quote} $ ./eclipse -nosplash -consoleLog -application org.eclipse.equinox.p2.director -repository http://download.eclipse.org/jdtls/snapshots/repository/latest/ -repository http://download.eclipse.org/eclipse/updates/4.8-I-builds/I20180402-2000/ -repository http://download.eclipse.org/releases/photon -repository http://download.jboss.org/jbosstools/oxygen/development/updates/ -installIU org.eclipse.jdt.ls.core/0.0.0 -installIU org.jboss.tools.ws.jaxrs.feature.feature.group/0.0.0 -installIU org.jboss.tools.cdi.feature.feature.group/0.0.0 -installIU org.jboss.tools.maven.hibernate.feature.feature.group/0.0.0 -installIU org.hibernate.eclipse.feature.feature.group/0.0.0 -installIU org.eclipse.m2e.wtp.jaxrs.feature.feature.group/0.0.0 {quote} I couldn't see Jax-RS contributing completion or warning because the Jax-RS plugin requires UI Harness to startup, and UI Harness is not available in JDT-LS. So for Jax-RS, it would require to first split the bundle into a UI and a non-UI part. I tried to get CDI reporting something, but I didn't manage to get CDI error markers even from JBoss Tools... So if anyone has an example project showing CDI warnings, please share it so I can test. [~fbricon] maybe? > 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 > Reporter: Mickael Istria > > 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, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-25858) Minishift binary is not set up after CDK runtime download

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-25858?page=com.atlassian.jira.plugi... ] Rob Stryker commented on JBIDE-25858: ------------------------------------- The reason this doesn't seem to work is a simple and dumb coding error. It is not the case that minishift home is the base of runtime detection. This was changed on March 20th. See this commit: https://github.com/jbosstools/jbosstools-openshift/pull/1697/files#diff-b... However... this error was due to poor logic, unfortunately. PR to come shortly. > Minishift binary is not set up after CDK runtime download > --------------------------------------------------------- > > Key: JBIDE-25858 > URL: https://issues.jboss.org/browse/JBIDE-25858 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: runtime-detection > Affects Versions: 4.5.3.AM3 > Reporter: Martin Malina > Assignee: Rob Stryker > > This is a followup of JBIDE-25835 . > Recently a new feature was added - cdk can be downloaded directly from the IDE now. > As with other runtimes, there are two main paths you can take: > a) New Server -> Download > b) Preferences -> Runtime Detection -> Download > tl;dr: b) doesn't work properly with cdk because minishift binary is still not set after the download. > There is quite a big difference between a) and b). With a), you are adding a server manually and once your download is finished, the correct path is predefined for you. Runtime detection is not involved. > With b), the server is downloaded, extracted and then the path is added to runtime detection which is in turn run. This will result in the new server being detected and added. > Now cdk should theoretically support both of these paths. a) works - you're in the middle of adding a cdk server manually, you invoke the download and once that's done, the minishift binary field is filled properly for you. > But b) doesn't work properly for cdk, because runtime detection for cdk is built around your minishift home and not the minishift binary path. (I don't really know why that's the case, but I guess you had a good reason for it.) So when you do b), cdk binary is downloaded, but what's added to runtime detection is ~/.minishift (or $MINISHIFT_HOME if set). The result is that the cdk server adapter is added once the download is finished, but the minishift binary remains empty. So the usefulness of this feature is questionable. > Maybe you will say that there is no way to fix this. I hope you will at least agree that this is not ideal and b) doesn't really work properly right now. > I don't know what the proper solution for this is but let me start with a question: Wouldn't it make sense to change runtime detection of cdk so that it uses the minishift binary as the main path? What's stopping us from doing that? > Sorry for the lengthy description, I felt I needed to explain the whole context here. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 6 months

1
0
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jbosstools-issues April 2018