April 2016 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBTIS-657) Fuse EA tooling cannot be installed from central

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBTIS-657?page=com.atlassian.jira.plugin.... ] Fred Bricon commented on JBTIS-657: ----------------------------------- I probably messed something up in the central webpage. I'll look into it > Fuse EA tooling cannot be installed from central > ------------------------------------------------ > > Key: JBTIS-657 > URL: https://issues.jboss.org/browse/JBTIS-657 > Project: JBoss Tools Integration Stack > Issue Type: Bug > Components: distribution > Affects Versions: 4.3.0.CR1 > Reporter: Jan Richter > Assignee: Paul Leacu > Priority: Blocker > Fix For: 4.3.0.Final > > > It fails with the following message: > {noformat}Cannot complete the install because one or more required items could not be found. > Software being installed: JBoss Fuse Tooling JMX Bundles 8.0.0.Beta2-v20160401-1305-B821 (org.fusesource.ide.jmx.feature.feature.group 8.0.0.Beta2-v20160401-1305-B821) > Missing requirement: JBoss Fuse Tooling JMX Bundles 8.0.0.Beta2-v20160401-1305-B821 (org.fusesource.ide.jmx.feature.feature.group 8.0.0.Beta2-v20160401-1305-B821) requires 'org.eclipse.gemini.management 2.0.0.RELEASE' but it could not be found{noformat} > and this is in the error log: > {noformat}HTTP Server 'Gateway Timeout': https://devstudio.jboss.com/targetplatforms/jbdsistarget/9.0.1.Final-SNAP... -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (JBTIS-657) Fuse EA tooling cannot be installed from central

by Paul Leacu (JIRA)

[ https://issues.jboss.org/browse/JBTIS-657?page=com.atlassian.jira.plugin.... ] Paul Leacu commented on JBTIS-657: ---------------------------------- [~fbricon] - Hey - we have an issue where the Fuse Proxy Wizard appears without early access being enabled (Fuse Tooling is EA). If selected without EA it fails. If EA is enabled the wizard installs Fuse Tooling as expected and all is well. The Fuse Tooling wizard is only defined on the EA side of JBDSIS discovery: https://github.com/jbosstools/jbosstools-integration-stack/blob/master/de... Is there something I'm setting up wrong?? Thanks - to test: {code} ./jbdevstudio -vmargs \ -Djboss.discovery.directory.url=https://devstudio.redhat.com/9.0/staging/updates/integration-stack/discovery/9.0.0.CR1a/earlyaccess/devstudio-directory.xml \ -Djboss.discovery.site.integration-stack.url=https://devstudio.redhat.com/9.0/staging/updates/integration-stack/discovery/9.0.0.CR1a/ \ -Djboss.discovery.earlyaccess.site.integration-stack.url=https://devstudio.redhat.com/9.0/staging/updates/integration-stack/discovery/9.0.0.CR1a/earlyaccess/ {code} > Fuse EA tooling cannot be installed from central > ------------------------------------------------ > > Key: JBTIS-657 > URL: https://issues.jboss.org/browse/JBTIS-657 > Project: JBoss Tools Integration Stack > Issue Type: Bug > Components: distribution > Affects Versions: 4.3.0.CR1 > Reporter: Jan Richter > Assignee: Paul Leacu > Priority: Blocker > Fix For: 4.3.0.Final > > > It fails with the following message: > {noformat}Cannot complete the install because one or more required items could not be found. > Software being installed: JBoss Fuse Tooling JMX Bundles 8.0.0.Beta2-v20160401-1305-B821 (org.fusesource.ide.jmx.feature.feature.group 8.0.0.Beta2-v20160401-1305-B821) > Missing requirement: JBoss Fuse Tooling JMX Bundles 8.0.0.Beta2-v20160401-1305-B821 (org.fusesource.ide.jmx.feature.feature.group 8.0.0.Beta2-v20160401-1305-B821) requires 'org.eclipse.gemini.management 2.0.0.RELEASE' but it could not be found{noformat} > and this is in the error log: > {noformat}HTTP Server 'Gateway Timeout': https://devstudio.jboss.com/targetplatforms/jbdsistarget/9.0.1.Final-SNAP... -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-22152) Unknown launch is left in Debug view after deletion of an OS 3 server adapter

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22152?page=com.atlassian.jira.plugi... ] Fred Bricon updated JBIDE-22152: -------------------------------- Priority: Minor (was: Major) > Unknown launch is left in Debug view after deletion of an OS 3 server adapter > ----------------------------------------------------------------------------- > > Key: JBIDE-22152 > URL: https://issues.jboss.org/browse/JBIDE-22152 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.1.CR1 > Reporter: Marián Labuda > Assignee: Jeff MAURY > Priority: Minor > Labels: openshift_v3, server_adapter > Fix For: 4.4.0.Alpha1 > > Attachments: launches.png > > > When I create a new OS3 Server adapter, it also creates a launch in Debug view. If debugging is triggered on an OS3 Server adapter it creates another launch in Debug view with debug icon. When the OS3 Server adapter is removed, its launches stay in Debug view as Unknown and it is not possible to remove them. > !launches.png! -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-22133) Get error "UnsupportedMediaType' when create project/applications from JBT on Mac

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22133?page=com.atlassian.jira.plugi... ] Fred Bricon updated JBIDE-22133: -------------------------------- Fix Version/s: 4.4.0.Alpha1 > Get error "UnsupportedMediaType' when create project/applications from JBT on Mac > --------------------------------------------------------------------------------- > > Key: JBIDE-22133 > URL: https://issues.jboss.org/browse/JBIDE-22133 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.1.Beta2 > Environment: JBDS 9.1.0 Beta2-v20160127-2213-B262 > Mac OS > Reporter: Xia Zhao > Assignee: Jeff Cantrill > Labels: openshift_v3 > Fix For: 4.4.0.Alpha1 > > > Get error "UnsupportedMediaType" when create project and applications from JBT on Mac -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-22152) Unknown launch is left in Debug view after deletion of an OS 3 server adapter

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22152?page=com.atlassian.jira.plugi... ] Fred Bricon reassigned JBIDE-22152: ----------------------------------- Assignee: Jeff MAURY > Unknown launch is left in Debug view after deletion of an OS 3 server adapter > ----------------------------------------------------------------------------- > > Key: JBIDE-22152 > URL: https://issues.jboss.org/browse/JBIDE-22152 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.1.CR1 > Reporter: Marián Labuda > Assignee: Jeff MAURY > Labels: openshift_v3, server_adapter > Fix For: 4.4.0.Alpha1 > > Attachments: launches.png > > > When I create a new OS3 Server adapter, it also creates a launch in Debug view. If debugging is triggered on an OS3 Server adapter it creates another launch in Debug view with debug icon. When the OS3 Server adapter is removed, its launches stay in Debug view as Unknown and it is not possible to remove them. > !launches.png! -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-22152) Unknown launch is left in Debug view after deletion of an OS 3 server adapter

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22152?page=com.atlassian.jira.plugi... ] Fred Bricon updated JBIDE-22152: -------------------------------- Fix Version/s: 4.4.0.Alpha1 > Unknown launch is left in Debug view after deletion of an OS 3 server adapter > ----------------------------------------------------------------------------- > > Key: JBIDE-22152 > URL: https://issues.jboss.org/browse/JBIDE-22152 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.1.CR1 > Reporter: Marián Labuda > Assignee: Jeff MAURY > Labels: openshift_v3, server_adapter > Fix For: 4.4.0.Alpha1 > > Attachments: launches.png > > > When I create a new OS3 Server adapter, it also creates a launch in Debug view. If debugging is triggered on an OS3 Server adapter it creates another launch in Debug view with debug icon. When the OS3 Server adapter is removed, its launches stay in Debug view as Unknown and it is not possible to remove them. > !launches.png! -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-22115) Truncated error message display connecting to server

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22115?page=com.atlassian.jira.plugi... ] Fred Bricon updated JBIDE-22115: -------------------------------- Fix Version/s: 4.4.0.Alpha1 > Truncated error message display connecting to server > ---------------------------------------------------- > > Key: JBIDE-22115 > URL: https://issues.jboss.org/browse/JBIDE-22115 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Environment: Version: 9.1.0.GA > Build id: GA-v20160403-1700-B477 > Build date: 20160403-1700 > Reporter: Len DiMaggio > Assignee: Viacheslav Kabanovich > Priority: Minor > Fix For: 4.4.0.Alpha1 > > Attachments: bad_token_1.png, bad_token_2.png > > > See attached screenshot - the error message is truncated until the user expands the width of the dialog. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-22153) Closing log of a pod throws an exception

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22153?page=com.atlassian.jira.plugi... ] Fred Bricon updated JBIDE-22153: -------------------------------- Fix Version/s: 4.4.0.Alpha1 > Closing log of a pod throws an exception > ---------------------------------------- > > Key: JBIDE-22153 > URL: https://issues.jboss.org/browse/JBIDE-22153 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.1.CR1 > Reporter: Marián Labuda > Assignee: Xavier Coulon > Labels: openshift_v3 > Fix For: 4.4.0.Alpha1 > > > When I am trying to close log of a pod (build pod or application pod, does not matter which one) by clicking on gray view tool item Close, I get following exception > {code} > Exception reading pod log inputstream > java.io.IOException: Stream closed > at java.io.BufferedInputStream.getBufIfOpen(BufferedInputStream.java:170) > at java.io.BufferedInputStream.read(BufferedInputStream.java:336) > at java.io.SequenceInputStream.read(SequenceInputStream.java:207) > at java.io.BufferedInputStream.read1(BufferedInputStream.java:284) > at java.io.BufferedInputStream.read(BufferedInputStream.java:345) > at java.io.FilterInputStream.read(FilterInputStream.java:107) > at org.jboss.tools.openshift.internal.ui.job.PodLogsJob$ConsoleStreamPipe.runOCBinary(PodLogsJob.java:166) > at org.jboss.tools.openshift.internal.core.OCBinaryOperation.run(OCBinaryOperation.java:34) > at org.jboss.tools.openshift.internal.ui.job.PodLogsJob$ConsoleStreamPipe.run(PodLogsJob.java:153) > at java.lang.Thread.run(Thread.java:745) > {code} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-22134) Sometimes docker image data are not shown in Deploy to OpenShift wizard

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22134?page=com.atlassian.jira.plugi... ] Fred Bricon reassigned JBIDE-22134: ----------------------------------- Assignee: Jeff Cantrill > Sometimes docker image data are not shown in Deploy to OpenShift wizard > ----------------------------------------------------------------------- > > Key: JBIDE-22134 > URL: https://issues.jboss.org/browse/JBIDE-22134 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.1.CR1 > Reporter: Marián Labuda > Assignee: Jeff Cantrill > Labels: docker, openshift_v3 > Fix For: 4.4.0.Alpha1 > > > Sometimes docker image data are not shown/processed in Deploy to OpenShift wizard. Environment variables, exposed ports etc. Unfortunately I don't have a way to reproduce it 100 %, I am not sure at the moment what is causing it, but when deploying a local docker image (image already pulled) to OpenShift, environment variables and exposed ports are empty, even though when using an image which has not been pulled yet, I have not spotted this at all. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-22153) Closing log of a pod throws an exception

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22153?page=com.atlassian.jira.plugi... ] Fred Bricon reassigned JBIDE-22153: ----------------------------------- Assignee: Xavier Coulon > Closing log of a pod throws an exception > ---------------------------------------- > > Key: JBIDE-22153 > URL: https://issues.jboss.org/browse/JBIDE-22153 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.1.CR1 > Reporter: Marián Labuda > Assignee: Xavier Coulon > Labels: openshift_v3 > Fix For: 4.4.0.Alpha1 > > > When I am trying to close log of a pod (build pod or application pod, does not matter which one) by clicking on gray view tool item Close, I get following exception > {code} > Exception reading pod log inputstream > java.io.IOException: Stream closed > at java.io.BufferedInputStream.getBufIfOpen(BufferedInputStream.java:170) > at java.io.BufferedInputStream.read(BufferedInputStream.java:336) > at java.io.SequenceInputStream.read(SequenceInputStream.java:207) > at java.io.BufferedInputStream.read1(BufferedInputStream.java:284) > at java.io.BufferedInputStream.read(BufferedInputStream.java:345) > at java.io.FilterInputStream.read(FilterInputStream.java:107) > at org.jboss.tools.openshift.internal.ui.job.PodLogsJob$ConsoleStreamPipe.runOCBinary(PodLogsJob.java:166) > at org.jboss.tools.openshift.internal.core.OCBinaryOperation.run(OCBinaryOperation.java:34) > at org.jboss.tools.openshift.internal.ui.job.PodLogsJob$ConsoleStreamPipe.run(PodLogsJob.java:153) > at java.lang.Thread.run(Thread.java:745) > {code} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

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 2016