March 2016 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBTIS-600) Add XmlStagingtable test updates to jbtis 4.2.x branch and include changes for JDBCHelper

by Matus Makovy (JIRA)

[ https://issues.jboss.org/browse/JBTIS-600?page=com.atlassian.jira.plugin.... ] Matus Makovy resolved JBTIS-600. -------------------------------- Resolution: Done PR: https://github.com/jbosstools/jbosstools-integration-stack-tests/pull/657 > Add XmlStagingtable test updates to jbtis 4.2.x branch and include changes for JDBCHelper > ----------------------------------------------------------------------------------------- > > Key: JBTIS-600 > URL: https://issues.jboss.org/browse/JBTIS-600 > Project: JBoss Tools Integration Stack > Issue Type: Bug > Components: QE, teiid > Affects Versions: 4.2.5.Final > Reporter: Matus Makovy > Assignee: Andrej Podhradsky > -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (JBTIS-600) Add XmlStagingtable test updates to jbtis 4.2.x branch and include changes for JDBCHelper

by Andrej Podhradsky (JIRA)

[ https://issues.jboss.org/browse/JBTIS-600?page=com.atlassian.jira.plugin.... ] Andrej Podhradsky commented on JBTIS-600: ----------------------------------------- [~mmakovy] could you provide which commins / pull requests you want do merge, please? > Add XmlStagingtable test updates to jbtis 4.2.x branch and include changes for JDBCHelper > ----------------------------------------------------------------------------------------- > > Key: JBTIS-600 > URL: https://issues.jboss.org/browse/JBTIS-600 > Project: JBoss Tools Integration Stack > Issue Type: Bug > Components: QE, teiid > Affects Versions: 4.2.5.Final > Reporter: Matus Makovy > Assignee: Andrej Podhradsky > -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (JBTIS-600) Add XmlStagingtable test updates to jbtis 4.2.x branch and include changes for JDBCHelper

by Andrej Podhradsky (JIRA)

[ https://issues.jboss.org/browse/JBTIS-600?page=com.atlassian.jira.plugin.... ] Andrej Podhradsky edited comment on JBTIS-600 at 3/17/16 5:53 AM: ------------------------------------------------------------------ [~mmakovy] could you provide which commits / pull requests you want do merge, please? was (Author: apodhrad): [~mmakovy] could you provide which commins / pull requests you want do merge, please? > Add XmlStagingtable test updates to jbtis 4.2.x branch and include changes for JDBCHelper > ----------------------------------------------------------------------------------------- > > Key: JBTIS-600 > URL: https://issues.jboss.org/browse/JBTIS-600 > Project: JBoss Tools Integration Stack > Issue Type: Bug > Components: QE, teiid > Affects Versions: 4.2.5.Final > Reporter: Matus Makovy > Assignee: Andrej Podhradsky > -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (JBTIS-600) Add XmlStagingtable test updates to jbtis 4.2.x branch and include changes for JDBCHelper

by Matus Makovy (JIRA)

Matus Makovy created JBTIS-600: ---------------------------------- Summary: Add XmlStagingtable test updates to jbtis 4.2.x branch and include changes for JDBCHelper Key: JBTIS-600 URL: https://issues.jboss.org/browse/JBTIS-600 Project: JBoss Tools Integration Stack Issue Type: Bug Components: QE, teiid Affects Versions: 4.2.5.Final Reporter: Matus Makovy Assignee: Andrej Podhradsky -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (JBTIS-571) Error loading file switchyard.xml. Unable to load the generated resource.

by Andrej Podhradsky (JIRA)

[ https://issues.jboss.org/browse/JBTIS-571?page=com.atlassian.jira.plugin.... ] Andrej Podhradsky commented on JBTIS-571: ----------------------------------------- Nicolas, do you see the same behavior like in the attached screencast or something else? I'm wondering why your IDE doesn't start. > Error loading file switchyard.xml. Unable to load the generated resource. > ------------------------------------------------------------------------- > > Key: JBTIS-571 > URL: https://issues.jboss.org/browse/JBTIS-571 > Project: JBoss Tools Integration Stack > Issue Type: Bug > Components: switchyard > Affects Versions: 9.0.0.Alpha2 > Reporter: nicolas duminil > Assignee: Brian Fitzpatrick > Priority: Blocker > Fix For: 9.0.0.Beta1 > > Attachments: jbtis-571_1.png, jbtis-571_2.png, Screencast_JBDS900GA_JBDSISAlpha2.webm > > > After creating a new switchyard project, next time it starts up JBDS is not able to open its own generated siwtchyard.xml file. The error "Error loading file switchyard.xml. Unable to load the generated resource" is displayed. The only choice is the OK button. Pressing it, the JBDS screen doesn't display but JBDS seems to be started and the LCK file created. The only option the user has is to kill the process. > Tested on Windows 7 and Windows 10 with Java 8. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-21701) Enable port forwarding on a given pod and a given debug port

by Xavier Coulon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21701?page=com.atlassian.jira.plugi... ] Xavier Coulon edited comment on JBIDE-21701 at 3/17/16 5:46 AM: ---------------------------------------------------------------- Adding a link to a patch that excludes uncessary MacOSX-specific dependencies was (Author: xcoulon): Adding a link to a patch that excludes optional dependencies during Tycho builds on non-Mac platforms > Enable port forwarding on a given pod and a given debug port > ------------------------------------------------------------ > > Key: JBIDE-21701 > URL: https://issues.jboss.org/browse/JBIDE-21701 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: openshift > Affects Versions: 4.3.1.Beta2 > Reporter: Fred Bricon > Assignee: Xavier Coulon > Fix For: 4.3.1.CR1 > > > Given a remote debug port, we need to ensure to programmatically enable port forwarding on a pod, return the matching local debug port (named debug). > The local port could be determined as the next available free port, or read from the server adapter's preferences. But that latter case would also require adding some UI to let a user set the local port. That could be done in a later iteration. > If port forwarding is already enabled on the remote pod, then the current local debug port should be returned -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (JBTIS-571) Error loading file switchyard.xml. Unable to load the generated resource.

by Andrej Podhradsky (JIRA)

[ https://issues.jboss.org/browse/JBTIS-571?page=com.atlassian.jira.plugin.... ] Andrej Podhradsky updated JBTIS-571: ------------------------------------ Attachment: Screencast_JBDS900GA_JBDSISAlpha2.webm > Error loading file switchyard.xml. Unable to load the generated resource. > ------------------------------------------------------------------------- > > Key: JBTIS-571 > URL: https://issues.jboss.org/browse/JBTIS-571 > Project: JBoss Tools Integration Stack > Issue Type: Bug > Components: switchyard > Affects Versions: 9.0.0.Alpha2 > Reporter: nicolas duminil > Assignee: Brian Fitzpatrick > Priority: Blocker > Fix For: 9.0.0.Beta1 > > Attachments: jbtis-571_1.png, jbtis-571_2.png, Screencast_JBDS900GA_JBDSISAlpha2.webm > > > After creating a new switchyard project, next time it starts up JBDS is not able to open its own generated siwtchyard.xml file. The error "Error loading file switchyard.xml. Unable to load the generated resource" is displayed. The only choice is the OK button. Pressing it, the JBDS screen doesn't display but JBDS seems to be started and the LCK file created. The only option the user has is to kill the process. > Tested on Windows 7 and Windows 10 with Java 8. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-21858) Opening the OpenShift 3 server adapter wizard is verrrry slow

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21858?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-21858: ------------------------------------- Labels: openshift_v3 server_adapter_wizard (was: ) > Opening the OpenShift 3 server adapter wizard is verrrry slow > ------------------------------------------------------------- > > Key: JBIDE-21858 > URL: https://issues.jboss.org/browse/JBIDE-21858 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.1.CR1 > Reporter: Fred Bricon > Assignee: Andre Dietisheim > Priority: Critical > Labels: openshift_v3, server_adapter_wizard > Fix For: 4.3.1.CR1 > > > Open the Server Adapter menu from the OpenShift explorer is suuuuper slow. We need to fix it! -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-21830) Server Adapter wizard: route selected by default is wrong

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21830?page=com.atlassian.jira.plugi... ] Andre Dietisheim edited comment on JBIDE-21830 at 3/17/16 5:26 AM: ------------------------------------------------------------------- [~scabanovich] thanks, but I'm already on this. Maybe I should have set "Coding in progress...". You found the proper fix for the selection, but there are other issue here: * the filtering is repeated in several place, imho we should have these kind of queries centralized * if fixing JBIDE-21858 the filtering has to happen on existing items, not resources loaded especially for this usecase of choosing a route. There are plenty of duplicate and non-intentional occurrences of loading of items (ex. service.getProject() right above your change does load - and there are plenty of these). I thus combine this and the other issue in one PR. was (Author: adietish): [~scabanovich] thanks, but I'm already on this. Maybe I should have set "Coding in progress...". You found the proper fix for the selection, but there are other issue here: * the filtering is repeated in several place, imho we should have these kind of queries centralized * if fixing JBIDE-21858 the filtering has to happen on existing items, not resources loaded especially for this usecase of choosing a route. There are plenty of duplicate and non-intentional occurrences of loading of items (ex. service.getProject() right above your change does load - and there are plenty of these). > Server Adapter wizard: route selected by default is wrong > --------------------------------------------------------- > > Key: JBIDE-21830 > URL: https://issues.jboss.org/browse/JBIDE-21830 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.1.CR1 > Reporter: Andre Dietisheim > Assignee: Andre Dietisheim > Priority: Blocker > Fix For: 4.3.1.CR1 > > Attachments: JBoss_-_nodejs-mongodb-example_at_OpenShift_3__console_engint_openshift_com__-_Eclipse_-__Users_max_Documents_workspace-ec2016.png, wrong-default-route.png > > -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-21830) Server Adapter wizard: route selected by default is wrong

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21830?page=com.atlassian.jira.plugi... ] Andre Dietisheim edited comment on JBIDE-21830 at 3/17/16 5:24 AM: ------------------------------------------------------------------- [~scabanovich] thanks, but I'm already on this. Maybe I should have set "Coding in progress...". You found the proper fix for the selection, but there are other issue here: * the filtering is repeated in several place, imho we should have these kind of queries centralized * if fixing JBIDE-21858 the filtering has to happen on existing items, not resources loaded especially for this usecase of choosing a route. There are plenty of duplicate and non-intentional occurrences of loading of items (ex. service.getProject() right above your change does load - and there are plenty of these). was (Author: adietish): [~scabanovich] thanks, but I'm already on this. Maybe I should have set "Coding in progress...". You found the proper fix for the selection, but there are other issue here: * the filtering is repeated in several place, imho we should have these kind of queries centralized * if fixing JBIDE-21858 the filtering has to happen on existing items since the loading of items has to be reduced, duplicate loading eliminated (ex. service.getProject() right above your change does load - and there are plenty of these). > Server Adapter wizard: route selected by default is wrong > --------------------------------------------------------- > > Key: JBIDE-21830 > URL: https://issues.jboss.org/browse/JBIDE-21830 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.1.CR1 > Reporter: Andre Dietisheim > Assignee: Andre Dietisheim > Priority: Blocker > Fix For: 4.3.1.CR1 > > Attachments: JBoss_-_nodejs-mongodb-example_at_OpenShift_3__console_engint_openshift_com__-_Eclipse_-__Users_max_Documents_workspace-ec2016.png, wrong-default-route.png > > -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

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 March 2016