April 2018 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-25898) OpenShift ITests: Fix ITests after latest changes in OpenShift Tooling

by Josef Kopriva (JIRA)

Josef Kopriva created JBIDE-25898: ------------------------------------- Summary: OpenShift ITests: Fix ITests after latest changes in OpenShift Tooling Key: JBIDE-25898 URL: https://issues.jboss.org/browse/JBIDE-25898 Project: Tools (JBoss Tools) Issue Type: Bug Components: integration-tests, openshift Affects Versions: 4.5.3.Final Reporter: Josef Kopriva Assignee: Josef Kopriva -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-25897) New Project validation uses wrong name space when there are two connections in OpenShift Explorer

by Denis Golovin (JIRA)

Denis Golovin created JBIDE-25897: ------------------------------------- Summary: New Project validation uses wrong name space when there are two connections in OpenShift Explorer Key: JBIDE-25897 URL: https://issues.jboss.org/browse/JBIDE-25897 Project: Tools (JBoss Tools) Issue Type: Bug Components: openshift Affects Versions: 4.5.3.AM3 Environment: Windows 10 Pro, CDK 3.4.0-alpha.1 Reporter: Denis Golovin Attachments: pyproject-error.gif !myproject-error.gif! Prerequisites to reproduce the issue: 1. Start CDK/Minishift 2. Create second connection with different user name 'developer3' for example 3. Click hyper link in explorer to create new Project 4. Use name 'myproject' 5. ERROR: {code}Could not create project "myproject": project.project.openshift.io "myproject" already exists Exception trying to POST https://192.168.99.100:8443/oapi/v1/projectrequests response code: 409 project.project.openshift.io "myproject" already exists{code} -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-25897) New Project validation uses wrong name space when there are two connections in OpenShift Explorer

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBIDE-25897?page=com.atlassian.jira.plugi... ] Denis Golovin updated JBIDE-25897: ---------------------------------- Description: !pyproject-error.gif! Prerequisites to reproduce the issue: 1. Start CDK/Minishift 2. Create second connection with different user name 'developer3' for example 3. Click hyper link in explorer to create new Project 4. Use name 'myproject' 5. ERROR: {code}Could not create project "myproject": project.project.openshift.io "myproject" already exists Exception trying to POST https://192.168.99.100:8443/oapi/v1/projectrequests response code: 409 project.project.openshift.io "myproject" already exists{code} was: !myproject-error.gif! Prerequisites to reproduce the issue: 1. Start CDK/Minishift 2. Create second connection with different user name 'developer3' for example 3. Click hyper link in explorer to create new Project 4. Use name 'myproject' 5. ERROR: {code}Could not create project "myproject": project.project.openshift.io "myproject" already exists Exception trying to POST https://192.168.99.100:8443/oapi/v1/projectrequests response code: 409 project.project.openshift.io "myproject" already exists{code} > New Project validation uses wrong name space when there are two connections in OpenShift Explorer > ------------------------------------------------------------------------------------------------- > > Key: JBIDE-25897 > URL: https://issues.jboss.org/browse/JBIDE-25897 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.5.3.AM3 > Environment: Windows 10 Pro, CDK 3.4.0-alpha.1 > Reporter: Denis Golovin > Attachments: pyproject-error.gif > > > !pyproject-error.gif! > Prerequisites to reproduce the issue: > 1. Start CDK/Minishift > 2. Create second connection with different user name 'developer3' for example > 3. Click hyper link in explorer to create new Project > 4. Use name 'myproject' > 5. ERROR: > {code}Could not create project "myproject": project.project.openshift.io "myproject" already exists > Exception trying to POST https://192.168.99.100:8443/oapi/v1/projectrequests response code: 409 project.project.openshift.io "myproject" already exists{code} -- This message was sent by Atlassian JIRA (v7.5.0#75005)

6 years, 1 month

1
0
0 / 0

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

by Mickael Istria (JIRA)

[ https://issues.jboss.org/browse/JBIDE-25895?page=com.atlassian.jira.plugi... ] Mickael Istria commented on JBIDE-25895: ---------------------------------------- Reducing priority because a blocker in JDT-LS ( https://github.com/eclipse/eclipse.jdt.ls/issues/613 ) would still make relatively hard to add Jax-RS features to it even if bundle is restructured at best. > 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 > Priority: Minor > > 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)

6 years, 1 month

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: ---------------------------------------- I'm taking this one as I already made the evaluation of it all, and found one blocker in JDT-LS which is captured in https://github.com/eclipse/eclipse.jdt.ls/issues/613 > 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: 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)

6 years, 1 month

1
0
0 / 0

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

by Mickael Istria (JIRA)

[ https://issues.jboss.org/browse/JBIDE-25895?page=com.atlassian.jira.plugi... ] Mickael Istria updated JBIDE-25895: ----------------------------------- Priority: Minor (was: Major) > 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 > Priority: Minor > > 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)

6 years, 1 month

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 reassigned JBIDE-25894: -------------------------------------- Assignee: Mickael Istria (was: 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: 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)

6 years, 1 month

1
0
0 / 0

[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)

6 years, 1 month

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)

6 years, 1 month

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)

6 years, 1 month

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jbosstools-issues April 2018