October 2016 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-23350) Deploy Docker Wizard: Prompt to enter credentials contains Finish button

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23350?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-23350: ------------------------------------- Priority: Minor (was: Major) > Deploy Docker Wizard: Prompt to enter credentials contains Finish button > ------------------------------------------------------------------------ > > Key: JBIDE-23350 > URL: https://issues.jboss.org/browse/JBIDE-23350 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: cdk, openshift > Affects Versions: 4.4.2.AM2 > Reporter: Marián Labuda > Priority: Minor > Labels: deploy_docker_wizard, openshift_v3 > Fix For: 4.4.x > > > When opening Deploy Image to OpenShift wizard from context menu of a docker image and there was no OpenShift connection selected, OpenShift connection wizard is shown with Finish button, although connection is active (connected). There should be opened the Deploy Image to OpenShift with the connection wizard page and it should have next button. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23350) Deploy Docker Wizard: Prompt to enter credentials contains Finish button

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23350?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-23350: ------------------------------------- Fix Version/s: 4.4.x > Deploy Docker Wizard: Prompt to enter credentials contains Finish button > ------------------------------------------------------------------------ > > Key: JBIDE-23350 > URL: https://issues.jboss.org/browse/JBIDE-23350 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: cdk, openshift > Affects Versions: 4.4.2.AM2 > Reporter: Marián Labuda > Priority: Minor > Labels: deploy_docker_wizard, openshift_v3 > Fix For: 4.4.x > > > When opening Deploy Image to OpenShift wizard from context menu of a docker image and there was no OpenShift connection selected, OpenShift connection wizard is shown with Finish button, although connection is active (connected). There should be opened the Deploy Image to OpenShift with the connection wizard page and it should have next button. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23315) Connection wizard: "Advanced >>" Button is cropped

by Aurélien Pupier (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23315?page=com.atlassian.jira.plugi... ] Aurélien Pupier commented on JBIDE-23315: ----------------------------------------- [~adietish]I'm on Windows 10, so not using GTK 3 > Connection wizard: "Advanced >>" Button is cropped > -------------------------------------------------- > > Key: JBIDE-23315 > URL: https://issues.jboss.org/browse/JBIDE-23315 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.4.1.Final > Reporter: Aurélien Pupier > Priority: Minor > Labels: connection_wizard > Fix For: 4.4.x > > Attachments: 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-23315) Connection wizard: "Advanced >>" Button is cropped

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23315?page=com.atlassian.jira.plugi... ] Andre Dietisheim commented on JBIDE-23315: ------------------------------------------ [~jeffmaury] I cant currently (but I know that i also saw it before), but if you see this too, then it's definitely not GTK3. A wizard/dialog would normally expand so that it fits all controls. The key question then is why this isnt fully working in this case. > Connection wizard: "Advanced >>" Button is cropped > -------------------------------------------------- > > Key: JBIDE-23315 > URL: https://issues.jboss.org/browse/JBIDE-23315 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.4.1.Final > Reporter: Aurélien Pupier > Priority: Minor > Labels: connection_wizard > Fix For: 4.4.x > > Attachments: 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-23351) Deploy Docker Wizard: Image stream sometimes is not created for local docker images

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23351?page=com.atlassian.jira.plugi... ] Andre Dietisheim commented on JBIDE-23351: ------------------------------------------ [~mlabuda] I understand, but without instructions on how to replicate this it's rather hard to find out what exactly is happening here and why it fails. It never happens to me with aloha, I thus cannot replicate it currently. Can you please record your steps when this happens to you the next time? > Deploy Docker Wizard: Image stream sometimes is not created for local docker images > ----------------------------------------------------------------------------------- > > Key: JBIDE-23351 > URL: https://issues.jboss.org/browse/JBIDE-23351 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.4.2.AM2 > Reporter: Marián Labuda > Labels: deploy_docker_wizard, openshift_v3 > Attachments: is_not_created.png > > > When deploying a local image to OpenShift, Image stream is not created even an image has been pushed to registry. For images on docker hub it works ok. > Following message is shown in resource summary: > !is_not_created.png! > I had checked the checkbox to push to registry. But I am not able to reproduce this all the time. I was able to do it only 2 times. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (ERT-437) Config.xml is not saved after "Create Hybrid Mobile Application" wizard finished [EBZ#506123]

by Friendly Jira Robot (JIRA)

Friendly Jira Robot created ERT-437: --------------------------------------- Summary: Config.xml is not saved after "Create Hybrid Mobile Application" wizard finished [EBZ#506123] Key: ERT-437 URL: https://issues.jboss.org/browse/ERT-437 Project: Eclipse Release Train Issue Type: Task Components: Thym Reporter: Friendly Jira Robot Fix For: Neon (4.6) Created attachment 264908 screenshot.png -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBDS-4077) Cannot run integration tests against Devstudio with latest target platform

by Rastislav Wagner (JIRA)

[ https://issues.jboss.org/browse/JBDS-4077?page=com.atlassian.jira.plugin.... ] Rastislav Wagner edited comment on JBDS-4077 at 10/18/16 4:08 AM: ------------------------------------------------------------------ [~nickboldt] I've setup 3 jobs to run deltaspike integration tests against preinstalled devstudio 1. master deltaspike tests with devstudio 10.1.0.GA https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/Develop... 2. master deltaspike tests with devstudio 10.2.0.AM1 https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/Develop... 3. master deltaspike tests with devstudio 10.2.0.AM2 https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/Develop... So the only thing that is different between these jobs is version of devstudio. First two pass (1 failure is expected), third one fails completely. We can also take a look at how devstudio looks like in these 3 jobs: 1. job https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/Develop... 2. job https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/Develop... 3. job https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/Develop... So 1. and 2. looks normal - just like devstudio, 3. looks like eclipse (see title - Java EE, not Devstudio, also no central tool item etc.) Eclipse log from 3. job - https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/Develop... - especially {code} !ENTRY org.eclipse.equinox.app 0 0 2016-10-18 03:32:07.216 !MESSAGE Product com.jboss.devstudio.core.product could not be found {code} It does not look like problem is in our tests/pom.xml :/ was (Author: rawagner): [~nickboldt] I've setup 3 jobs to run deltaspike integration tests against preinstalled devstudio 1. master deltaspike tests with devstudio 10.1.0.GA https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/Develop... 2. master deltaspike tests with devstudio 10.2.0.AM1 https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/Develop... 3. master deltaspike tests with devstudio 10.2.0.AM2 https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/Develop... So the only thing that is different between these jobs is version of devstudio. First two pass (1 failure is expected), third one fails completely. We can also take a look at how devstudio looks like in these 3 jobs: 1. job https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/Develop... 2. job https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/Develop... 3. job https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/Develop... So 1. and 2. looks normal - just like devstudio, 3. looks like eclipse (see title - Java EE, not Devstudio, also no central tool item etc.) It does not look like problem is in our tests/pom.xml :/ > Cannot run integration tests against Devstudio with latest target platform > -------------------------------------------------------------------------- > > Key: JBDS-4077 > URL: https://issues.jboss.org/browse/JBDS-4077 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Bug > Components: build, target-platform > Affects Versions: 10.2.0.AM1 > Reporter: Jan Richter > Assignee: Marián Labuda > Priority: Blocker > Fix For: 10.2.0.AM3 > > Attachments: .log, jbosstools-integration-tests.log.txt.zip, no_devstudio.jpg, no_devstudio.png, org.jboss.tools.deltaspike.ui.bot.test.DeltaspikeAllBotTests.txt, org.jboss.tools.deltaspike.ui.bot.test.log.txt, org.jboss.tools.deltaspike.ui.bot.test.log_0.txt, Screenshot_2016-10-05_10-00-03.png, Screenshot_2016-10-05_10-00-21.png, Screenshot_2016-10-05_10-00-28.png, Screenshot_2016-10-05_10-00-57.png, Screenshot_2016-10-05_10-01-14.png, Screenshot_2016-10-05_10-01-32.png, shell.png, TEST-org.jboss.tools.deltaspike.ui.bot.test.DeltaspikeAllBotTests.xml, tpfail.png > > > Integration tests run from maven against Devstudio, which was built using the latest target platform (4.61.0.AM1-SNAPSHOT), cannot properly launch all the plugins and fail afterwards. > A full devstudio should open when the tests are run. Instead it looks like this: > !tpfail.png|thumbnail! -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22229) Tooling to check if patches/PRs are applied across both master and maintenance

by Lukáš Valach (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22229?page=com.atlassian.jira.plugi... ] Lukáš Valach closed JBIDE-22229. -------------------------------- Verified in git. > Tooling to check if patches/PRs are applied across both master and maintenance > ------------------------------------------------------------------------------ > > Key: JBIDE-22229 > URL: https://issues.jboss.org/browse/JBIDE-22229 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: build > Affects Versions: 4.3.1.Final > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 4.4.2.AM2 > > > 1. review and push https://github.com/jbosstools/jbosstools-build-ci/pull/143 > 2. migrate scripts in jbdevstudio-ci that also use python to generate JIRAs to the same repo > 3. externalize shared JIRA component mapping table so both scripts can use it -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22229) Tooling to check if patches/PRs are applied across both master and maintenance

by Lukáš Valach (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22229?page=com.atlassian.jira.plugi... ] Lukáš Valach updated JBIDE-22229: --------------------------------- Sprint: devex #115 May 2016, devex #117 July 2016 (was: devex #115 May 2016, devex #117 July 2016, devex #122 October 2016) > Tooling to check if patches/PRs are applied across both master and maintenance > ------------------------------------------------------------------------------ > > Key: JBIDE-22229 > URL: https://issues.jboss.org/browse/JBIDE-22229 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: build > Affects Versions: 4.3.1.Final > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 4.4.2.AM2 > > > 1. review and push https://github.com/jbosstools/jbosstools-build-ci/pull/143 > 2. migrate scripts in jbdevstudio-ci that also use python to generate JIRAs to the same repo > 3. externalize shared JIRA component mapping table so both scripts can use it -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBDS-4054) publish rpms + metadata to /latest/ locations so they can be easily installed by QE

by Lukáš Valach (JIRA)

[ https://issues.jboss.org/browse/JBDS-4054?page=com.atlassian.jira.plugin.... ] Lukáš Valach closed JBDS-4054. ------------------------------ Verified in 10.2.0.AM2 > publish rpms + metadata to /latest/ locations so they can be easily installed by QE > ----------------------------------------------------------------------------------- > > Key: JBDS-4054 > URL: https://issues.jboss.org/browse/JBDS-4054 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Task > Components: build, rpm > Affects Versions: 10.1.0.GA, 10.2.0.AM1 > Reporter: Nick Boldt > Assignee: Nick Boldt > Labels: doc_writer_needed, docs_installation_guide, new_and_noteworthy > Fix For: 10.2.0.AM2 > > Attachments: rh-eclipse46-devstudio.repo > > > Next step is publishing these yum repos (metadata + rpms) to a location that can be made easily available to RHEL users, eg., > * https://devstudio.redhat.com/10.0/snapshots/builds/devstudio.rpm_master/l... > * https://devstudio.redhat.com/10.0/snapshots/rpms/10.2.0/x86_64/ > And, we have an empty placeholder site for the eventual release: > * https://devstudio.redhat.com/static/10.0/stable/rpms/x86_64/ -- 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