September 2017 - jbosstools-issues

[JBoss JIRA] (JBIDE-24986) Application wizard: template is deselected when returning to template selection

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24986?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-24986: ------------------------------------- Fix Version/s: 4.5.x > Application wizard: template is deselected when returning to template selection > ------------------------------------------------------------------------------- > > Key: JBIDE-24986 > URL: https://issues.jboss.org/browse/JBIDE-24986 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.5.1.AM2 > Environment: Red Hat JBoss Developer Studio > Version: 11.1.0.AM2 > Build id: AM2-v20170905-0703-B967 > Build date: 20170905-0703 > Reporter: Josef Kopriva > Labels: application_wizard, openshift_v3 > Fix For: 4.5.x > > > Template should be selected even after the user clicks on Back button to select templates. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBDS-4537) Ensure Datatools and WTP-JPT (Dali) are available in DevTools (rh-eclipse47) so downstream rh-eclipse47-devstudio can use it

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBDS-4537?page=com.atlassian.jira.plugin.... ] Nick Boldt commented on JBDS-4537: ---------------------------------- Yep, GMTA. I should learn to hit enter on JIRA comments AFTER the first cup of coffee is consumed, not during its consumption. :D Thanks for the detailed response, nonetheless. So... for this issue, what's the process for moving from Koji / Fedora / eclipse-\* to Brew / DevTools / rh-eclipse47-\* ? Assuming it's... a) open a RH BZ b) do something with rhpkg? c) check Brew d) profit! > Ensure Datatools and WTP-JPT (Dali) are available in DevTools (rh-eclipse47) so downstream rh-eclipse47-devstudio can use it > ---------------------------------------------------------------------------------------------------------------------------- > > Key: JBDS-4537 > URL: https://issues.jboss.org/browse/JBDS-4537 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Sub-task > Components: rpm, upstream > Affects Versions: 11.1.0.AM1 > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 11.x > > > Mat says that Eclipse DTP and WTP-JPT are already in Fedora. > So we need to ensure Datatools and WTP-JPT (Dali) are ALSO available in DevTools (rh-eclipse47); then downstream rh-eclipse47-devstudio can use it -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24985) Test test_pull_from_insecure_repository is failing

by Josef Kopriva (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24985?page=com.atlassian.jira.plugi... ] Josef Kopriva updated JBIDE-24985: ---------------------------------- Component/s: integration-tests (was: docker) > Test test_pull_from_insecure_repository is failing > -------------------------------------------------- > > Key: JBIDE-24985 > URL: https://issues.jboss.org/browse/JBIDE-24985 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: integration-tests > Affects Versions: 4.5.1.AM2 > Reporter: Lukáš Valach > Assignee: Lukáš Valach > Fix For: 4.5.1.AM2 > > > The test test_pull_from_insecure_repository is failing with this output: > {console} > [branch_rhel7-x64-jbds-releng-lvalach] docker: > [branch_rhel7-x64-jbds-releng-lvalach] test_docker_installed_and_running > [branch_rhel7-x64-jbds-releng-lvalach] test_fetch_and_run_remote_image > [branch_rhel7-x64-jbds-releng-lvalach] Unable to find image 'debian:latest' locally > [branch_rhel7-x64-jbds-releng-lvalach] Trying to pull repository registry.access.redhat.com/debian ... > [branch_rhel7-x64-jbds-releng-lvalach] Trying to pull repository docker.io/library/debian ... > [branch_rhel7-x64-jbds-releng-lvalach] sha256:6ccbcbf362dbc4add74711cb774751b59cdfd7aed16c3c29aaecbea871952fe0: Pulling from docker.io/library/debian > [branch_rhel7-x64-jbds-releng-lvalach] 06b22ddb1913: Pulling fs layer > [branch_rhel7-x64-jbds-releng-lvalach] 06b22ddb1913: Verifying Checksum > [branch_rhel7-x64-jbds-releng-lvalach] 06b22ddb1913: Download complete > [branch_rhel7-x64-jbds-releng-lvalach] 06b22ddb1913: Pull complete > [branch_rhel7-x64-jbds-releng-lvalach] Digest: sha256:6ccbcbf362dbc4add74711cb774751b59cdfd7aed16c3c29aaecbea871952fe0 > [branch_rhel7-x64-jbds-releng-lvalach] Status: Downloaded newer image for docker.io/debian:latest > [branch_rhel7-x64-jbds-releng-lvalach] test_pull_from_insecure_repository > [branch_rhel7-x64-jbds-releng-lvalach] Trying to pull repository ce-registry.usersys.redhat.com/jboss-eap-6/eap64 ... > [branch_rhel7-x64-jbds-releng-lvalach] Pulling repository ce-registry.usersys.redhat.com/jboss-eap-6/eap64 > [branch_rhel7-x64-jbds-releng-lvalach] invalid character '<' looking for beginning of value > [branch_rhel7-x64-jbds-releng-lvalach] ASSERT:docker should be able to pull from insecure repositories > [branch_rhel7-x64-jbds-releng-lvalach] test_daemon_uses_default_tcp_port > [branch_rhel7-x64-jbds-releng-lvalach] test_talk_to_the_outer_world > [branch_rhel7-x64-jbds-releng-lvalach] > [branch_rhel7-x64-jbds-releng-lvalach] Ran 5 tests. > [branch_rhel7-x64-jbds-releng-lvalach] > [branch_rhel7-x64-jbds-releng-lvalach] FAILED (failures=1) > {console} > Whole log: > https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/job/update-s... > We probably need to update a repository URL. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24986) Application wizard: template is deselected when returning to template selection

by Josef Kopriva (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24986?page=com.atlassian.jira.plugi... ] Josef Kopriva updated JBIDE-24986: ---------------------------------- Labels: application_wizard (was: ) > Application wizard: template is deselected when returning to template selection > ------------------------------------------------------------------------------- > > Key: JBIDE-24986 > URL: https://issues.jboss.org/browse/JBIDE-24986 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.5.1.AM2 > Environment: Red Hat JBoss Developer Studio > Version: 11.1.0.AM2 > Build id: AM2-v20170905-0703-B967 > Build date: 20170905-0703 > Reporter: Josef Kopriva > Labels: application_wizard > > Template should be selected even after the user clicks on Back button to select templates. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24986) Application wizard: template is deselected when returning to template selection

by Josef Kopriva (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24986?page=com.atlassian.jira.plugi... ] Josef Kopriva updated JBIDE-24986: ---------------------------------- Steps to Reproduce: 0. Have connection to OpenShift instance and create OpenShift project 1. (In OpenShift Explorer) Right click on project and select *New* -> *Application* 2. Select any template in *New OpenShift Application* wizard 3. Click on *Next* button 4. Click on *Back* button 5. Template is deselected, but it should be selected was: 0. Have connection to OpenShift instance and create OpenShift project 1. (In OpenShift Explorer) Right click on project and select *New* -> *Application* 2. Select any template in *New OpenShift Application* wizard 3. Click on *Next * button 4. Click on *Back* button 5. Template is deselected, but it should be selected > Application wizard: template is deselected when returning to template selection > ------------------------------------------------------------------------------- > > Key: JBIDE-24986 > URL: https://issues.jboss.org/browse/JBIDE-24986 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.5.1.AM2 > Environment: Red Hat JBoss Developer Studio > Version: 11.1.0.AM2 > Build id: AM2-v20170905-0703-B967 > Build date: 20170905-0703 > Reporter: Josef Kopriva > > Template should be selected even after the user clicks on Back button to select templates. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBDS-4537) Ensure Datatools and WTP-JPT (Dali) are available in DevTools (rh-eclipse47) so downstream rh-eclipse47-devstudio can use it

by Mat Booth (JIRA)

[ https://issues.jboss.org/browse/JBDS-4537?page=com.atlassian.jira.plugin.... ] Mat Booth edited comment on JBDS-4537 at 9/5/17 10:43 AM: ---------------------------------------------------------- Oof, open can of terminology worms incoming.... :-) It's because in koji "package" is a bit closer in meaning to "specfile+source" so here you are searching what effectively the list of source RPMs (build input) rather than the list of resulting binary RPMs (build output). The relationship between source and binary RPMs can be 1 to many. In the simplest case, the resulting binary RPM implicitly has the same name as the source RPM. You may also have additional declarations in the spec file defining additional binary RPMs with different names -- it's a good way to separately package logically discrete or optional features of a software using a single specfile. I am aware that I am using "package" to describe a binary RPM named for its source RPM and "sub-package" to describe binary RPMs that are named differently to the source RPM. Sorry about that -- overloaded terminology strikes again! Really, all binary RPMs are equal in the eyes of the gods, and you can only not install it by itself in the normal sense that it may have dependencies on other RPMs. Does that make sense? Edit: Looks like you figured it while I was typing :-) was (Author: mat.booth): Oof, open can of terminology worms incoming.... :-) It's because in koji "package" is a bit closer in meaning to "specfile+source" so here you are searching what effectively the list of source RPMs (build input) rather than the list of resulting binary RPMs (build output). The relationship between source and binary RPMs can be 1 to many. In the simplest case, the resulting binary RPM implicitly has the same name as the source RPM. You may also have additional declarations in the spec file defining additional binary RPMs with different names -- it's a good way to separately package logically discrete or optional features of a software using a single specfile. I am aware that I am using "package" to describe a binary RPM named for its source RPM and "sub-package" to describe binary RPMs that are named differently to the source RPM. Sorry about that -- overloaded terminology strikes again! Really, all binary RPMs are equal in the eyes of the gods, and you can only not install it by itself in the normal sense that it may have dependencies on other RPMs. Does that make sense? > Ensure Datatools and WTP-JPT (Dali) are available in DevTools (rh-eclipse47) so downstream rh-eclipse47-devstudio can use it > ---------------------------------------------------------------------------------------------------------------------------- > > Key: JBDS-4537 > URL: https://issues.jboss.org/browse/JBDS-4537 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Sub-task > Components: rpm, upstream > Affects Versions: 11.1.0.AM1 > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 11.x > > > Mat says that Eclipse DTP and WTP-JPT are already in Fedora. > So we need to ensure Datatools and WTP-JPT (Dali) are ALSO available in DevTools (rh-eclipse47); then downstream rh-eclipse47-devstudio can use it -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24986) Application wizard: template is deselected when returning to template selection

by Josef Kopriva (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24986?page=com.atlassian.jira.plugi... ] Josef Kopriva updated JBIDE-24986: ---------------------------------- Steps to Reproduce: 0. Have connection to OpenShift instance and create OpenShift project 1. (In OpenShift Explorer) Right click on project and select *New* -> *Application* 2. Select any template in *New OpenShift Application* wizard 3. Click on *Next * button 4. Click on *Back* button 5. Template is deselected, but it should be selected was: 0. Create project 1. (In OpenShift Explorer) Right click on project and select *New* -> *Application* 2. Select any template in *New OpenShift Application* wizard 3. Click on *Next * button 4. Click on *Back* button 5. Template is deselected, but it should be selected > Application wizard: template is deselected when returning to template selection > ------------------------------------------------------------------------------- > > Key: JBIDE-24986 > URL: https://issues.jboss.org/browse/JBIDE-24986 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.5.1.AM2 > Environment: Red Hat JBoss Developer Studio > Version: 11.1.0.AM2 > Build id: AM2-v20170905-0703-B967 > Build date: 20170905-0703 > Reporter: Josef Kopriva > > Template should be selected even after the user clicks on Back button to select templates. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24986) Application wizard: template is deselected when returning to template selection

by Josef Kopriva (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24986?page=com.atlassian.jira.plugi... ] Josef Kopriva updated JBIDE-24986: ---------------------------------- Steps to Reproduce: 0. Create project 1. (In OpenShift Explorer) Right click on project and select *New* -> *Application* 2. Select any template in *New OpenShift Application* wizard 3. Click on *Next * button 4. Click on *Back* button 5. Template is deselected, but it should be selected was: 0. Create project 1. Right click on project and select *New* -> *Application* 2. Select any template in *New OpenShift Application* wizard 3. Click on *Next * button 4. Click on *Back* button 5. Template is deselected, but it should be selected > Application wizard: template is deselected when returning to template selection > ------------------------------------------------------------------------------- > > Key: JBIDE-24986 > URL: https://issues.jboss.org/browse/JBIDE-24986 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.5.1.AM2 > Environment: Red Hat JBoss Developer Studio > Version: 11.1.0.AM2 > Build id: AM2-v20170905-0703-B967 > Build date: 20170905-0703 > Reporter: Josef Kopriva > > Template should be selected even after the user clicks on Back button to select templates. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24986) Application wizard: template is deselected when returning to template selection

by Josef Kopriva (JIRA)

Josef Kopriva created JBIDE-24986: ------------------------------------- Summary: Application wizard: template is deselected when returning to template selection Key: JBIDE-24986 URL: https://issues.jboss.org/browse/JBIDE-24986 Project: Tools (JBoss Tools) Issue Type: Bug Components: openshift Affects Versions: 4.5.1.AM2 Environment: Red Hat JBoss Developer Studio Version: 11.1.0.AM2 Build id: AM2-v20170905-0703-B967 Build date: 20170905-0703 Reporter: Josef Kopriva Template should be selected even after the user clicks on Back button to select templates. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBDS-4537) Ensure Datatools and WTP-JPT (Dali) are available in DevTools (rh-eclipse47) so downstream rh-eclipse47-devstudio can use it

by Mat Booth (JIRA)

[ https://issues.jboss.org/browse/JBDS-4537?page=com.atlassian.jira.plugin.... ] Mat Booth commented on JBDS-4537: --------------------------------- Oof, open can of terminology worms incoming.... :-) It's because in koji "package" is a bit closer in meaning to "specfile+source" so here you are searching what effectively the list of source RPMs (build input) rather than the list of resulting binary RPMs (build output). The relationship between source and binary RPMs can be 1 to many. In the simplest case, the resulting binary RPM implicitly has the same name as the source RPM. You may also have additional declarations in the spec file defining additional binary RPMs with different names -- it's a good way to separately package logically discrete or optional features of a software using a single specfile. I am aware that I am using "package" to describe a binary RPM named for its source RPM and "sub-package" to describe binary RPMs that are named differently to the source RPM. Sorry about that -- overloaded terminology strikes again! Really, all binary RPMs are equal in the eyes of the gods, and you can only not install it by itself in the normal sense that it may have dependencies on other RPMs. Does that make sense? > Ensure Datatools and WTP-JPT (Dali) are available in DevTools (rh-eclipse47) so downstream rh-eclipse47-devstudio can use it > ---------------------------------------------------------------------------------------------------------------------------- > > Key: JBDS-4537 > URL: https://issues.jboss.org/browse/JBDS-4537 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Sub-task > Components: rpm, upstream > Affects Versions: 11.1.0.AM1 > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 11.x > > > Mat says that Eclipse DTP and WTP-JPT are already in Fedora. > So we need to ensure Datatools and WTP-JPT (Dali) are ALSO available in DevTools (rh-eclipse47); then downstream rh-eclipse47-devstudio can use it -- This message was sent by Atlassian JIRA (v7.2.3#72005)

8 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 2017