September 2016 - jbosstools-issues

[JBoss JIRA] (JBIDE-22319) Make OpenshiftServer implement IConnectionFacade

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22319?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-22319: ------------------------------------- Fix Version/s: 4.4.2.AM2 (was: 4.4.2.AM1) > Make OpenshiftServer implement IConnectionFacade > ------------------------------------------------ > > Key: JBIDE-22319 > URL: https://issues.jboss.org/browse/JBIDE-22319 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Reporter: Thomas Mäder > Fix For: 4.4.2.AM2 > > > Add support for having a jmx conection via JBoss remoting to OpenShiftServer. > * need to add jmx client library > * find out the correct url > * configure deployment config with necessary env, ports, etc. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22915) Deploy Docker Image: Replication controller is not created for some images

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22915?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-22915: ------------------------------------- Fix Version/s: 4.4.2.AM2 (was: 4.4.2.AM1) > Deploy Docker Image: Replication controller is not created for some images > -------------------------------------------------------------------------- > > Key: JBIDE-22915 > URL: https://issues.jboss.org/browse/JBIDE-22915 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.4.1.AM3 > Reporter: Marián Labuda > Assignee: Jeff MAURY > Labels: deploy_docker_wizard, openshift_v3 > Fix For: 4.4.2.AM2 > > > When I am trying to deploy docker image docker.io/openshift/hello-openshift:v1.2.1 from context menu of the image in Docker Explorer it does not trigger a new replication controller and thus an application pod is not spinned up. When working from oc binary, replication controller is created successfully ("oc new-app docker.io/openshift/hello-openshift:v1.2.1") -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22915) Deploy Docker Image: Replication controller is not created for some images

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22915?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-22915: ------------------------------------- Sprint: devex #121 October 2016 (was: devex #120 September 2016) > Deploy Docker Image: Replication controller is not created for some images > -------------------------------------------------------------------------- > > Key: JBIDE-22915 > URL: https://issues.jboss.org/browse/JBIDE-22915 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.4.1.AM3 > Reporter: Marián Labuda > Assignee: Jeff MAURY > Labels: deploy_docker_wizard, openshift_v3 > Fix For: 4.4.2.AM2 > > > When I am trying to deploy docker image docker.io/openshift/hello-openshift:v1.2.1 from context menu of the image in Docker Explorer it does not trigger a new replication controller and thus an application pod is not spinned up. When working from oc binary, replication controller is created successfully ("oc new-app docker.io/openshift/hello-openshift:v1.2.1") -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBDS-4049) Cannot install Devstudio 10.1.0.GA into Eclipse Neon.1 RC3 (remediation required)

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBDS-4049?page=com.atlassian.jira.plugin.... ] Nick Boldt edited comment on JBDS-4049 at 9/23/16 11:15 AM: ------------------------------------------------------------ With the above PR, we're better... but I think due to the old 4.60.1.Final TP containing an old version of recommenders we're still getting some remediation: !4049-better-but-not-perfect.png|thumbnail! {code} Cannot complete the install because of a conflicting dependency. Software being installed: Code Recommenders Snipmatch 2.4.0.v20160607-1609 (org.eclipse.recommenders.snipmatch.rcp.feature.feature.group 2.4.0.v20160607-1609) Software currently installed: Code Recommenders for Java Developers 2.4.3.v20160825-1609 (org.eclipse.recommenders.rcp.feature.feature.group 2.4.3.v20160825-1609) Only one of the following can be installed at once: Code Recommenders Dependency Identification UI 2.4.0.v20160607-1609 (org.eclipse.recommenders.coordinates.rcp 2.4.0.v20160607-1609) Code Recommenders Dependency Identification UI 2.4.3.v20160708-1339 (org.eclipse.recommenders.coordinates.rcp 2.4.3.v20160708-1339) Cannot satisfy dependency: From: Code Recommenders for Java Developers 2.4.3.v20160825-1609 (org.eclipse.recommenders.rcp.feature.feature.group 2.4.3.v20160825-1609) To: org.eclipse.recommenders.coordinates.rcp [2.4.3.v20160708-1339] Cannot satisfy dependency: From: Code Recommenders Snipmatch UI 2.4.0.v20160607-1609 (org.eclipse.recommenders.snipmatch.rcp 2.4.0.v20160607-1609) To: bundle org.eclipse.recommenders.coordinates.rcp [2.4.0,2.4.1) Cannot satisfy dependency: From: Code Recommenders Snipmatch 2.4.0.v20160607-1609 (org.eclipse.recommenders.snipmatch.rcp.feature.feature.group 2.4.0.v20160607-1609) To: org.eclipse.recommenders.snipmatch.rcp [2.4.0.v20160607-1609]{code} was (Author: nickboldt): With the above PR, we're better... but I think due to the old 4.60.1.Final TP containing an old version of snipmatch we're still getting some remediation: !4049-better-but-not-perfect.png|thumbnail! > Cannot install Devstudio 10.1.0.GA into Eclipse Neon.1 RC3 (remediation required) > --------------------------------------------------------------------------------- > > Key: JBDS-4049 > URL: https://issues.jboss.org/browse/JBDS-4049 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Bug > Components: jsp/jsf/xml/html-source-editing, target-platform, updatesite, upstream > Affects Versions: 10.1.0.GA > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 10.2.0.AM1 > > Attachments: 4049-better-but-not-perfect.png, ds10.1_on_neon.1.RC3_remediation_needed.png > > > Steps to repro: > 1. Download eclipse-jee-neon-1-RC3-linux-gtk-x86_64.tar.gz, unpack and run > 2. Help > Eclipse Marketplace... > Search for "jboss" and install Red Hat JBoss Developer Studio 10.1.0.GA > 3. Remediation needed: > {code}Cannot complete the install because of a conflicting dependency. > Software being installed: Red Hat JBoss Developer Studio (Core Features) 10.1.0.v20160902-1725 (com.jboss.devstudio.core.feature.feature.group 10.1.0.v20160902-1725) > Software currently installed: JavaScript Development Tools 2.0.0.v201608301904 (org.eclipse.wst.jsdt.feature.feature.group 2.0.0.v201608301904) > Only one of the following can be installed at once: > JavaScript Development Tools Core 2.0.0.v201603171403 (org.eclipse.wst.jsdt.core 2.0.0.v201603171403) > JavaScript Development Tools Core 1.3.401.v201511181529 (org.eclipse.wst.jsdt.core 1.3.401.v201511181529) > JavaScript Development Tools Core 2.0.0.v201608251059 (org.eclipse.wst.jsdt.core 2.0.0.v201608251059) > JavaScript Development Tools Core 2.0.0.v201604281930 (org.eclipse.wst.jsdt.core 2.0.0.v201604281930) > JavaScript Development Tools Core 2.0.0.v201605251700 (org.eclipse.wst.jsdt.core 2.0.0.v201605251700) > Cannot satisfy dependency: > From: Red Hat JBoss Developer Studio (Core Features) 10.1.0.v20160902-1725 (com.jboss.devstudio.core.feature.feature.group 10.1.0.v20160902-1725) > To: com.jboss.devstudio.core.rpm.feature.feature.group [10.1.0.v20160902-1725] > Cannot satisfy dependency: > From: Red Hat JBoss Developer Studio (RPM Features) 10.1.0.v20160902-1725 (com.jboss.devstudio.core.rpm.feature.feature.group 10.1.0.v20160902-1725) > To: org.eclipse.wst.jsdt.feature.feature.group [2.0.0.v201605311817] > Cannot satisfy dependency: > From: JavaScript Development Tools 2.0.0.v201605311817 (org.eclipse.wst.jsdt.feature.feature.group 2.0.0.v201605311817) > To: org.eclipse.wst.jsdt.core [2.0.0.v201605251700] > Cannot satisfy dependency: > From: JavaScript Development Tools 2.0.0.v201608301904 (org.eclipse.wst.jsdt.feature.feature.group 2.0.0.v201608301904) > To: org.eclipse.wst.jsdt.core [2.0.0.v201608251059] > {code} -- [^ds10.1_on_neon.1.RC3_remediation_needed.png] -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBDS-4049) Cannot install Devstudio 10.1.0.GA into Eclipse Neon.1 RC3 (remediation required)

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBDS-4049?page=com.atlassian.jira.plugin.... ] Nick Boldt updated JBDS-4049: ----------------------------- Attachment: 4049-better-but-not-perfect.png With the above PR, we're better... but I think due to the old 4.60.1.Final TP containing an old version of snipmatch we're still getting some remediation: !4049-better-but-not-perfect.png|thumbnail! > Cannot install Devstudio 10.1.0.GA into Eclipse Neon.1 RC3 (remediation required) > --------------------------------------------------------------------------------- > > Key: JBDS-4049 > URL: https://issues.jboss.org/browse/JBDS-4049 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Bug > Components: jsp/jsf/xml/html-source-editing, target-platform, updatesite, upstream > Affects Versions: 10.1.0.GA > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 10.2.0.AM1 > > Attachments: 4049-better-but-not-perfect.png, ds10.1_on_neon.1.RC3_remediation_needed.png > > > Steps to repro: > 1. Download eclipse-jee-neon-1-RC3-linux-gtk-x86_64.tar.gz, unpack and run > 2. Help > Eclipse Marketplace... > Search for "jboss" and install Red Hat JBoss Developer Studio 10.1.0.GA > 3. Remediation needed: > {code}Cannot complete the install because of a conflicting dependency. > Software being installed: Red Hat JBoss Developer Studio (Core Features) 10.1.0.v20160902-1725 (com.jboss.devstudio.core.feature.feature.group 10.1.0.v20160902-1725) > Software currently installed: JavaScript Development Tools 2.0.0.v201608301904 (org.eclipse.wst.jsdt.feature.feature.group 2.0.0.v201608301904) > Only one of the following can be installed at once: > JavaScript Development Tools Core 2.0.0.v201603171403 (org.eclipse.wst.jsdt.core 2.0.0.v201603171403) > JavaScript Development Tools Core 1.3.401.v201511181529 (org.eclipse.wst.jsdt.core 1.3.401.v201511181529) > JavaScript Development Tools Core 2.0.0.v201608251059 (org.eclipse.wst.jsdt.core 2.0.0.v201608251059) > JavaScript Development Tools Core 2.0.0.v201604281930 (org.eclipse.wst.jsdt.core 2.0.0.v201604281930) > JavaScript Development Tools Core 2.0.0.v201605251700 (org.eclipse.wst.jsdt.core 2.0.0.v201605251700) > Cannot satisfy dependency: > From: Red Hat JBoss Developer Studio (Core Features) 10.1.0.v20160902-1725 (com.jboss.devstudio.core.feature.feature.group 10.1.0.v20160902-1725) > To: com.jboss.devstudio.core.rpm.feature.feature.group [10.1.0.v20160902-1725] > Cannot satisfy dependency: > From: Red Hat JBoss Developer Studio (RPM Features) 10.1.0.v20160902-1725 (com.jboss.devstudio.core.rpm.feature.feature.group 10.1.0.v20160902-1725) > To: org.eclipse.wst.jsdt.feature.feature.group [2.0.0.v201605311817] > Cannot satisfy dependency: > From: JavaScript Development Tools 2.0.0.v201605311817 (org.eclipse.wst.jsdt.feature.feature.group 2.0.0.v201605311817) > To: org.eclipse.wst.jsdt.core [2.0.0.v201605251700] > Cannot satisfy dependency: > From: JavaScript Development Tools 2.0.0.v201608301904 (org.eclipse.wst.jsdt.feature.feature.group 2.0.0.v201608301904) > To: org.eclipse.wst.jsdt.core [2.0.0.v201608251059] > {code} -- [^ds10.1_on_neon.1.RC3_remediation_needed.png] -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22810) OpenShift Explorer: empty at start

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22810?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-22810: ------------------------------------- Sprint: devex #119 August 2016, devex #121 October 2016 (was: devex #119 August 2016, devex #120 September 2016) > OpenShift Explorer: empty at start > ---------------------------------- > > Key: JBIDE-22810 > URL: https://issues.jboss.org/browse/JBIDE-22810 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.4.1.AM1 > Reporter: Viacheslav Kabanovich > Assignee: Viacheslav Kabanovich > Fix For: 4.4.2.AM2 > > Attachments: EmptyViewAtStart.png > > > When I close Eclipse with OpenShift Explorer not visible (by selecting another view in the same area of the workbench, or by switching another perspective), after I reopen Eclipse, and select OpenShift Explorer. I push 'Connect' button and can select for authenticating any available connection, it happens successfully, but the view remains empty. After I close/reopen OpenShift Explorer, it is opened populated with connections. > I have to add that it is not 100% reproducible. What is interesting, when starting it in the debugger, I reproduce it around 80%, while in normal run the probability is very low if do it leisurely, but can be increased to 50% if take the task with some dedication and find the right moment (very soon after the window opens) to select the explorer. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22869) Server adapter: Publishing code changes (via rsync) is buggy

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22869?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-22869: ------------------------------------- Fix Version/s: 4.4.2.AM2 (was: 4.4.2.AM1) > Server adapter: Publishing code changes (via rsync) is buggy > ------------------------------------------------------------ > > Key: JBIDE-22869 > URL: https://issues.jboss.org/browse/JBIDE-22869 > Project: Tools (JBoss Tools) > Issue Type: Epic > Components: openshift > Affects Versions: 4.4.1.AM2 > Reporter: Andre Dietisheim > Assignee: Rob Stryker > Fix For: 4.4.2.AM2 > > > Across the platform we have quite a few serious issues when publishing code via the server editor. This shows us that_ > - we don't test well enough > - we lack time -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22869) Server adapter: Publishing code changes (via rsync) is buggy

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22869?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-22869: ------------------------------------- Sprint: devex #121 October 2016 (was: devex #120 September 2016) > Server adapter: Publishing code changes (via rsync) is buggy > ------------------------------------------------------------ > > Key: JBIDE-22869 > URL: https://issues.jboss.org/browse/JBIDE-22869 > Project: Tools (JBoss Tools) > Issue Type: Epic > Components: openshift > Affects Versions: 4.4.1.AM2 > Reporter: Andre Dietisheim > Assignee: Rob Stryker > Fix For: 4.4.2.AM2 > > > Across the platform we have quite a few serious issues when publishing code via the server editor. This shows us that_ > - we don't test well enough > - we lack time -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22773) Openshift server adapter can't start with eap64-basic-s2i template on Windows: can't copy MANIFEST.MF reported

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22773?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-22773: ------------------------------------- Fix Version/s: 4.4.2.AM2 (was: 4.4.2.AM1) > Openshift server adapter can't start with eap64-basic-s2i template on Windows: can't copy MANIFEST.MF reported > -------------------------------------------------------------------------------------------------------------- > > Key: JBIDE-22773 > URL: https://issues.jboss.org/browse/JBIDE-22773 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift, upstream > Affects Versions: 4.4.1.AM2 > Reporter: Jeff MAURY > Assignee: Jeff MAURY > Priority: Critical > Labels: server > Fix For: 4.4.2.AM2 > > Attachments: screenshot-1.png > > > When starting the Openshift server adapter created from the eap64-basic-s2i template, the rsync phase reports the following error: > [^screenshot-1.png] -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22810) OpenShift Explorer: empty at start

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22810?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-22810: ------------------------------------- Fix Version/s: 4.4.2.AM2 (was: 4.4.2.AM1) > OpenShift Explorer: empty at start > ---------------------------------- > > Key: JBIDE-22810 > URL: https://issues.jboss.org/browse/JBIDE-22810 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.4.1.AM1 > Reporter: Viacheslav Kabanovich > Assignee: Viacheslav Kabanovich > Fix For: 4.4.2.AM2 > > Attachments: EmptyViewAtStart.png > > > When I close Eclipse with OpenShift Explorer not visible (by selecting another view in the same area of the workbench, or by switching another perspective), after I reopen Eclipse, and select OpenShift Explorer. I push 'Connect' button and can select for authenticating any available connection, it happens successfully, but the view remains empty. After I close/reopen OpenShift Explorer, it is opened populated with connections. > I have to add that it is not 100% reproducible. What is interesting, when starting it in the debugger, I reproduce it around 80%, while in normal run the probability is very low if do it leisurely, but can be increased to 50% if take the task with some dedication and find the right moment (very soon after the window opens) to select the explorer. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 6 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 September 2016