April 2018 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-25615) Update test cases for server in Polarion

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-25615?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-25615: ------------------------------- Fix Version/s: 4.6.x (was: 4.5.x) > Update test cases for server in Polarion > ---------------------------------------- > > Key: JBIDE-25615 > URL: https://issues.jboss.org/browse/JBIDE-25615 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: integration-tests, server > Affects Versions: 4.5.2.Final > Reporter: Josef Kopriva > Assignee: Josef Kopriva > Fix For: 4.6.x > > > Add latest EAP and WildFly, remove servers with expired support. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-25596) Wrong Git repo used when creating OpenShift application

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-25596?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-25596: ------------------------------- Fix Version/s: 4.6.x (was: 4.5.x) > Wrong Git repo used when creating OpenShift application > ------------------------------------------------------- > > Key: JBIDE-25596 > URL: https://issues.jboss.org/browse/JBIDE-25596 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.5.2.Final > Reporter: Jeff MAURY > Assignee: Dmitrii Bocharov > Labels: openshift > Fix For: 4.6.x > > > When creating an OpenShift application from a local Eclipse project, the Git repo URL is wrongly extracted. > I have clone a project so I have two remotes in my Git config: upstream and orign. I have created a branch and pushed to origin. > When the OpenShift application is created, the Git repo URL is upstream and the Git ref is the newly created branch. Thus this is invalid as the newly created branch does not exists on upstream and I would expect the Git repo URL to be origin -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-25554) Fuse PR build jobs are failing on dev-platform CCI Jenkins

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-25554?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-25554: ------------------------------- Fix Version/s: 4.6.x (was: 4.5.x) > Fuse PR build jobs are failing on dev-platform CCI Jenkins > ---------------------------------------------------------- > > Key: JBIDE-25554 > URL: https://issues.jboss.org/browse/JBIDE-25554 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build, fusetools > Affects Versions: 4.5.2.AM2 > Reporter: Andrej Podhradsky > Assignee: Andrej Podhradsky > Fix For: 4.6.x > > Attachments: fuse-prs-green.png, log.txt > > > The job jbosstools-fuse_PullRequest is failing on dev-platform but it passes on fusesource. See the attached log file. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-25456) Kubernetes editor: create editor and integration for yaml-language-server

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-25456?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-25456: ------------------------------- Fix Version/s: 4.6.x (was: 4.5.x) > Kubernetes editor: create editor and integration for yaml-language-server > ------------------------------------------------------------------------- > > Key: JBIDE-25456 > URL: https://issues.jboss.org/browse/JBIDE-25456 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: openshift > Affects Versions: 4.5.2.AM2 > Reporter: Andre Dietisheim > Assignee: Andre Dietisheim > Labels: kubernetes_editor, openshift_v3 > Fix For: 4.6.x > > > Given that there's a need to edit kubernetes/openshift json/yaml such an editor would be very helpful. We could easily create that by creating an editor that's based on lsp4e and integrating the yaml-language-server. > * The yaml-langauge server: https://github.com/redhat-developer/yaml-language-server > * Similar integration that's already been done for fabric8 analytics: https://github.com/fabric8-analytics/fabric8-analytics-devstudio-plugin -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-25446) Windows/Mac slave gets disconnected during job execution

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-25446?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-25446: ------------------------------- Fix Version/s: 4.6.x (was: 4.5.x) > Windows/Mac slave gets disconnected during job execution > -------------------------------------------------------- > > Key: JBIDE-25446 > URL: https://issues.jboss.org/browse/JBIDE-25446 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: qa > Affects Versions: 4.5.2.AM2 > Reporter: Ondrej Dockal > Assignee: Pavol Srna > Priority: Blocker > Labels: jenkins > Fix For: 4.6.0.AM1, 4.6.x > > > During jenkins job execution slaves is disconnected with exception > {code} > 19:09:27 19:09:27.096 DEBUG [WorkbenchTestable][AbstractWait] Waiting until shell matching Matcher matching when all matchers match: [Matcher matching widget which text matches: "Problem Occured"] is available.... > 19:09:32 FATAL: command execution failed > 19:09:32 java.io.IOException: Backing channel 'Channel to /10.8.247.148' is disconnected. > 19:09:32 at hudson.remoting.RemoteInvocationHandler.channelOrFail(RemoteInvocationHandler.java:191) > 19:09:32 at hudson.remoting.RemoteInvocationHandler.invoke(RemoteInvocationHandler.java:256) > 19:09:32 at com.sun.proxy.$Proxy68.isAlive(Unknown Source) > 19:09:32 at hudson.Launcher$RemoteLauncher$ProcImpl.isAlive(Launcher.java:1043) > 19:09:32 at hudson.Launcher$RemoteLauncher$ProcImpl.join(Launcher.java:1035) > 19:09:32 at hudson.Launcher$ProcStarter.join(Launcher.java:399) > 19:09:32 at hudson.tasks.Maven.perform(Maven.java:367) > 19:09:32 at hudson.tasks.BuildStepMonitor$1.perform(BuildStepMonitor.java:20) > 19:09:32 at hudson.model.AbstractBuild$AbstractBuildExecution.perform(AbstractBuild.java:779) > 19:09:32 at hudson.model.Build$BuildExecution.build(Build.java:205) > 19:09:32 at hudson.model.Build$BuildExecution.doRun(Build.java:162) > 19:09:32 at hudson.model.AbstractBuild$AbstractBuildExecution.run(AbstractBuild.java:534) > 19:09:32 at hudson.model.Run.execute(Run.java:1728) > 19:09:32 at hudson.matrix.MatrixRun.run(MatrixRun.java:146) > 19:09:32 at hudson.model.ResourceController.execute(ResourceController.java:98) > 19:09:32 at hudson.model.Executor.run(Executor.java:404) > 19:09:32 Caused by: java.io.IOException: Connection aborted: org.jenkinsci.remoting.nio.NioChannelHub$MonoNioTransport@5af9151e[name=Channel to /10.8.247.148] > 19:09:32 at org.jenkinsci.remoting.nio.NioChannelHub$NioTransport.abort(NioChannelHub.java:210) > 19:09:32 at org.jenkinsci.remoting.nio.NioChannelHub.run(NioChannelHub.java:635) > 19:09:32 at jenkins.util.ContextResettingExecutorService$1.run(ContextResettingExecutorService.java:28) > 19:09:32 at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) > 19:09:32 at java.util.concurrent.FutureTask.run(FutureTask.java:266) > 19:09:32 at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) > 19:09:32 at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) > 19:09:32 at java.lang.Thread.run(Thread.java:748) > 19:09:32 Caused by: java.io.IOException: Connection reset by peer > 19:09:32 at sun.nio.ch.FileDispatcherImpl.read0(Native Method) > 19:09:32 at sun.nio.ch.SocketDispatcher.read(SocketDispatcher.java:39) > 19:09:32 at sun.nio.ch.IOUtil.readIntoNativeBuffer(IOUtil.java:223) > 19:09:32 at sun.nio.ch.IOUtil.read(IOUtil.java:197) > 19:09:32 at sun.nio.ch.SocketChannelImpl.read(SocketChannelImpl.java:380) > 19:09:32 at org.jenkinsci.remoting.nio.FifoBuffer$Pointer.receive(FifoBuffer.java:142) > 19:09:32 at org.jenkinsci.remoting.nio.FifoBuffer.receive(FifoBuffer.java:359) > 19:09:32 at org.jenkinsci.remoting.nio.NioChannelHub.run(NioChannelHub.java:564) > 19:09:32 ... 6 more > 19:09:32 Build step 'Invoke top-level Maven targets' marked build as failure > {code} -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-25393) Move forge itests from jbosstools-integration-tests to jbosstools-forge

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-25393?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-25393: ------------------------------- Fix Version/s: 4.6.x (was: 4.5.x) > Move forge itests from jbosstools-integration-tests to jbosstools-forge > ----------------------------------------------------------------------- > > Key: JBIDE-25393 > URL: https://issues.jboss.org/browse/JBIDE-25393 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: forge, integration-tests > Affects Versions: 4.5.2.AM1 > Reporter: Josef Kopriva > Assignee: Josef Kopriva > Fix For: 4.6.x > > -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-25763) Delete Resources: Search filter should apply to Name and Type, too

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-25763?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-25763: ------------------------------- Fix Version/s: 4.6.x (was: 4.5.x) > Delete Resources: Search filter should apply to Name and Type, too > ------------------------------------------------------------------ > > Key: JBIDE-25763 > URL: https://issues.jboss.org/browse/JBIDE-25763 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.5.3.AM2 > Reporter: Josef Kopriva > Assignee: Andre Dietisheim > Labels: delete_resources > Fix For: 4.6.x > > Attachments: afterChangingFilter.png, afterOpening.png > > > Usecase 2 as reported in JBIDE-25755 (in which Usecase 1 was fixed): > {quote} > Delete resources filter does not work as expected - there are 2 use cases: > 1. After opening wizard there are shown also *Secret* type resources: > !afterOpening.png|thumbnail! > , but after changing filter a deleting it, *Secret*s are not shown: > !afterChangingFilter.png|thumbnail! > 2. In my opinion *Label filter* should also work for columns *Name* and *Type* > {quote} -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 11 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 closed JBIDE-25894. ---------------------------------- Resolution: Partially Completed I'm closing it as partially complete. The possibility was evaluated, some new questions and proposals emerged. > 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, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-25597) TP: create target platforms based on Eclipse Photon

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-25597?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-25597: ------------------------------- Fix Version/s: 4.6.0.AM2 4.6.0.AM3 > TP: create target platforms based on Eclipse Photon > --------------------------------------------------- > > Key: JBIDE-25597 > URL: https://issues.jboss.org/browse/JBIDE-25597 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: target-platform > Affects Versions: 4.5.2.Final > Reporter: Jeff MAURY > Assignee: Nick Boldt > Labels: target-platform > Fix For: 4.6.0.AM1, 4.6.0.AM2, 4.6.0.AM3, 4.6.0.Final > > Attachments: base.log > > > In order to start Photon based builds, we need a working Photon based target platform > For sprint 148 / AM1: Photon.0.M6 > For sprint 149 / AM2: Photon.0.M7 > For sprint 150 / AM3: Photon.0.RC3 > For sprint 151 / GA: Photon.0.GA -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 11 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 updated JBIDE-25894: ----------------------------------- I believe that this is currently a too expensive task to work on. I expected JDT-LS would be more extensible and able to consume typical Eclipse IDE extensions to forward it through LSP, but it isn't really extensible at the moment. I've opened a ticket to JDT-LS to discuss extensibility, and lack of ability to reuse the existing ecosystem of extensions for Eclipse IDE into JDT-LS. At the moment, it seems like JDT-LS devs are considering implementing extensibility into JDT-LS as specific extension points (basically mimicking most extension points for JDT-UI). I've mentioned there my opinion that it's IMO not an affordable task -it took a dozen of years of very competent and numerous developers to do it for JDT UI-, and that it would be better (for Cloud use-cases) to consider ways to re-use existing extensions and extension points rather than creating new ones. The discussions about extensibility stopped there. One sub-topic that was discussed in obviously hardware/CPU/RAM cost. Indeed, if we want JDT-LS to become extensible and/or reuse existing ecosystem of Eclipse extensions, it's going to make it bigger, it's not something we can avoid to get the resource requirements growing as we add features. On the other hand, growing an existing LS which already have good support for Java to add Java EE features is still going to be cheaper that mulitplying LSs: one for plain Java, one for Java EE, one for Spring... which would have to duplicate work. So, as part of this "be ready for Language Servers to get bigger as it gets richer", one topic that has been mentioned is evaluating possibilities of multi-tenant/multi-users Eclipse IDE workspaces. This would allow to get 1 LS serving multiple users/tasks, resulting in most resources being shared by multiple users, which should make it a relatively cheap resources/user ration I've opened a ERT-622 about it and this is a path we're currently trying to evaluate as we believe it would be very profitable for all Eclipse-based language servers, and all Eclipse-based apps in general. It wouldn't be an easy task though, but it's too early to get some estimate. > 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, 11 months

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jbosstools-issues April 2018