September 2016 - jbosstools-issues

[JBoss JIRA] (JBIDE-23012) move createnewandnoteworthy.py to jbosstools-build-ci or jbosstools-website and deprecate jbosstools-documentation

by Lukáš Valach (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23012?page=com.atlassian.jira.plugi... ] Lukáš Valach closed JBIDE-23012. -------------------------------- Verified on branch 4.4.x. > move createnewandnoteworthy.py to jbosstools-build-ci or jbosstools-website and deprecate jbosstools-documentation > ------------------------------------------------------------------------------------------------------------------ > > Key: JBIDE-23012 > URL: https://issues.jboss.org/browse/JBIDE-23012 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build > Affects Versions: 4.4.1.AM3 > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 4.4.1.Final > > > Since July 2014, the only file that's been changed in the jbosstools-documentation repo is ... > https://github.com/jbosstools/jbosstools-documentation/blob/master/whatsn... > In fact, the last time the repo was tagged was for JBoss Tools 4.1.0.Final -- 3 years ago. > So... since docs are now on access.redhat.com and N&N are on tools.jboss.org (in jbosstools-website), maybe it's time to terminate this project and move the ONE active file into another project? > Could move it to jbosstools-webite, where all the N&N stuff lives, or we could move it to jbosstools-build-ci, where all the other python/jira scripts live. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBDS-4045) Createnewandnoteworthy.py are not mentioned in project readme

by Lukáš Valach (JIRA)

Lukáš Valach created JBDS-4045: ---------------------------------- Summary: Createnewandnoteworthy.py are not mentioned in project readme Key: JBDS-4045 URL: https://issues.jboss.org/browse/JBDS-4045 Project: Red Hat JBoss Developer Studio (devstudio) Issue Type: Bug Components: build Affects Versions: 4.4 Reporter: Lukáš Valach Assignee: Nick Boldt Priority: Minor The script *createnewandnoteworthy.py* has been copied to *jbosstools-build-ci* project on Git Hub ([JBIDE-23012|https://issues.jboss.org/browse/JBIDE-23012]), but isn't mentioned in readme file as another scripts. Please add same descripton to [readme.adoc|https://github.com/jbosstools/jbosstools-build-ci/blob/jbosst...]. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20405) Connection wizard: Improve the error message resulting from trying to create new OpenShift v3 application when launching wizard from Central

by Jeff MAURY (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20405?page=com.atlassian.jira.plugi... ] Jeff MAURY commented on JBIDE-20405: ------------------------------------ Can't reproduce with 4.4.1. Should we close it ? > Connection wizard: Improve the error message resulting from trying to create new OpenShift v3 application when launching wizard from Central > -------------------------------------------------------------------------------------------------------------------------------------------- > > Key: JBIDE-20405 > URL: https://issues.jboss.org/browse/JBIDE-20405 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.3.0.Beta2 > Reporter: Len DiMaggio > Priority: Minor > Labels: connection_wizard, help_wanted, openshift_v3 > Fix For: 4.4.x > > Attachments: Screenshot-4.png, Screenshot-5.png > > Original Estimate: 2 hours > Remaining Estimate: 2 hours > > See attached screenshots - can we provide a more descriptive, and better formatted, error message? Thx! -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20045) Software/Update page looks bad in Dark mode

by Jeff MAURY (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20045?page=com.atlassian.jira.plugi... ] Jeff MAURY commented on JBIDE-20045: ------------------------------------ it look weirder on Windows see [^windowws-screenshot.png] > Software/Update page looks bad in Dark mode > ------------------------------------------- > > Key: JBIDE-20045 > URL: https://issues.jboss.org/browse/JBIDE-20045 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: central > Affects Versions: 4.3.0.Beta1 > Reporter: Fred Bricon > Assignee: Snjezana Peco > Priority: Minor > Fix For: 4.3.x > > Attachments: central.png, windowws-screenshot.png > > > - Enable Eclipse Dark Theme in Preferences > Appearance, > - Open Central, click on the Software Update page > - Make sure Early Access is enabled > - Check this : > !http://content.screencast.com/users/fbricon/folders/Jing/media/679d7466-cba0-42b8-aaf0-8d6b2f35691a/00000113.png! > - grey areas around the checkboxes and the titles > - blue links don't look good > - Early-Access items are not highlighted (even after fixing JBIDE-20007) -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20045) Software/Update page looks bad in Dark mode

by Jeff MAURY (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20045?page=com.atlassian.jira.plugi... ] Jeff MAURY updated JBIDE-20045: ------------------------------- Attachment: windowws-screenshot.png > Software/Update page looks bad in Dark mode > ------------------------------------------- > > Key: JBIDE-20045 > URL: https://issues.jboss.org/browse/JBIDE-20045 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: central > Affects Versions: 4.3.0.Beta1 > Reporter: Fred Bricon > Assignee: Snjezana Peco > Priority: Minor > Fix For: 4.3.x > > Attachments: central.png, windowws-screenshot.png > > > - Enable Eclipse Dark Theme in Preferences > Appearance, > - Open Central, click on the Software Update page > - Make sure Early Access is enabled > - Check this : > !http://content.screencast.com/users/fbricon/folders/Jing/media/679d7466-cba0-42b8-aaf0-8d6b2f35691a/00000113.png! > - grey areas around the checkboxes and the titles > - blue links don't look good > - Early-Access items are not highlighted (even after fixing JBIDE-20007) -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22969) Make sure OpenShift Tools support proxies

by Dmitrii Bocharov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22969?page=com.atlassian.jira.plugi... ] Dmitrii Bocharov updated JBIDE-22969: ------------------------------------- Sprint: devex #120 September 2016 (was: devex #119 August 2016) > Make sure OpenShift Tools support proxies > ----------------------------------------- > > Key: JBIDE-22969 > URL: https://issues.jboss.org/browse/JBIDE-22969 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: openshift > Reporter: Alexey Kazakov > Assignee: Dmitrii Bocharov > Fix For: 4.4.2.AM1 > > Attachments: proxy_settings.png > > > CDK is now support proxy servers. We also should make sure OpenShift Tools works fine with proxies too. > If devstudio and cdk are installed using DevSuite installer and user configured proxy server correctly then everything should just work on Eclipse side. > This issue covers: > - testing > - creating all needed (currently missing) automated tests (including reddeer/swt bot Integration Tests) > - fixing any problems we have in OpenShift tooling regarding proxy support. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 7 months

1
0
0 / 0

[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 updated JBIDE-22803: ------------------------------------- Sprint: devex #120 September 2016 (was: devex #119 August 2016) > 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.1.Final > > 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, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22727) Openshift resources managed by explorer and watcher are declared in both place leading to inconsistency

by Dmitrii Bocharov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22727?page=com.atlassian.jira.plugi... ] Dmitrii Bocharov updated JBIDE-22727: ------------------------------------- Sprint: devex #120 September 2016 (was: devex #119 August 2016) > Openshift resources managed by explorer and watcher are declared in both place leading to inconsistency > ------------------------------------------------------------------------------------------------------- > > Key: JBIDE-22727 > URL: https://issues.jboss.org/browse/JBIDE-22727 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.4.1.AM1 > Reporter: Jeff MAURY > Assignee: Dmitrii Bocharov > Labels: explorer, openshift, openshift_v3 > Fix For: 4.4.x > > > The kind of Openshift resources are declated in 2 different places: WatchManager and ConnectionWrapper. This increases the technical debt and may lead to resources displayed by the explorer but not refreshed by the watcher. > The task requires investigation about ResourceKind.IMAGE_STREAM_TAG, which is present in ConnectionWrapper, but there is no such element in WatchManager's array. See discussion [here|https://github.com/jbosstools/jbosstools-openshift/pull/1272#discuss...] -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22994) Remove old Help->Report Problem dialog

by Dmitrii Bocharov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22994?page=com.atlassian.jira.plugi... ] Dmitrii Bocharov updated JBIDE-22994: ------------------------------------- Sprint: devex #120 September 2016 (was: devex #119 August 2016) > Remove old Help->Report Problem dialog > -------------------------------------- > > Key: JBIDE-22994 > URL: https://issues.jboss.org/browse/JBIDE-22994 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: aeri, common/jst/core > Reporter: Denis Golovin > Assignee: Dmitrii Bocharov > Labels: new_and_noteworthy > Fix For: 4.4.1.Final > > Attachments: screenshot-1.png > > > Should we deprecate delete old Report Problem dialog with aeri enabled? -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22725) Provided wrong credentials, CDK adapter creates openshift connection with a strange IP

by Martin Malina (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22725?page=com.atlassian.jira.plugi... ] Martin Malina commented on JBIDE-22725: --------------------------------------- I can still reproduce it. But for that I needed to do a vagrant destroy first. When I had an existing box that was previously registered, starting without registering still resulted in correct output of service manager. But when I then did "vagrant destroy" and started again, it failed, i.e. vagrant service-manager env returned this: {code} $ vagrant service-manager env # docker env: # Copying TLS certificates to /Users/rasp/jbossqa/cdk2.2.rc3/cdk/components/rhel/rhel-ose/.vagrant/machines/default/virtualbox/docker # Set the following environment variables to enable access to the # docker daemon running inside of the vagrant virtual machine: export DOCKER_HOST=tcp://10.0.2.15:2376 export DOCKER_CERT_PATH=/Users/rasp/jbossqa/cdk2.2.rc3/cdk/components/rhel/rhel-ose/.vagrant/machines/default/virtualbox/docker export DOCKER_TLS_VERIFY=1 export DOCKER_API_VERSION=1.22 # run following command to configure your shell: # eval "$(vagrant service-manager env)" {code} [~jeffmaury], can you try to do "vagrant destroy" first and then set wrong credentials using SUB_USERNAME and SUB_PASSWORD and then vagrant up. > Provided wrong credentials, CDK adapter creates openshift connection with a strange IP > -------------------------------------------------------------------------------------- > > Key: JBIDE-22725 > URL: https://issues.jboss.org/browse/JBIDE-22725 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: cdk, upstream > Affects Versions: 4.4.1.AM1 > Reporter: Martin Malina > Fix For: 4.4.x > > > When you start CDK with wrong credentials, service manager will return this strange IP: > {code} > # docker env: > # Copying TLS certificates to /Users/rasp/jbossqa/cdk2.1/cdk2.1.rc5/components/rhel/misc/shared_folder/rhel-ose/.vagrant/machines/default/virtualbox/docker > # Set the following environment variables to enable access to the docker daemon running inside of the vagrant virtual machine: > export DOCKER_HOST=tcp://10.0.2.15:2376 > export DOCKER_CERT_PATH=/Users/rasp/jbossqa/cdk2.1/cdk2.1.rc5/components/rhel/misc/shared_folder/rhel-ose/.vagrant/machines/default/virtualbox/docker > export DOCKER_TLS_VERIFY=1 > export DOCKER_API_VERSION=1.21 > # run following command to configure your shell: > # eval "$(vagrant service-manager env)" > {code} > This has been reported upstream here: > https://github.com/projectatomic/vagrant-service-manager/issues/299 > Let's use this JIRA to track the upstream issue. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 7 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