August 2018 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-26143) Add EAP support to SSP

by Jan Richter (JIRA)

[ https://issues.jboss.org/browse/JBIDE-26143?page=com.atlassian.jira.plugi... ] Jan Richter closed JBIDE-26143. ------------------------------- > Add EAP support to SSP > ---------------------- > > Key: JBIDE-26143 > URL: https://issues.jboss.org/browse/JBIDE-26143 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: runtime-server-protocol > Affects Versions: 4.6.0.AM3 > Reporter: Rob Stryker > Assignee: Rob Stryker > Fix For: 4.6.0.Final > > > Make EAP stuff work too. woo. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-26199) No response when adding a discovery path for the 2nd time / removing a non existing path

by Jan Richter (JIRA)

[ https://issues.jboss.org/browse/JBIDE-26199?page=com.atlassian.jira.plugi... ] Jan Richter closed JBIDE-26199. ------------------------------- > No response when adding a discovery path for the 2nd time / removing a non existing path > ---------------------------------------------------------------------------------------- > > Key: JBIDE-26199 > URL: https://issues.jboss.org/browse/JBIDE-26199 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: runtime-server-protocol > Affects Versions: 4.6.0.Final > Reporter: Jan Richter > Assignee: Rob Stryker > Fix For: 4.6.0.Final > > > server/addDiscoveryPath should have some way of notifying the client when it's trying to add a discovery path that has already been added. > same goes for server/removeDiscoveryPath when the path doesn't exist on the server -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-26140) Remove unit testing related jars from SSP distribution

by Jan Richter (JIRA)

[ https://issues.jboss.org/browse/JBIDE-26140?page=com.atlassian.jira.plugi... ] Jan Richter closed JBIDE-26140. ------------------------------- > Remove unit testing related jars from SSP distribution > ------------------------------------------------------ > > Key: JBIDE-26140 > URL: https://issues.jboss.org/browse/JBIDE-26140 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: runtime-server-protocol > Reporter: Denis Golovin > Assignee: Rob Stryker > Fix For: 4.6.0.Final > > Attachments: ssp-distribution.png > > > The size of zipped distribution is around 30MB. Could be less if unit test related jars like hamcrest or assertj are not included. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-26222) Schema generation doesn't include return values

by Jan Richter (JIRA)

[ https://issues.jboss.org/browse/JBIDE-26222?page=com.atlassian.jira.plugi... ] Jan Richter closed JBIDE-26222. ------------------------------- > Schema generation doesn't include return values > ----------------------------------------------- > > Key: JBIDE-26222 > URL: https://issues.jboss.org/browse/JBIDE-26222 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: runtime-server-protocol > Affects Versions: 4.6.0.Final > Reporter: Rob Stryker > Assignee: Rob Stryker > Fix For: 4.6.0.Final > > > Schema / Specification generation doesn't include return values. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBDS-4723) Eclipse marketplace is missing

by Anton Hughes (JIRA)

Anton Hughes created JBDS-4723: ---------------------------------- Summary: Eclipse marketplace is missing Key: JBDS-4723 URL: https://issues.jboss.org/browse/JBDS-4723 Project: Red Hat JBoss Developer Studio (devstudio) Issue Type: Enhancement Reporter: Anton Hughes In Jboss Version: 12.0.0.GA there is no eclipse marketplace . Im not sure if this is intentional or not. But Im sure a lot of users, like myself, find this a bit annoying. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-26290) Build: server fails on baseline check

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-26290?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-26290: ------------------------------------- Fix Version/s: 4.9.0.AM2 > Build: server fails on baseline check > ------------------------------------- > > Key: JBIDE-26290 > URL: https://issues.jboss.org/browse/JBIDE-26290 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: server > Affects Versions: 4.9.0.AM1 > Reporter: Andre Dietisheim > Priority: Blocker > Fix For: 4.9.0.AM2 > > > [build #2388|https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/Devstudio/view/devstudio_master/job/jbosstools-server_master/2388] currently fails with baseline check failures: > {code} > ... > 22:01:47 [INFO] org.jboss.ide.eclipse.as.serverAdapter.wtp.feature . FAILURE [ 1.052 s] > ... > 22:01:47 [INFO] org.jboss.tools.jmx.jolokia ........................ FAILURE [ 29.077 s] > ... > 22:01:47 [INFO] org.jboss.ide.eclipse.as.server.rse.integration.feature FAILURE [ 0.883 s] > ... > 22:01:47 [INFO] org.jboss.tools.wtp.runtimes.tomcat.feature ........ FAILURE [ 0.797 s] > {code} > {code} > 22:01:47 [ERROR] Failed to execute goal org.eclipse.tycho:tycho-p2-plugin:1.2.0:p2-metadata (attached-p2-metadata) on project org.jboss.tools.archives.scanner.feature: baseline and build artifacts have same version but different contents > 22:01:47 [ERROR] no-classifier: different > 22:01:47 [ERROR] feature.xml: different > 22:01:47 [ERROR] -> [Help 1] > 22:01:47 org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute goal org.eclipse.tycho:tycho-p2-plugin:1.2.0:p2-metadata (attached-p2-metadata) on project org.jboss.tools.archives.scanner.feature: baseline and build artifacts have same version but different contents > 22:01:47 no-classifier: different > 22:01:47 feature.xml: different > {code} > {code} > 22:01:48 [ERROR] Failed to execute goal org.eclipse.tycho:tycho-p2-plugin:1.2.0:p2-metadata (attached-p2-metadata) on project org.jboss.tools.jmx.jolokia: baseline and build artifacts have same version but different contents > 22:01:48 [ERROR] no-classifier: different > 22:01:48 [ERROR] org/jboss/tools/jmx/jolokia/internal/connection/JolokiaMBeanServerConnection.class: different > 22:01:48 [ERROR] -> [Help 1] > {code} > {code} > 22:01:48 [ERROR] Failed to execute goal org.eclipse.tycho:tycho-p2-plugin:1.2.0:p2-metadata (attached-p2-metadata) on project org.jboss.ide.eclipse.as.server.rse.integration.feature: baseline and build artifacts have same version but different contents > 22:01:48 [ERROR] no-classifier: different > 22:01:48 [ERROR] feature.xml: different > {code} > {code} > 22:01:48 [ERROR] Failed to execute goal org.eclipse.tycho:tycho-p2-plugin:1.2.0:p2-metadata (attached-p2-metadata) on project org.jboss.tools.wtp.runtimes.tomcat.feature: baseline and build artifacts have same version but different contents > 22:01:48 [ERROR] no-classifier: different > 22:01:48 [ERROR] feature.xml: different > {code} -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-26290) Build: server fails on baseline check

by Andre Dietisheim (JIRA)

Andre Dietisheim created JBIDE-26290: ---------------------------------------- Summary: Build: server fails on baseline check Key: JBIDE-26290 URL: https://issues.jboss.org/browse/JBIDE-26290 Project: Tools (JBoss Tools) Issue Type: Bug Components: server Affects Versions: 4.9.0.AM1 Reporter: Andre Dietisheim Priority: Blocker [build #2388|https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/Devstudio/view/devstudio_master/job/jbosstools-server_master/2388] currently fails with baseline check failures: {code} ... 22:01:47 [INFO] org.jboss.ide.eclipse.as.serverAdapter.wtp.feature . FAILURE [ 1.052 s] ... 22:01:47 [INFO] org.jboss.tools.jmx.jolokia ........................ FAILURE [ 29.077 s] ... 22:01:47 [INFO] org.jboss.ide.eclipse.as.server.rse.integration.feature FAILURE [ 0.883 s] ... 22:01:47 [INFO] org.jboss.tools.wtp.runtimes.tomcat.feature ........ FAILURE [ 0.797 s] {code} {code} 22:01:47 [ERROR] Failed to execute goal org.eclipse.tycho:tycho-p2-plugin:1.2.0:p2-metadata (attached-p2-metadata) on project org.jboss.tools.archives.scanner.feature: baseline and build artifacts have same version but different contents 22:01:47 [ERROR] no-classifier: different 22:01:47 [ERROR] feature.xml: different 22:01:47 [ERROR] -> [Help 1] 22:01:47 org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute goal org.eclipse.tycho:tycho-p2-plugin:1.2.0:p2-metadata (attached-p2-metadata) on project org.jboss.tools.archives.scanner.feature: baseline and build artifacts have same version but different contents 22:01:47 no-classifier: different 22:01:47 feature.xml: different {code} {code} 22:01:48 [ERROR] Failed to execute goal org.eclipse.tycho:tycho-p2-plugin:1.2.0:p2-metadata (attached-p2-metadata) on project org.jboss.tools.jmx.jolokia: baseline and build artifacts have same version but different contents 22:01:48 [ERROR] no-classifier: different 22:01:48 [ERROR] org/jboss/tools/jmx/jolokia/internal/connection/JolokiaMBeanServerConnection.class: different 22:01:48 [ERROR] -> [Help 1] {code} {code} 22:01:48 [ERROR] Failed to execute goal org.eclipse.tycho:tycho-p2-plugin:1.2.0:p2-metadata (attached-p2-metadata) on project org.jboss.ide.eclipse.as.server.rse.integration.feature: baseline and build artifacts have same version but different contents 22:01:48 [ERROR] no-classifier: different 22:01:48 [ERROR] feature.xml: different {code} {code} 22:01:48 [ERROR] Failed to execute goal org.eclipse.tycho:tycho-p2-plugin:1.2.0:p2-metadata (attached-p2-metadata) on project org.jboss.tools.wtp.runtimes.tomcat.feature: baseline and build artifacts have same version but different contents 22:01:48 [ERROR] no-classifier: different 22:01:48 [ERROR] feature.xml: different {code} -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-26251) Server adapter: cannot start in Debug using oc 3.11

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-26251?page=com.atlassian.jira.plugi... ] Andre Dietisheim commented on JBIDE-26251: ------------------------------------------ merged [openshift-restclient-java issue #339|https://github.com/openshift/openshift-restclient-java/issues/339], built and deployed new client library. Created a PR for this issue where the new client library is being used. PR was merged into master. Resolving. > Server adapter: cannot start in Debug using oc 3.11 > --------------------------------------------------- > > Key: JBIDE-26251 > URL: https://issues.jboss.org/browse/JBIDE-26251 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.9.0.AM1 > Environment: CDK > F28 > oc client 3.11 alpha - build from master > Reporter: Josef Kopriva > Assignee: Andre Dietisheim > Priority: Critical > Fix For: 4.9.0.AM2 > > > {code:java} > eclipse.buildId=12.9.0.AM1-v20180726-1026-B3091 > java.version=1.8.0_181 > java.vendor=Oracle Corporation > BootLoader constants: OS=linux, ARCH=x86_64, WS=gtk, NL=en_US > Framework arguments: -product com.jboss.devstudio.core.product > Command-line arguments: -data file:/home/jkopriva/devstudio_B3091_testing/workspace/ -os linux -ws gtk -arch x86_64 -product com.jboss.devstudio.core.product > org.jboss.tools.openshift.core > Error > Mon Jul 30 12:53:55 CEST 2018 > Could not launch server eap-app (Service) at OpenShift 3 (192.168.42.218) > com.openshift.restclient.OpenShiftException: OpenShiftBinaryCapability process exited: Error: unknown shorthand flag: 'p' in -p > Usage: > oc port-forward TYPE/NAME [LOCAL_PORT:]REMOTE_PORT [...[LOCAL_PORT_N:]REMOTE_PORT_N] [flags] > Examples: > # Listens on ports 5000 and 6000 locally, forwarding data to/from ports 5000 and 6000 in the pod > oc port-forward mypod 5000 6000 > > # Listens on port 8888 locally, forwarding to 5000 in the pod > oc port-forward mypod 8888:5000 > > # Listens on a random port locally, forwarding to 5000 in the pod > oc port-forward mypod :5000 > > # Listens on a random port locally, forwarding to 5000 in the pod > oc port-forward mypod 0:5000 > Options: > --pod-running-timeout=1m0s: The length of time (like 5s, 2m, or 3h, higher than zero) to wait until at least one pod is running > Use "oc options" for a list of global command-line options (applies to all commands). > at com.openshift.internal.restclient.capability.resources.AbstractOpenShiftBinaryCapability.checkProcessIsAlive(AbstractOpenShiftBinaryCapability.java:219) > at com.openshift.internal.restclient.capability.resources.AbstractOpenShiftBinaryCapability.startProcess(AbstractOpenShiftBinaryCapability.java:182) > at com.openshift.internal.restclient.capability.resources.AbstractOpenShiftBinaryCapability.start(AbstractOpenShiftBinaryCapability.java:176) > at com.openshift.internal.restclient.capability.resources.OpenShiftBinaryPortForwarding.forwardPorts(OpenShiftBinaryPortForwarding.java:112) > at org.jboss.tools.openshift.internal.core.portforwarding.PortForwardingUtils$1$1.runOCBinary(PortForwardingUtils.java:148) > at org.jboss.tools.openshift.internal.core.ocbinary.OCBinaryOperation.run(OCBinaryOperation.java:29) > at org.jboss.tools.openshift.internal.core.portforwarding.PortForwardingUtils$1.visit(PortForwardingUtils.java:150) > at org.jboss.tools.openshift.internal.core.portforwarding.PortForwardingUtils$1.visit(PortForwardingUtils.java:1) > at com.openshift.internal.restclient.model.KubernetesResource.accept(KubernetesResource.java:94) > at org.jboss.tools.openshift.internal.core.portforwarding.PortForwardingUtils.startPortForwarding(PortForwardingUtils.java:142) > at org.jboss.tools.openshift.core.server.behavior.OpenShiftLaunchController.startPortForwarding(OpenShiftLaunchController.java:366) > at org.jboss.tools.openshift.core.server.behavior.OpenShiftLaunchController$2.onDebugChange(OpenShiftLaunchController.java:267) > at org.jboss.tools.openshift.internal.core.server.debug.OpenShiftDebugMode.toggleDebugger(OpenShiftDebugMode.java:252) > at org.jboss.tools.openshift.internal.core.server.debug.OpenShiftDebugMode.execute(OpenShiftDebugMode.java:186) > at org.jboss.tools.openshift.core.server.behavior.OpenShiftLaunchController.updateOpenShift(OpenShiftLaunchController.java:111) > at org.jboss.tools.openshift.core.server.behavior.OpenShiftLaunchController.launch(OpenShiftLaunchController.java:90) > at org.jboss.ide.eclipse.as.wtp.core.server.launch.ControllableServerLaunchConfiguration.launch(ControllableServerLaunchConfiguration.java:52) > at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:859) > at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:717) > at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:712) > at org.eclipse.wst.server.core.internal.Server.startImpl2(Server.java:3566) > at org.eclipse.wst.server.core.internal.Server.startImpl(Server.java:3502) > at org.eclipse.wst.server.core.internal.Server$StartJob.run(Server.java:377) > at org.eclipse.core.internal.jobs.Worker.run(Worker.java:60) > {code} -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-26289) Update version identifier to 5.4.1-SNAPSHOT

by Koen Aers (JIRA)

[ https://issues.jboss.org/browse/JBIDE-26289?page=com.atlassian.jira.plugi... ] Koen Aers reassigned JBIDE-26289: --------------------------------- Assignee: Koen Aers > Update version identifier to 5.4.1-SNAPSHOT > ------------------------------------------- > > Key: JBIDE-26289 > URL: https://issues.jboss.org/browse/JBIDE-26289 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: hibernate > Affects Versions: 4.9.0.AM1 > Reporter: Koen Aers > Assignee: Koen Aers > Fix For: 4.9.0.AM2 > > -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-26289) Update version identifier to 5.4.1-SNAPSHOT

by Koen Aers (JIRA)

[ https://issues.jboss.org/browse/JBIDE-26289?page=com.atlassian.jira.plugi... ] Koen Aers updated JBIDE-26289: ------------------------------ Fix Version/s: 4.9.0.AM2 > Update version identifier to 5.4.1-SNAPSHOT > ------------------------------------------- > > Key: JBIDE-26289 > URL: https://issues.jboss.org/browse/JBIDE-26289 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: hibernate > Affects Versions: 4.9.0.AM1 > Reporter: Koen Aers > Assignee: Koen Aers > Fix For: 4.9.0.AM2 > > -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 8 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 August 2018