July 2018 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-26138) Integration Tests: NodeJSAppDebugTest

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-26138?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-26138: ------------------------------- Fix Version/s: 4.9.x (was: 4.6.0.Final) > Integration Tests: NodeJSAppDebugTest > ------------------------------------- > > Key: JBIDE-26138 > URL: https://issues.jboss.org/browse/JBIDE-26138 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: integration-tests, openshift > Affects Versions: 4.6.0.AM3 > Reporter: Josef Kopriva > Assignee: Josef Kopriva > Fix For: 4.9.x > > -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-25586) OpenJDK9 + OpenShift Tooling: Cannot connect to OpenShift on CDK

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-25586?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-25586: ------------------------------- Sprint: devex #146 March 2018, devex #147 April 2018, devex #148 April 2018, devex #149 May 2018, devex #152 July 2018 (was: devex #146 March 2018, devex #147 April 2018, devex #148 April 2018, devex #149 May 2018, devex #151 June 2018) > OpenJDK9 + OpenShift Tooling: Cannot connect to OpenShift on CDK > ---------------------------------------------------------------- > > Key: JBIDE-25586 > URL: https://issues.jboss.org/browse/JBIDE-25586 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: cdk, openshift > Affects Versions: 4.5.2.Final > Environment: FC27 > OpenJDK 9.0.1 > CDK v3.3.0-rc.1-1 > eclipse.buildId=11.2.0.GA-v20180115-0516-B1866 > java.version=9.0.1 > java.vendor=Oracle Corporation > BootLoader constants: OS=linux, ARCH=x86_64, WS=gtk, NL=en_US > Framework arguments: -product com.jboss.devstudio.core.product > Command-line arguments: -os linux -ws gtk -arch x86_64 -product com.jboss.devstudio.core.product > Reporter: Josef Kopriva > Assignee: Rob Stryker > Priority: Critical > Labels: cdk, connection > Fix For: 4.9.0.AM1 > > > But, connecting to online openshift instance works. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-25586) OpenJDK9 + OpenShift Tooling: Cannot connect to OpenShift on CDK

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-25586?page=com.atlassian.jira.plugi... ] Nick Boldt commented on JBIDE-25586: ------------------------------------ [checkUnresolvedIssues.py] Slip to fixversion = *4.9.0.AM1* and sprint = *devex #152 July 2018* > OpenJDK9 + OpenShift Tooling: Cannot connect to OpenShift on CDK > ---------------------------------------------------------------- > > Key: JBIDE-25586 > URL: https://issues.jboss.org/browse/JBIDE-25586 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: cdk, openshift > Affects Versions: 4.5.2.Final > Environment: FC27 > OpenJDK 9.0.1 > CDK v3.3.0-rc.1-1 > eclipse.buildId=11.2.0.GA-v20180115-0516-B1866 > java.version=9.0.1 > java.vendor=Oracle Corporation > BootLoader constants: OS=linux, ARCH=x86_64, WS=gtk, NL=en_US > Framework arguments: -product com.jboss.devstudio.core.product > Command-line arguments: -os linux -ws gtk -arch x86_64 -product com.jboss.devstudio.core.product > Reporter: Josef Kopriva > Assignee: Rob Stryker > Priority: Critical > Labels: cdk, connection > Fix For: 4.9.0.AM1 > > > But, connecting to online openshift instance works. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBDS-4710) Central page is not showing proper content after page reload

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBDS-4710?page=com.atlassian.jira.plugin.... ] Nick Boldt updated JBDS-4710: ----------------------------- Fix Version/s: 12.9.0.AM1 (was: 12.0.0.GA) > Central page is not showing proper content after page reload > ------------------------------------------------------------ > > Key: JBDS-4710 > URL: https://issues.jboss.org/browse/JBDS-4710 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Bug > Components: central > Affects Versions: 12.0.0.AM3 > Reporter: Vojtech Prusa > Assignee: Jeff MAURY > Priority: Blocker > Fix For: 12.9.0.AM1 > > Attachments: image-2018-06-19-10-04-56-516.png, image-2018-06-19-10-06-27-472.png > > > Relaoding the central page (Getting Started tab) does not load content for project examples. > Jenkins itests fails as well > https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/job/central.... -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBDS-4710) Central page is not showing proper content after page reload

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBDS-4710?page=com.atlassian.jira.plugin.... ] Nick Boldt updated JBDS-4710: ----------------------------- Sprint: devex #152 July 2018 (was: devex #151 June 2018) > Central page is not showing proper content after page reload > ------------------------------------------------------------ > > Key: JBDS-4710 > URL: https://issues.jboss.org/browse/JBDS-4710 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Bug > Components: central > Affects Versions: 12.0.0.AM3 > Reporter: Vojtech Prusa > Assignee: Jeff MAURY > Priority: Blocker > Fix For: 12.9.0.AM1 > > Attachments: image-2018-06-19-10-04-56-516.png, image-2018-06-19-10-06-27-472.png > > > Relaoding the central page (Getting Started tab) does not load content for project examples. > Jenkins itests fails as well > https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/job/central.... -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBDS-4710) Central page is not showing proper content after page reload

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBDS-4710?page=com.atlassian.jira.plugin.... ] Nick Boldt commented on JBDS-4710: ---------------------------------- [checkUnresolvedIssues.py] Slip to fixversion = *12.9.0.AM1* and sprint = *devex #152 July 2018* > Central page is not showing proper content after page reload > ------------------------------------------------------------ > > Key: JBDS-4710 > URL: https://issues.jboss.org/browse/JBDS-4710 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Bug > Components: central > Affects Versions: 12.0.0.AM3 > Reporter: Vojtech Prusa > Assignee: Jeff MAURY > Priority: Blocker > Fix For: 12.9.0.AM1 > > Attachments: image-2018-06-19-10-04-56-516.png, image-2018-06-19-10-06-27-472.png > > > Relaoding the central page (Getting Started tab) does not load content for project examples. > Jenkins itests fails as well > https://dev-platform-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/job/central.... -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBDS-4706) Use "Red Hat Developer Studio" instead of "Red Hat JBoss Developer Studio" in graphics & text

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBDS-4706?page=com.atlassian.jira.plugin.... ] Nick Boldt updated JBDS-4706: ----------------------------- Fix Version/s: 12.9.0.AM1 (was: 12.0.0.GA) > Use "Red Hat Developer Studio" instead of "Red Hat JBoss Developer Studio" in graphics & text > --------------------------------------------------------------------------------------------- > > Key: JBDS-4706 > URL: https://issues.jboss.org/browse/JBDS-4706 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Task > Components: build, installer > Affects Versions: 12.0.0.AM1 > Reporter: Nick Boldt > Assignee: Jeff MAURY > Priority: Blocker > Fix For: 12.9.0.AM1 > > Attachments: DevStudio_iconproduction.zip, JBossPerspective.jpg, about_devstudio.png, devstudio12-central.png, devstudio_banner.png, heading.png, installer01.png, installer02.png, splash.bmp, uninstall.ico > > > Branding has requested that we rename devstudio from "Red Hat JBoss Developer Studio" to "Red Hat Developer Studio". > We'll need to collect graphics for use in the product and its website on https://devstudio.redhat.com/12/staging/updates/ -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-26071) Add server adapter for WildFly 13

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-26071?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-26071: ------------------------------- Fix Version/s: 4.9.0.AM1 (was: 4.6.0.Final) > Add server adapter for WildFly 13 > --------------------------------- > > Key: JBIDE-26071 > URL: https://issues.jboss.org/browse/JBIDE-26071 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: server > Affects Versions: 4.6.0.AM2 > Reporter: Martin Malina > Assignee: Rob Stryker > Priority: Blocker > Fix For: 4.9.0.AM1 > > > It turns out WildFly 13 was released yesterday. They're on a quarterly release cadence now apparently. So I wonder how we should deal with this. Perhaps should group some of the versions if there are no breaking changes for us? Or do you think it's better to stick with our current model of always adding a new adapter and that way you can always update the libs? -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-26071) Add server adapter for WildFly 13

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-26071?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-26071: ------------------------------- Sprint: devex #152 July 2018 (was: devex #151 June 2018) > Add server adapter for WildFly 13 > --------------------------------- > > Key: JBIDE-26071 > URL: https://issues.jboss.org/browse/JBIDE-26071 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: server > Affects Versions: 4.6.0.AM2 > Reporter: Martin Malina > Assignee: Rob Stryker > Priority: Blocker > Fix For: 4.9.0.AM1 > > > It turns out WildFly 13 was released yesterday. They're on a quarterly release cadence now apparently. So I wonder how we should deal with this. Perhaps should group some of the versions if there are no breaking changes for us? Or do you think it's better to stick with our current model of always adding a new adapter and that way you can always update the libs? -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-26071) Add server adapter for WildFly 13

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-26071?page=com.atlassian.jira.plugi... ] Nick Boldt commented on JBIDE-26071: ------------------------------------ [checkUnresolvedIssues.py] Slip to fixversion = *4.9.0.AM1* and sprint = *devex #152 July 2018* > Add server adapter for WildFly 13 > --------------------------------- > > Key: JBIDE-26071 > URL: https://issues.jboss.org/browse/JBIDE-26071 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: server > Affects Versions: 4.6.0.AM2 > Reporter: Martin Malina > Assignee: Rob Stryker > Priority: Blocker > Fix For: 4.9.0.AM1 > > > It turns out WildFly 13 was released yesterday. They're on a quarterly release cadence now apparently. So I wonder how we should deal with this. Perhaps should group some of the versions if there are no breaking changes for us? Or do you think it's better to stick with our current model of always adding a new adapter and that way you can always update the libs? -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 8 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 July 2018