October 2016 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-22803) Explorer: When OS projects are created and deleted, seems Openshift explorer restores non existing values

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22803?page=com.atlassian.jira.plugi... ] Andre Dietisheim edited comment on JBIDE-22803 at 10/10/16 11:15 AM: --------------------------------------------------------------------- [~jcantrill] [~bdshadow] I grok/agree that we should ideally not rely on versions to determine whether a feature is (not) present. But if a try/fallback is hacky I believe we should. In the specific case trying to watch projects and catching it feels hacky since it seems that we have to consider the timing and the repetition. To top this claim it looks like there's a bug in the server where we get an error even though the message that we get presented reports "OK, could watch project". ([~bdshadow] you might want to supply the details?). Furthermore we need an alternative approach if projects are not watchable. Maybe polling and freshing projects? We could possibly do the version check in the client library (and not in JBT) preventing consumers from relying on versions. I still believe that offering access to the version still could be a nice feature, already if its just for display purposes. was (Author: adietish): [~jcantrill] [~bdshadow] I grok/agree that we should ideally not rely on versions to determine whether a feature is (not) present. But if a try/fallback is hacky I believe we should. In the specific case trying to watch projects and catching it feels hacky since it seems that we have to consider the timing and the repetition. To top this claim it looks like there's a bug in the server where we get an error even though the message that we get presented reports "OK, could watch project". ([~bdshadow] you might want to supply the details?). Furthermore we need an alternative approach if projects are not watchable. We could possibly do it in the client library (and not in JBT) preventing consumers from relying on versions. I still believe that offering access to the version still could be a nice feature, already if its just for display purposes. > Explorer: When OS projects are created and deleted, seems Openshift explorer restores non existing values > --------------------------------------------------------------------------------------------------------- > > Key: JBIDE-22803 > URL: https://issues.jboss.org/browse/JBIDE-22803 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.4.1.AM2 > Reporter: Jeff MAURY > Assignee: Dmitrii Bocharov > Labels: explorer, openshift, openshift_v3 > Fix For: 4.4.2.AM2 > > Attachments: after application creation.png, after build finished.png, Openshift Web Console.png, screenshot-1.png > > > EXEC: create an Openshift project > EXEC: expand it > EXEC: Create an application in this project (nodejs-example) > ASSERT: wait for the pod to be available > EXEC: delete the Openshit project > EXEC: create an Openshift project (using the same name. You may have to repeat this step as you may got error that it still exists) > EXEC: expand it > EXEC: Create an application in this project (nodejs-example) > EXEC: expand the nodejs-example node > ASSERT: you should see 2 pods the old one and the build pod you just created: [^screenshot-1.png] -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22803) Explorer: When OS projects are created and deleted, seems Openshift explorer restores non existing values

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22803?page=com.atlassian.jira.plugi... ] Andre Dietisheim edited comment on JBIDE-22803 at 10/10/16 11:08 AM: --------------------------------------------------------------------- [~jcantrill] [~bdshadow] I grok/agree that we should ideally not rely on versions to determine whether a feature is (not) present. But if a try/fallback is hacky I believe we should. In the specific case trying to watch projects and catching it feels hacky since it seems that we have to consider the timing and the repetition. To top this claim it looks like there's a bug in the server where we get an error even though the message that we get presented reports "OK, could watch project". ([~bdshadow] you might want to supply the details?). Furthermore we need an alternative approach if projects are not watchable. We could possibly do it in the client library (and not in JBT) preventing consumers from relying on versions. I still believe that offering access to the version still could be a nice feature, already if its just for display purposes. was (Author: adietish): [~jcantrill] [~bdshadow] I grok/agree that we should ideally not rely on versions to determine whether a feature is (not) present. But if a try/fallback is hacky I believe we should. In the specific case trying to watch projects and catching it feels hacky since it seems that we have to consider the timing and the repetition. To top this claim it looks like there's a bug in the server where we get an error even though the message that we get presented reports "OK, could watch project". ([~bdshadow] you might want to supply the details?). We could possibly do it in the client library (and not in JBT) preventing consumers from relying on versions. I still believe that offering access to the version still could be a nice feature, already if its just for display purposes. > Explorer: When OS projects are created and deleted, seems Openshift explorer restores non existing values > --------------------------------------------------------------------------------------------------------- > > Key: JBIDE-22803 > URL: https://issues.jboss.org/browse/JBIDE-22803 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.4.1.AM2 > Reporter: Jeff MAURY > Assignee: Dmitrii Bocharov > Labels: explorer, openshift, openshift_v3 > Fix For: 4.4.2.AM2 > > Attachments: after application creation.png, after build finished.png, Openshift Web Console.png, screenshot-1.png > > > EXEC: create an Openshift project > EXEC: expand it > EXEC: Create an application in this project (nodejs-example) > ASSERT: wait for the pod to be available > EXEC: delete the Openshit project > EXEC: create an Openshift project (using the same name. You may have to repeat this step as you may got error that it still exists) > EXEC: expand it > EXEC: Create an application in this project (nodejs-example) > EXEC: expand the nodejs-example node > ASSERT: you should see 2 pods the old one and the build pod you just created: [^screenshot-1.png] -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22803) Explorer: When OS projects are created and deleted, seems Openshift explorer restores non existing values

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22803?page=com.atlassian.jira.plugi... ] Andre Dietisheim edited comment on JBIDE-22803 at 10/10/16 10:58 AM: --------------------------------------------------------------------- [~jcantrill] [~bdshadow] I grok/agree that we should ideally not rely on versions to determine whether a feature is (not) present. But if a try/fallback is hacky I believe we should. In the specific case trying to watch projects and catching it feels hacky since it seems that we have to consider the timing and the repetition. To top this claim it looks like there's a bug in the server where we get an error even though the message that we get presented reports "OK, could watch project". ([~bdshadow] you might want to supply the details?). We could possibly do it in the client library (and not in JBT) preventing consumers from relying on versions. I still believe that offering access to the version still could be a nice feature, already if its just for display purposes. was (Author: adietish): [~jcantrill] [~bdshadow] I grok/agree that we should ideally not rely on versions to determine whether a feature is (not) present. But if a try/fallback is hacky I believe we should. We could possibly do it in the client library (and not in JBT) preventing consumers from relying on versions. I still believe that offering access to the version still could be a nice feature, already if its just for display purposes. > Explorer: When OS projects are created and deleted, seems Openshift explorer restores non existing values > --------------------------------------------------------------------------------------------------------- > > Key: JBIDE-22803 > URL: https://issues.jboss.org/browse/JBIDE-22803 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.4.1.AM2 > Reporter: Jeff MAURY > Assignee: Dmitrii Bocharov > Labels: explorer, openshift, openshift_v3 > Fix For: 4.4.2.AM2 > > Attachments: after application creation.png, after build finished.png, Openshift Web Console.png, screenshot-1.png > > > EXEC: create an Openshift project > EXEC: expand it > EXEC: Create an application in this project (nodejs-example) > ASSERT: wait for the pod to be available > EXEC: delete the Openshit project > EXEC: create an Openshift project (using the same name. You may have to repeat this step as you may got error that it still exists) > EXEC: expand it > EXEC: Create an application in this project (nodejs-example) > EXEC: expand the nodejs-example node > ASSERT: you should see 2 pods the old one and the build pod you just created: [^screenshot-1.png] -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22803) Explorer: When OS projects are created and deleted, seems Openshift explorer restores non existing values

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22803?page=com.atlassian.jira.plugi... ] Andre Dietisheim commented on JBIDE-22803: ------------------------------------------ [~jcantrill] [~bdshadow] I grok/agree that we should ideally not rely on versions to determine whether a feature is (not) present. But if a try/fallback is hacky I believe we should. We could possibly do it in the client library (and not in JBT) preventing consumers from relying on versions. I still believe that offering access to the version still could be a nice feature, already if its just for display purposes. > Explorer: When OS projects are created and deleted, seems Openshift explorer restores non existing values > --------------------------------------------------------------------------------------------------------- > > Key: JBIDE-22803 > URL: https://issues.jboss.org/browse/JBIDE-22803 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.4.1.AM2 > Reporter: Jeff MAURY > Assignee: Dmitrii Bocharov > Labels: explorer, openshift, openshift_v3 > Fix For: 4.4.2.AM2 > > Attachments: after application creation.png, after build finished.png, Openshift Web Console.png, screenshot-1.png > > > EXEC: create an Openshift project > EXEC: expand it > EXEC: Create an application in this project (nodejs-example) > ASSERT: wait for the pod to be available > EXEC: delete the Openshit project > EXEC: create an Openshift project (using the same name. You may have to repeat this step as you may got error that it still exists) > EXEC: expand it > EXEC: Create an application in this project (nodejs-example) > EXEC: expand the nodejs-example node > ASSERT: you should see 2 pods the old one and the build pod you just created: [^screenshot-1.png] -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBTIS-702) BxMS feature in marketplace doesn't install Kie navigator

by Andrej Podhradsky (JIRA)

[ https://issues.jboss.org/browse/JBTIS-702?page=com.atlassian.jira.plugin.... ] Andrej Podhradsky closed JBTIS-702. ----------------------------------- Verified with Eclipse Mars.2 for JEE Developers + JBDS-IS 9.0.2.GA > BxMS feature in marketplace doesn't install Kie navigator > --------------------------------------------------------- > > Key: JBTIS-702 > URL: https://issues.jboss.org/browse/JBTIS-702 > Project: JBoss Tools Integration Stack > Issue Type: Bug > Components: distribution > Affects Versions: 9.0.0.GA > Environment: Eclipse Mars.2 for JEE Developers > Reporter: Andrej Podhradsky > Assignee: Paul Leacu > Fix For: 9.0.2.GA > > > After installing BxMS feature form marketplace I noticed that the Kie Navigator is missing. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBDS-4088) Stop building the devstudio src.zip as it is now replaced by a link to github

by Lukáš Valach (JIRA)

[ https://issues.jboss.org/browse/JBDS-4088?page=com.atlassian.jira.plugin.... ] Lukáš Valach commented on JBDS-4088: ------------------------------------ Hi Nick, I checked that build of jbdevstudio-product doesn't produce *-src.zip, but sources zip is still mentioned in [README.md|https://github.com/jbdevstudio/jbdevstudio-product/blob/master/...]. Should you update readme please? Thank you in advance. > Stop building the devstudio src.zip as it is now replaced by a link to github > ----------------------------------------------------------------------------- > > Key: JBDS-4088 > URL: https://issues.jboss.org/browse/JBDS-4088 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Task > Components: build > Affects Versions: 10.2.0.AM1 > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 10.2.0.AM2 > > > Per https://trello.com/c/OhNmvELX/4-remove-jbds-sources-zip-from-list-of-deli... it's time to stop building the devstudio src.zip entirely, so it won't be included in the deliverables on developers.redhat.com and in the CSP. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBTIS-914) Integration Stack features have incorrect versions

by Andrej Podhradsky (JIRA)

[ https://issues.jboss.org/browse/JBTIS-914?page=com.atlassian.jira.plugin.... ] Andrej Podhradsky closed JBTIS-914. ----------------------------------- Verified with JBDS-IS 9.0.2. Now, all the mentioned features are of the version 9.0.2.GA-v20161003-1506-B66. > Integration Stack features have incorrect versions > -------------------------------------------------- > > Key: JBTIS-914 > URL: https://issues.jboss.org/browse/JBTIS-914 > Project: JBoss Tools Integration Stack > Issue Type: Bug > Components: distribution > Affects Versions: 4.0.0 > Reporter: Andrej Podhradsky > Assignee: Paul Leacu > Priority: Critical > Fix For: 9.0.2.GA > > > |com.jboss.devstudio.integration-stack.bpr.feature|9.0.2.CR1| > |com.jboss.devstudio.integration-stack.ds.feature|9.0.2.CR1| > |com.jboss.devstudio.integration-stack.fuse.feature|9.0.2.CR1| > |com.jboss.devstudio.integration-stack.soa.feature|9.0.2.CR1| > The version should be something like *9.0.1.GA-v20160808-1454-B27* -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBDS-4076) "RPM release" mismatch between src.rpm and x86_64.rpm

by Lukáš Valach (JIRA)

[ https://issues.jboss.org/browse/JBDS-4076?page=com.atlassian.jira.plugin.... ] Lukáš Valach closed JBDS-4076. ------------------------------ Verified in 10.2.0.AM2. All RPMs which are available on [FTP server|https://devstudio.jboss.com/10.0/snapshots/builds/devstudio.rpm_ma...] have correct time. Src rpm has always same timestamp as 86_64.rpm. > "RPM release" mismatch between src.rpm and x86_64.rpm > ----------------------------------------------------- > > Key: JBDS-4076 > URL: https://issues.jboss.org/browse/JBDS-4076 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Bug > Components: build, rpm > Reporter: Václav Kadlčík > Assignee: Nick Boldt > Fix For: 10.2.0.AM2 > > > This is an issue with upcoming rh-eclipse46-devstudio.rpm. > Sometimes there's a mismatch in the "RPM release" between a built RPM and its src.rpm. For example https://devstudio.jboss.com/10.0/snapshots/builds/devstudio.rpm_master/20... contains: > rh-eclipse46-devstudio-10.2-0.20161004.0056.el7.src.rpm > rh-eclipse46-devstudio-10.2-0.20161004.0057.el7.x86_64.rpm > The RPM release part is "0.20161004.0057.el7"; looks constructed using the date and time of building. The time bits are different between the two files. > The SOURCERPM info in the RPM is broken as well: > {{$ rpm -q --qf='%{SOURCERPM}\n' -p rh-eclipse46-devstudio-10.2-0.20161004.0057.el7.x86_64.rpm > rh-eclipse46-devstudio-10.2-0.20161004.0057.el7.src.rpm > }} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23302) https no longer working on tools.jboss.org

by Marcel Bruch (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23302?page=com.atlassian.jira.plugi... ] Marcel Bruch commented on JBIDE-23302: -------------------------------------- Max, we did not make any changes so far. Nick, my best guess is that the discovery URL you (s/o at JBoss Tools) put into aeri's plugin.xml extension uses that url. I remember Max told me some time ago that he set up a redirect from "somewhere" to redhat.ctrflow.com because he did not want to use the ctrlflow url directly in the plugin.xml. If so, that's something we are not involved in. Alexey, for timely responses please send future support requests directly to support(a)ctrlflow.com, use the in-app chat, the support form, or call our support team directly. Due to your requested changes, I'm not able to keep up monitoring jbosstools-dev or JIRA on a regular basis. Thanks. > https no longer working on tools.jboss.org > ------------------------------------------ > > Key: JBIDE-23302 > URL: https://issues.jboss.org/browse/JBIDE-23302 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: aeri, website > Reporter: Nick Boldt > Fix For: 4.4.2.AM2 > > > Is it expected that tools.jboss.org no longer provides https? > https keeps redirecting to http for me, so I'm getting errors in Eclipse as thrown by AERI, eg: > {code}Server 'org.jboss.tools' failed with exception: Connect to tools.jboss.org:443 [tools.jboss.org/10.4.129.28] failed: connect timed out. ; version: 2.0.1.201608030901 > {code} > To see this in action, go here: > https://tools.jboss.org --> redirects to http://tools.jboss.org > or, go here: > https://tools.jboss.org:443/ --> redirects to http://tools.jboss.org > I bet this is a problem for eng-ops@ or the new PnT portal. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23210) Application wizard: builder image application are created all the time for first project

by Marián Labuda (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23210?page=com.atlassian.jira.plugi... ] Marián Labuda closed JBIDE-23210. --------------------------------- Verified in DevStudio 10.2.0.AM2 build ID AM2-v20161005-2259-B6159 > Application wizard: builder image application are created all the time for first project > ---------------------------------------------------------------------------------------- > > Key: JBIDE-23210 > URL: https://issues.jboss.org/browse/JBIDE-23210 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.4.1.Final > Environment: # openshift version > openshift v3.2.1.15 > kubernetes v1.2.0-36-g4a3f9c5 > etcd 2.2.5 > Reporter: Peng Li > Assignee: Andre Dietisheim > Labels: application_wizard, deploy_docker_wizard, openshift_v3 > Fix For: 4.4.2.AM2 > > Attachments: Screenshot from 2016-09-22 15-58-02.png, Screenshot from 2016-09-22 16-00-12.png > > > Creation of an application based on builder image ignore preselected project and is created on first project all the time. This is happening only for builder images. Template based application are not affected by this issue. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 5 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 October 2016