March 2016 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-21662) Server adapter: workspace project is not automatically published if there was no initial publish

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21662?page=com.atlassian.jira.plugi... ] Alexey Kazakov commented on JBIDE-21662: ---------------------------------------- If all needed changes are already merged to 4.3.x then please resolve this issue. So [~mlabuda] can verify it. > Server adapter: workspace project is not automatically published if there was no initial publish > ------------------------------------------------------------------------------------------------ > > Key: JBIDE-21662 > URL: https://issues.jboss.org/browse/JBIDE-21662 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.1.CR1 > Reporter: Marián Labuda > Assignee: Rob Stryker > Priority: Critical > Labels: openshift_v3, server_adapter > Fix For: 4.3.1.CR1 > > > When I am having a workspace project, OS3 application and server adapter, application should be automatically changed based on local file disk changes as it was introduced in JBIDE-21371. But auto-publish does not work if there was not performed initial publish on server adapter which links workspace project with OS 3 application. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-21761) Port mapping validation is not correct

by Viacheslav Kabanovich (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21761?page=com.atlassian.jira.plugi... ] Viacheslav Kabanovich commented on JBIDE-21761: ----------------------------------------------- [~xcoulon], please consider if https://github.com/jbosstools/jbosstools-openshift/pull/1035 is good enough to fix it. > Port mapping validation is not correct > -------------------------------------- > > Key: JBIDE-21761 > URL: https://issues.jboss.org/browse/JBIDE-21761 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.1.CR1 > Reporter: Marián Labuda > Assignee: Xavier Coulon > Labels: docker, openshift_v3 > Fix For: 4.3.1.CR1 > > Attachments: validation_msg.png > > > In Deploy docker image on the page with port mapping when adding a new port mapping there is a validation error telling that correct format of pod is alphanumeric, what is wrong. See following image. > !validation_msg.png! > There should be allowed only numbers in range 0-65535. It is not only validation message but it allows to create also mapping to port e.g. "abc123" what should not be possible. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-21662) Server adapter: workspace project is not automatically published if there was no initial publish

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21662?page=com.atlassian.jira.plugi... ] Rob Stryker commented on JBIDE-21662: ------------------------------------- As far as I can tell from my testing this is fixed, but there's always a possibility I'm doing it differently than someone else. It's not just JBIDE-21582 but also JBIDE-21835. But they're on the same topic branch. These two jiras represent significant changes to the server adapter and its publishing code...s o hopefully we can get more people testing on it.... in case there are other bugs hanging around. > Server adapter: workspace project is not automatically published if there was no initial publish > ------------------------------------------------------------------------------------------------ > > Key: JBIDE-21662 > URL: https://issues.jboss.org/browse/JBIDE-21662 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.1.CR1 > Reporter: Marián Labuda > Assignee: Rob Stryker > Priority: Critical > Labels: openshift_v3, server_adapter > Fix For: 4.3.1.CR1 > > > When I am having a workspace project, OS3 application and server adapter, application should be automatically changed based on local file disk changes as it was introduced in JBIDE-21371. But auto-publish does not work if there was not performed initial publish on server adapter which links workspace project with OS 3 application. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (ERT-83) com.google.gson is required but not named in any feature.xml [EBZ#487768]

by Victor Rubezhny (JIRA)

[ https://issues.jboss.org/browse/ERT-83?page=com.atlassian.jira.plugin.sys... ] Victor Rubezhny resolved ERT-83. -------------------------------- Resolution: Done > com.google.gson is required but not named in any feature.xml [EBZ#487768] > ------------------------------------------------------------------------- > > Key: ERT-83 > URL: https://issues.jboss.org/browse/ERT-83 > Project: Eclipse Release Train > Issue Type: Task > Components: JSDT > Reporter: Friendly Jira Robot > Assignee: Victor Rubezhny > Labels: General, bzira > > The bundle org.eclipse.wst.jsdt.js.npm had a dependency on com.google.gson, but that google bundle from Orbit is not mentioned by the enclosing feature org.eclipse.wst.jsdt.nodejs.feature. > This was found by doing a P2 mirror operation of the WTP repository and finding that com.google.gson was not brought along for the ride. > Though an install from the WTP repository will find the bundle and work, it's important for the feature to name the dependency also so that in the future if a patch is required on com.google.gson, we can create a feature patch to insert a newer version. This will be appreciated by those doing support in the future. > It will also mean that a mirror operation will bring along the proper set of dependencies. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-21662) Server adapter: workspace project is not automatically published if there was no initial publish

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21662?page=com.atlassian.jira.plugi... ] Fred Bricon commented on JBIDE-21662: ------------------------------------- That should be fixed once the initial state of the server is set to stopped to fix JBIDE-21582. Starting the server will automatically trigger a full publish, right [~rob.stryker]? > Server adapter: workspace project is not automatically published if there was no initial publish > ------------------------------------------------------------------------------------------------ > > Key: JBIDE-21662 > URL: https://issues.jboss.org/browse/JBIDE-21662 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.1.CR1 > Reporter: Marián Labuda > Assignee: Rob Stryker > Priority: Critical > Labels: openshift_v3, server_adapter > Fix For: 4.3.1.CR1 > > > When I am having a workspace project, OS3 application and server adapter, application should be automatically changed based on local file disk changes as it was introduced in JBIDE-21371. But auto-publish does not work if there was not performed initial publish on server adapter which links workspace project with OS 3 application. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-21836) Preferences: openshift 3 oc location resets to a different/old value on restart

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21836?page=com.atlassian.jira.plugi... ] Alexey Kazakov commented on JBIDE-21836: ---------------------------------------- Can someone from QE to test it too? [~mlabuda]? I saw this issue in action on Max's laptop :) > Preferences: openshift 3 oc location resets to a different/old value on restart > ------------------------------------------------------------------------------- > > Key: JBIDE-21836 > URL: https://issues.jboss.org/browse/JBIDE-21836 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Reporter: Max Rydahl Andersen > Assignee: Max Rydahl Andersen > Priority: Blocker > Labels: oc_binary, openshift_v3, preferences > Fix For: 4.3.1.CR1 > > > on start of eclipse new workspace the value is for reason unknown to me set to: > {code} > /Users/max/Downloads/openshift-origin-v1.0.3-1695461-darwin-amd64/oc > {code} > which does exist, but is old version and publish fails. > Then I set it to > {code} > /usr/local/bin/oc > {code} > now publish works. > Restart eclipse - old value returns and publish starts failing again. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-21662) Server adapter: workspace project is not automatically published if there was no initial publish

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21662?page=com.atlassian.jira.plugi... ] Alexey Kazakov commented on JBIDE-21662: ---------------------------------------- I would say it's pretty confusing for users. [~rob.stryker] does it require any significant work to fix? It's not a blocker but IMO it's critical. > Server adapter: workspace project is not automatically published if there was no initial publish > ------------------------------------------------------------------------------------------------ > > Key: JBIDE-21662 > URL: https://issues.jboss.org/browse/JBIDE-21662 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.1.CR1 > Reporter: Marián Labuda > Assignee: Rob Stryker > Labels: openshift_v3, server_adapter > Fix For: 4.3.1.CR1 > > > When I am having a workspace project, OS3 application and server adapter, application should be automatically changed based on local file disk changes as it was introduced in JBIDE-21371. But auto-publish does not work if there was not performed initial publish on server adapter which links workspace project with OS 3 application. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-21662) Server adapter: workspace project is not automatically published if there was no initial publish

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21662?page=com.atlassian.jira.plugi... ] Alexey Kazakov updated JBIDE-21662: ----------------------------------- Priority: Critical (was: Major) > Server adapter: workspace project is not automatically published if there was no initial publish > ------------------------------------------------------------------------------------------------ > > Key: JBIDE-21662 > URL: https://issues.jboss.org/browse/JBIDE-21662 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.1.CR1 > Reporter: Marián Labuda > Assignee: Rob Stryker > Priority: Critical > Labels: openshift_v3, server_adapter > Fix For: 4.3.1.CR1 > > > When I am having a workspace project, OS3 application and server adapter, application should be automatically changed based on local file disk changes as it was introduced in JBIDE-21371. But auto-publish does not work if there was not performed initial publish on server adapter which links workspace project with OS 3 application. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-21849) [AP] Not able to list services under a project after login to AP

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21849?page=com.atlassian.jira.plugi... ] Alexey Kazakov commented on JBIDE-21849: ---------------------------------------- This is not for 9.1.0 I guess. [~maxandersen]? > [AP] Not able to list services under a project after login to AP > ---------------------------------------------------------------- > > Key: JBIDE-21849 > URL: https://issues.jboss.org/browse/JBIDE-21849 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.1.Beta2 > Environment: -JBoss OpenShift 3 Tools 3.2.0.Alpha1-v20160310-0336-B1191 > -AP puddle: 2016-03-09.2 > -oc version: > oc v3.2.0.1 > kubernetes v1.2.0-alpha.7-703-gbc4550d > Reporter: Xia Zhao > Priority: Critical > Labels: openshift_v3 > > -Not able to list services under a project after login to RHAP, get error message "Could not list BuildConfig resources in namespace xia: {"kind":"Status","apiVersion":"v1","metadata":{},"status":"Failure","message":"the server could not find the requested resource","reason":"NotFound","details":{},"code":404}" > -Issue did not repro if switch to OSE > -Repro on Linux/Windows/Mac OS -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-21849) [AP] Not able to list services under a project after login to AP

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21849?page=com.atlassian.jira.plugi... ] Alexey Kazakov reassigned JBIDE-21849: -------------------------------------- Assignee: (was: Viacheslav Kabanovich) > [AP] Not able to list services under a project after login to AP > ---------------------------------------------------------------- > > Key: JBIDE-21849 > URL: https://issues.jboss.org/browse/JBIDE-21849 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.1.Beta2 > Environment: -JBoss OpenShift 3 Tools 3.2.0.Alpha1-v20160310-0336-B1191 > -AP puddle: 2016-03-09.2 > -oc version: > oc v3.2.0.1 > kubernetes v1.2.0-alpha.7-703-gbc4550d > Reporter: Xia Zhao > Priority: Critical > Labels: openshift_v3 > > -Not able to list services under a project after login to RHAP, get error message "Could not list BuildConfig resources in namespace xia: {"kind":"Status","apiVersion":"v1","metadata":{},"status":"Failure","message":"the server could not find the requested resource","reason":"NotFound","details":{},"code":404}" > -Issue did not repro if switch to OSE > -Repro on Linux/Windows/Mac OS -- 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 March 2016