September 2016 - jbosstools-issues

[JBoss JIRA] (JBDS-4050) CDK 2.2 installation failed in devsuite 1.1.0-GA-20160915

by Budh Ram Gurung (JIRA)

Budh Ram Gurung created JBDS-4050: ------------------------------------- Summary: CDK 2.2 installation failed in devsuite 1.1.0-GA-20160915 Key: JBDS-4050 URL: https://issues.jboss.org/browse/JBDS-4050 Project: Red Hat JBoss Developer Studio (devstudio) Issue Type: Bug Components: platform-installer Environment: **Operating System** Windows 10 Pro 64 Bit **Devsuite version** Devsuite 1.1.0-GA-20160915-140 Reporter: Budh Ram Gurung Priority: Minor Attachments: 1.devsuite.PNG, 2.c++.PNG, 3.vagrant_cli.PNG, install.log After passing through registration, on clicking 'Install' button in the installer window, the CDK 2.2 get failed message. Check the attached screenshots. Other information, I had following things pre-installed before running the installer: - Docker toolbox (probably it remain there when I was trying it last time) - Vagrant 1.8.1 - Cygwin - VirtualBox 5.0.26 -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBTIS-896) Drools - Use Jira states for skipping some test cases which are supposed to fail

by Andrej Podhradsky (JIRA)

[ https://issues.jboss.org/browse/JBTIS-896?page=com.atlassian.jira.plugin.... ] Andrej Podhradsky updated JBTIS-896: ------------------------------------ Component/s: drools/ jBPM QE > Drools - Use Jira states for skipping some test cases which are supposed to fail > -------------------------------------------------------------------------------- > > Key: JBTIS-896 > URL: https://issues.jboss.org/browse/JBTIS-896 > Project: JBoss Tools Integration Stack > Issue Type: Task > Components: drools/ jBPM, QE > Affects Versions: 4.4.0.Alpha1 > Reporter: Andrej Podhradsky > Assignee: Tomas David > Fix For: 4.4.0.Alpha1 > > > Currently, smoke tests fail due to a known issue in drools plugin (DROOLS-1250). Please use an existing logic for checking Jira states so that we can skip the testing of Problems view (e.g. by setting reddeer.skipUnfixedIssues=true). -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBTIS-896) Drools - Use Jira states for skipping some test cases which are supposed to fail

by Andrej Podhradsky (JIRA)

Andrej Podhradsky created JBTIS-896: --------------------------------------- Summary: Drools - Use Jira states for skipping some test cases which are supposed to fail Key: JBTIS-896 URL: https://issues.jboss.org/browse/JBTIS-896 Project: JBoss Tools Integration Stack Issue Type: Task Affects Versions: 4.4.0.Alpha1 Reporter: Andrej Podhradsky Assignee: Tomas David Fix For: 4.4.0.Alpha1 Currently, smoke tests fail due to a known issue in drools plugin (DROOLS-1250). Please use an existing logic for checking Jira states so that we can skip the testing of Problems view (e.g. by setting reddeer.skipUnfixedIssues=true). -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBTIS-895) Update code for Input Parameter Mapping

by Jozef Marko (JIRA)

Jozef Marko created JBTIS-895: --------------------------------- Summary: Update code for Input Parameter Mapping Key: JBTIS-895 URL: https://issues.jboss.org/browse/JBTIS-895 Project: JBoss Tools Integration Stack Issue Type: Sub-task Components: BPMN2, QE Affects Versions: 4.4.0.Alpha1 Reporter: Jozef Marko Assignee: Jozef Marko -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23014) Allow connections to configure the cluster namespace from which to get clusterwide templates

by Marián Labuda (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23014?page=com.atlassian.jira.plugi... ] Marián Labuda edited comment on JBIDE-23014 at 9/16/16 2:58 AM: ---------------------------------------------------------------- Not sure how this was meant to be working, but something is not working and other things which could are not working too. I have a CDK and I changed cluster namespace from openshift to something different. "customproject". I guess I would have to set proper policy, rules for the project with oadm command etc etc. to have it as a cluster namespace. First thing. Although I changed default value "openshift" to something different (what probably is not the meant cluster namespace), retrieving templates and image builder is not working correctly. New OpenShift Application wizard still lists templates with "openshift" namespace, although image builders are not listed here anymore. So it results to a list of template with "openshift" namespace without image builders for this namespace although cluster namespace is not "openshift" anymore and I have not opened wizard on the "openshift" project. Next thing, which I am not sure if should be possible, but if cluster namespace is not anything else but project with proper rules, policy.. it should work. I have another project, let's say "customproject02". I have uploaded a template to project "customproject". I am able to be switched on command line client to customproject02 and still list template(s) on customproject. But in tooling if I select customproject02 and open a New OpenShift Application wizard on it via context menu, the template with namespace "customproject" is not listed there although I set it as a cluster namespace. I am also missing units tests (one liner in Unit tests is not enough, and no integration test for this) was (Author: mlabuda): Not sure how this was meant to be working, but something is not working and other things which could are not working too. I have a CDK and I changed cluster namespace from openshift to something different. "customproject". I guess I would have to set proper policy, rules for the project with oadm command etc etc. to have it as a cluster namespace. First thing. Although I changed default value "openshift" to something different (what probably is not the meant cluster namespace), retrieving templates and image builder is not working correctly. New OpenShift Application wizard still lists templates with "openshift" namespace, although image builders are not listed here anymore. So it results to a list of template with "openshift" namespace without image builders for this namespace although cluster namespace is not "openshift" anymore and I have not opened wizard on the "openshift" project. Next thing, which I am not sure if should be possible, but if cluster namespace is not anything else but project with proper rules, policy.. it should work. I have another project, let's say "customproject02". I have uploaded a template to project "customproject". I am able to be switched on command line client to customproject02 and still list template(s) on customproject. But in tooling if I select customproject02 and open a New OpenShift Application wizard on it via context menu, the template with namespace "customproject" is not listed there although I set it as a cluster namespace. > Allow connections to configure the cluster namespace from which to get clusterwide templates > -------------------------------------------------------------------------------------------- > > Key: JBIDE-23014 > URL: https://issues.jboss.org/browse/JBIDE-23014 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: openshift > Affects Versions: 4.4.1.Final > Reporter: Jeff Cantrill > Assignee: Jeff MAURY > Labels: connection, connection_wizard, new_and_noteworthy, openshift, openshift_v3 > Fix For: 4.4.2.AM1 > > > There are a few places where we assume the cluster is configured with the openshift namespace (e.gretrieve templates) which contains templates and other resources that are available to everyone. We should provide a per connection configuration (advanced property?) that allows us to change the default since it is not discoverable from the server. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23014) Allow connections to configure the cluster namespace from which to get clusterwide templates

by Marián Labuda (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23014?page=com.atlassian.jira.plugi... ] Marián Labuda edited comment on JBIDE-23014 at 9/16/16 2:58 AM: ---------------------------------------------------------------- Not sure how this was meant to be working, but something is not working and other things which could are not working too. I have a CDK and I changed cluster namespace from openshift to something different. "customproject". I guess I would have to set proper policy, rules for the project with oadm command etc etc. to have it as a cluster namespace. First thing. Although I changed default value "openshift" to something different (what probably is not the meant cluster namespace), retrieving templates and image builder is not working correctly. New OpenShift Application wizard still lists templates with "openshift" namespace, although image builders are not listed here anymore. So it results to a list of template with "openshift" namespace without image builders for this namespace although cluster namespace is not "openshift" anymore and I have not opened wizard on the "openshift" project. Next thing, which I am not sure if should be possible, but if cluster namespace is not anything else but project with proper rules, policy.. it should work. I have another project, let's say "customproject02". I have uploaded a template to project "customproject". I am able to be switched on command line client to customproject02 and still list template(s) on customproject. But in tooling if I select customproject02 and open a New OpenShift Application wizard on it via context menu, the template with namespace "customproject" is not listed there although I set it as a cluster namespace. I am also missing more units tests (one liner in Unit tests is not enough) and there are no integration tests for this. was (Author: mlabuda): Not sure how this was meant to be working, but something is not working and other things which could are not working too. I have a CDK and I changed cluster namespace from openshift to something different. "customproject". I guess I would have to set proper policy, rules for the project with oadm command etc etc. to have it as a cluster namespace. First thing. Although I changed default value "openshift" to something different (what probably is not the meant cluster namespace), retrieving templates and image builder is not working correctly. New OpenShift Application wizard still lists templates with "openshift" namespace, although image builders are not listed here anymore. So it results to a list of template with "openshift" namespace without image builders for this namespace although cluster namespace is not "openshift" anymore and I have not opened wizard on the "openshift" project. Next thing, which I am not sure if should be possible, but if cluster namespace is not anything else but project with proper rules, policy.. it should work. I have another project, let's say "customproject02". I have uploaded a template to project "customproject". I am able to be switched on command line client to customproject02 and still list template(s) on customproject. But in tooling if I select customproject02 and open a New OpenShift Application wizard on it via context menu, the template with namespace "customproject" is not listed there although I set it as a cluster namespace. I am also missing units tests (one liner in Unit tests is not enough, and no integration test for this) > Allow connections to configure the cluster namespace from which to get clusterwide templates > -------------------------------------------------------------------------------------------- > > Key: JBIDE-23014 > URL: https://issues.jboss.org/browse/JBIDE-23014 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: openshift > Affects Versions: 4.4.1.Final > Reporter: Jeff Cantrill > Assignee: Jeff MAURY > Labels: connection, connection_wizard, new_and_noteworthy, openshift, openshift_v3 > Fix For: 4.4.2.AM1 > > > There are a few places where we assume the cluster is configured with the openshift namespace (e.gretrieve templates) which contains templates and other resources that are available to everyone. We should provide a per connection configuration (advanced property?) that allows us to change the default since it is not discoverable from the server. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBTIS-894) Fix failing ComplexSpecialCharactersAndLengthsTest

by Jozef Marko (JIRA)

[ https://issues.jboss.org/browse/JBTIS-894?page=com.atlassian.jira.plugin.... ] Jozef Marko updated JBTIS-894: ------------------------------ Git Pull Request: https://github.com/jbosstools/jbosstools-integration-stack-tests/pull/790, https://github.com/jbosstools/jbosstools-integration-stack-tests/pull/791 (was: https://github.com/jbosstools/jbosstools-integration-stack-tests/pull/790) > Fix failing ComplexSpecialCharactersAndLengthsTest > -------------------------------------------------- > > Key: JBTIS-894 > URL: https://issues.jboss.org/browse/JBTIS-894 > Project: JBoss Tools Integration Stack > Issue Type: Sub-task > Components: BPMN2, QE > Affects Versions: 4.4.0.Alpha1, 4.3.2.CR1 > Reporter: Jozef Marko > Assignee: Jozef Marko > -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBTIS-894) Fix failing ComplexSpecialCharactersAndLengthsTest

by Jozef Marko (JIRA)

[ https://issues.jboss.org/browse/JBTIS-894?page=com.atlassian.jira.plugin.... ] Jozef Marko edited comment on JBTIS-894 at 9/16/16 2:31 AM: ------------------------------------------------------------ PRs for jbtis-4.4.x and master sent. was (Author: jomarko): PR for jbtis-4.4.x sent > Fix failing ComplexSpecialCharactersAndLengthsTest > -------------------------------------------------- > > Key: JBTIS-894 > URL: https://issues.jboss.org/browse/JBTIS-894 > Project: JBoss Tools Integration Stack > Issue Type: Sub-task > Components: BPMN2, QE > Affects Versions: 4.4.0.Alpha1, 4.3.2.CR1 > Reporter: Jozef Marko > Assignee: Jozef Marko > -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBTIS-894) Fix failing ComplexSpecialCharactersAndLengthsTest

by Jozef Marko (JIRA)

[ https://issues.jboss.org/browse/JBTIS-894?page=com.atlassian.jira.plugin.... ] Jozef Marko updated JBTIS-894: ------------------------------ Affects Version/s: 4.3.2.CR1 > Fix failing ComplexSpecialCharactersAndLengthsTest > -------------------------------------------------- > > Key: JBTIS-894 > URL: https://issues.jboss.org/browse/JBTIS-894 > Project: JBoss Tools Integration Stack > Issue Type: Sub-task > Components: BPMN2, QE > Affects Versions: 4.4.0.Alpha1, 4.3.2.CR1 > Reporter: Jozef Marko > Assignee: Jozef Marko > -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBTIS-894) Fix failing ComplexSpecialCharactersAndLengthsTest

by Jozef Marko (JIRA)

Jozef Marko created JBTIS-894: --------------------------------- Summary: Fix failing ComplexSpecialCharactersAndLengthsTest Key: JBTIS-894 URL: https://issues.jboss.org/browse/JBTIS-894 Project: JBoss Tools Integration Stack Issue Type: Sub-task Components: BPMN2, QE Affects Versions: 4.4.0.Alpha1 Reporter: Jozef Marko Assignee: Jozef Marko -- This message was sent by Atlassian JIRA (v6.4.11#64026)

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