September 2016 - jbosstools-issues

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

by Dmitrii Bocharov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22803?page=com.atlassian.jira.plugi... ] Dmitrii Bocharov commented on JBIDE-22803: ------------------------------------------ [~jcantrill] [~adietish] [~jeffmaury] tried to find out how to get the version of the OpenShift Origin Server, but found nothing implemented yes and it seems not-so-easy-to-solve problem. I tried watching projects with [the latest v1.3.0|https://github.com/openshift/origin/releases/tag/v1.3.0] and it works! That's great! I also tried with https://console.engint.openshift.com and the version of OS installed there doesn't support this feature (in spite of OpenShift Master: v3.2.1.15-8-gc402626). I tried to debug and what i notices is that org.jboss.tools.openshift.internal.core.WatchManager.WatchListener error method is called without stopping (because it tries to restart(); all the time). And i have an idea how solve the question of whether the feature is available or not. If we look at response variable of com.openshift.internal.restclient.okhttp.WatchClient.WatchEndpoint.onFailure(IOException, Response) then we'll see the following: Response{protocol=http/1.1, code=200, message=OK, url=https://console.engint.openshift.com/oapi/v1/projects?watch=true&} I understand that it's a dirty hack, but we can retrieve this url (by response.request().url()) and analyze the code. And, for example, if this response repeats, say, 3 times, then we understand that the feature is not available. I see how cheaty it is, but it should work > 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)

7 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBDS-4059) RPM errors: Installing rh-eclipse46-devstudio.10.1 into rh-eclipse46 beta.

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBDS-4059?page=com.atlassian.jira.plugin.... ] Nick Boldt commented on JBDS-4059: ---------------------------------- Reopened. [~vkadlcik] I've added you as a dev on the team so you can now reopen issues. > RPM errors: Installing rh-eclipse46-devstudio.10.1 into rh-eclipse46 beta. > -------------------------------------------------------------------------- > > Key: JBDS-4059 > URL: https://issues.jboss.org/browse/JBDS-4059 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Bug > Components: build > Reporter: Pavol Srna > Assignee: Nick Boldt > Fix For: 10.2.0.AM2 > > > [~vkadlcik] has run some rpm sanity tests. The findings can be seen here: http://nest.test.redhat.com/mnt/qa/scratch/bkr-hv03-guest19/2016:24366/tp... > [~nickboldt] can you please investigate? Thanks! -- This message was sent by Atlassian JIRA (v6.4.11#64026)

7 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBDS-4059) RPM errors: Installing rh-eclipse46-devstudio.10.1 into rh-eclipse46 beta.

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBDS-4059?page=com.atlassian.jira.plugin.... ] Nick Boldt edited comment on JBDS-4059 at 9/30/16 11:13 AM: ------------------------------------------------------------ Reopened. [~vkadlcik] I've added you as a dev on the team so you can now reopen JBIDE and JBDS issues. was (Author: nickboldt): Reopened. [~vkadlcik] I've added you as a dev on the team so you can now reopen issues. > RPM errors: Installing rh-eclipse46-devstudio.10.1 into rh-eclipse46 beta. > -------------------------------------------------------------------------- > > Key: JBDS-4059 > URL: https://issues.jboss.org/browse/JBDS-4059 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Bug > Components: build > Reporter: Pavol Srna > Assignee: Nick Boldt > Fix For: 10.2.0.AM2 > > > [~vkadlcik] has run some rpm sanity tests. The findings can be seen here: http://nest.test.redhat.com/mnt/qa/scratch/bkr-hv03-guest19/2016:24366/tp... > [~nickboldt] can you please investigate? Thanks! -- This message was sent by Atlassian JIRA (v6.4.11#64026)

7 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22966) create bzira fork that supports scraping RH bugzilla

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22966?page=com.atlassian.jira.plugi... ] Nick Boldt commented on JBIDE-22966: ------------------------------------ Currently there are 7 RHT BZ, but they're all resolved. So still no immediate urgency here. > create bzira fork that supports scraping RH bugzilla > ---------------------------------------------------- > > Key: JBIDE-22966 > URL: https://issues.jboss.org/browse/JBIDE-22966 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: build > Affects Versions: 4.4.1.AM3 > Reporter: Nick Boldt > Assignee: Nick Boldt > Priority: Minor > Fix For: 4.4.2.AM2 > > > Sample issue to scrape: > https://bugzilla.redhat.com/show_bug.cgi?id=1363849 > More issues: > https://bugzilla.redhat.com/buglist.cgi?component=rh-eclipse46&list_id=56... > Target method: > * look for whiteboard = RHT (then filter by date since last change, as current bzira.py [1] does) > Mappings: > * BZ Product = Red Hat Software Collections --> RHECLIPSE jira > * BZ component = rh-eclipse46 (maybe others in future, eg., eclipse-cdt, eclipse-docker) --> same component in jira (python script will generate new components automatically) > * Version = rh-eclipse46 --> "rh-eclipse46" version in JIRA > * Target Milestone --> label in JIRA > * Target Release -> label in JIRA > [1] https://github.com/maxandersen/jiralint/blob/master/bzira.py -- This message was sent by Atlassian JIRA (v6.4.11#64026)

7 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23091) use #close smart tag in task JIRA commit messages (getProjectRootPomParents.sh) so JIRAs can be closed automatically when changes are applied

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23091?page=com.atlassian.jira.plugi... ] Nick Boldt commented on JBIDE-23091: ------------------------------------ Jobs updated, ready for the next time we need them: https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/jbos... https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/jbos... > use #close smart tag in task JIRA commit messages (getProjectRootPomParents.sh) so JIRAs can be closed automatically when changes are applied > --------------------------------------------------------------------------------------------------------------------------------------------- > > Key: JBIDE-23091 > URL: https://issues.jboss.org/browse/JBIDE-23091 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: build > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 4.4.2.AM2 > > > Rather than having to create and bulk-close 17 JIRAs, we should use smart commit msgs that cause JIRA workflow to close JIRAs automatically -- This message was sent by Atlassian JIRA (v6.4.11#64026)

7 years, 7 months

1
0
0 / 0

[JBoss JIRA] (ERT-204) Docker Machine lookup does not work on Windows machines [EBZ#494305]

by Xavier Coulon (JIRA)

[ https://issues.jboss.org/browse/ERT-204?page=com.atlassian.jira.plugin.sy... ] Xavier Coulon updated ERT-204: ------------------------------ Sprint: devex #118 July 2016, devex #120 September 2016 (was: devex #118 July 2016, devex #120 September 2016, RHDEVDOCS Sprint 121, > Oct 19) > Docker Machine lookup does not work on Windows machines [EBZ#494305] > -------------------------------------------------------------------- > > Key: ERT-204 > URL: https://issues.jboss.org/browse/ERT-204 > Project: Eclipse Release Train > Issue Type: Bug > Components: Linux Tools > Reporter: Friendly Jira Robot > Assignee: Xavier Coulon > Labels: 5.0.0, Docker, bzira > Fix For: Neon (4.6) > > > When creating Docker connection, the docker-machine mechanism does not work on Window as it seems to find docker-machine and not docker-machine.exe -- This message was sent by Atlassian JIRA (v6.4.11#64026)

7 years, 7 months

1
0
0 / 0

[JBoss JIRA] (ERT-204) Docker Machine lookup does not work on Windows machines [EBZ#494305]

by Xavier Coulon (JIRA)

[ https://issues.jboss.org/browse/ERT-204?page=com.atlassian.jira.plugin.sy... ] Xavier Coulon updated ERT-204: ------------------------------ Sprint: devex #118 July 2016, devex #120 September 2016, devex #121 October 2016 (was: devex #118 July 2016, devex #120 September 2016) > Docker Machine lookup does not work on Windows machines [EBZ#494305] > -------------------------------------------------------------------- > > Key: ERT-204 > URL: https://issues.jboss.org/browse/ERT-204 > Project: Eclipse Release Train > Issue Type: Bug > Components: Linux Tools > Reporter: Friendly Jira Robot > Assignee: Xavier Coulon > Labels: 5.0.0, Docker, bzira > Fix For: Neon (4.6) > > > When creating Docker connection, the docker-machine mechanism does not work on Window as it seems to find docker-machine and not docker-machine.exe -- This message was sent by Atlassian JIRA (v6.4.11#64026)

7 years, 7 months

1
0
0 / 0

[JBoss JIRA] (ERT-204) Docker Machine lookup does not work on Windows machines [EBZ#494305]

by Xavier Coulon (JIRA)

[ https://issues.jboss.org/browse/ERT-204?page=com.atlassian.jira.plugin.sy... ] Xavier Coulon updated ERT-204: ------------------------------ Sprint: devex #118 July 2016, devex #120 September 2016, RHDEVDOCS Sprint 121, > Oct 19 (was: devex #118 July 2016, devex #120 September 2016) > Docker Machine lookup does not work on Windows machines [EBZ#494305] > -------------------------------------------------------------------- > > Key: ERT-204 > URL: https://issues.jboss.org/browse/ERT-204 > Project: Eclipse Release Train > Issue Type: Bug > Components: Linux Tools > Reporter: Friendly Jira Robot > Assignee: Xavier Coulon > Labels: 5.0.0, Docker, bzira > Fix For: Neon (4.6) > > > When creating Docker connection, the docker-machine mechanism does not work on Window as it seems to find docker-machine and not docker-machine.exe -- This message was sent by Atlassian JIRA (v6.4.11#64026)

7 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3257) Basic FeedHenry Support

by Gorkem Ercan (JIRA)

[ https://issues.jboss.org/browse/JBDS-3257?page=com.atlassian.jira.plugin.... ] Gorkem Ercan closed JBDS-3257. ------------------------------ > Basic FeedHenry Support > ----------------------- > > Key: JBDS-3257 > URL: https://issues.jboss.org/browse/JBDS-3257 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Epic > Components: aerogear-hybrid, requirements > Reporter: Max Rydahl Andersen > Assignee: Gorkem Ercan > Fix For: 9.1.0.GA > > > as feedhenry user I would like to be able to easily import my existing feedhenry application into developer studio and allow me to edit and commit code back to feedhenry. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

7 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3247) Hybrid Mobile Tooling covering base Apache Cordova

by Gorkem Ercan (JIRA)

[ https://issues.jboss.org/browse/JBDS-3247?page=com.atlassian.jira.plugin.... ] Gorkem Ercan closed JBDS-3247. ------------------------------ Resolution: Done > Hybrid Mobile Tooling covering base Apache Cordova > -------------------------------------------------- > > Key: JBDS-3247 > URL: https://issues.jboss.org/browse/JBDS-3247 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Epic > Components: aerogear-hybrid, cordovasim, requirements > Reporter: Max Rydahl Andersen > Assignee: Gorkem Ercan > Fix For: 10.x > > -- This message was sent by Atlassian JIRA (v6.4.11#64026)

7 years, 7 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jbosstools-issues September 2016