March 2018 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBDS-4687) Rename "JBoss Fuse" and "Red Hat JBoss Fuse" to "Red Hat Fuse" for version >7.x

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBDS-4687?page=com.atlassian.jira.plugin.... ] Nick Boldt updated JBDS-4687: ----------------------------- Summary: Rename "JBoss Fuse" and "Red Hat JBoss Fuse" to "Red Hat Fuse" for version >7.x (was: Rename "Jboss Fuse" to "Red Hat Fuse" for version >7.x) > Rename "JBoss Fuse" and "Red Hat JBoss Fuse" to "Red Hat Fuse" for version >7.x > ------------------------------------------------------------------------------- > > Key: JBDS-4687 > URL: https://issues.jboss.org/browse/JBDS-4687 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Task > Components: installer > Reporter: Aurélien Pupier > Assignee: Nick Boldt > Fix For: 11.3.0.AM3 > > > Rename "Jboss Fuse" to "Red Hat Fuse" for version >7.x (and in place in common?) -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-25814) Server adapter wizard: should use selected or recent connetion, not simply the 1st in the list

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-25814?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-25814: ------------------------------------- Labels: server_adapter_wizard (was: ) > Server adapter wizard: should use selected or recent connetion, not simply the 1st in the list > ---------------------------------------------------------------------------------------------- > > Key: JBIDE-25814 > URL: https://issues.jboss.org/browse/JBIDE-25814 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.5.3.AM2 > Reporter: Andre Dietisheim > Assignee: Rob Stryker > Labels: server_adapter_wizard > > steps: > # ASSERT: have several connections in the OpenShift explorer (ex. CDK, OpenShift online) > # EXEC: launch new application wizard via File > New > Other > OpenShift > OpenShift Application > # ASSERT: Connection selection page pops up > # EXEC: select your 2nd connection, get to the next page. But then, cancel, dont get any further. > # EXEC: launch server adapter wizard via File > New > Other > Server > OpenShift > OpenShift 3 Server adapter > # ASSERT: Connection selection page pops up > Result: > the connection selection page has the 1st connection selected, not the one that we used lately -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-25814) Server adapter wizard: should use selected or recent connetion, not simply the 1st in the list

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-25814?page=com.atlassian.jira.plugi... ] Andre Dietisheim reassigned JBIDE-25814: ---------------------------------------- Assignee: Rob Stryker > Server adapter wizard: should use selected or recent connetion, not simply the 1st in the list > ---------------------------------------------------------------------------------------------- > > Key: JBIDE-25814 > URL: https://issues.jboss.org/browse/JBIDE-25814 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.5.3.AM2 > Reporter: Andre Dietisheim > Assignee: Rob Stryker > > steps: > # ASSERT: have several connections in the OpenShift explorer (ex. CDK, OpenShift online) > # EXEC: launch new application wizard via File > New > Other > OpenShift > OpenShift Application > # ASSERT: Connection selection page pops up > # EXEC: select your 2nd connection, get to the next page. But then, cancel, dont get any further. > # EXEC: launch server adapter wizard via File > New > Other > Server > OpenShift > OpenShift 3 Server adapter > # ASSERT: Connection selection page pops up > Result: > the connection selection page has the 1st connection selected, not the one that we used lately -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBDS-4687) Rename "Jboss Fuse" to "Red Hat Fuse" for version >7.x

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBDS-4687?page=com.atlassian.jira.plugin.... ] Nick Boldt edited comment on JBDS-4687 at 3/14/18 9:59 AM: ----------------------------------------------------------- OK, so the next release of Fuse Tooling will be "Red Hat Fuse Tooling" instead of "Red Hat {color:red}-JBoss-{color} Fuse Tooling", removing the "{color:blue}*JBoss*{color}" segment. Correct? This means we would have Red Hat Fuse Tooling 10.3 go GA on April 24 (GA code freeze is April 11), as part of Red Hat {color:blue}*JBoss*{color} Developer Studio 11.3 [1], inside of Red Hat Developer Suite 2.3 [2], in support of Red Hat {color:red}-JBoss-{color} Fuse 7.0 [3]. [1] https://developers.redhat.com/products/devtudio/overview/ [2] https://developers.redhat.com/products/devsuite/overview/ [3] https://developers.redhat.com/products/fuse/overview/ (needs to be rebranded too). Aside: if you're wondering why the {color:blue}*JBoss*{color} segment remains in Red Hat {color:blue}*JBoss*{color} Developer Studio, it's a long story. TL;DR, someone decided the JBoss brand was still strong & important. Considering we get 10x more startups of {color:blue}*JBoss*{color} Tools than Red Hat {color:blue}*JBoss*{color} Developer Studio, I'm not surprised that it was decided to keep the {color:blue}*JBoss*{color} in there. #consistent was (Author: nickboldt): OK, so the next release of Fuse Tooling will be "Red Hat Fuse Tooling" instead of "Red Hat {color:red}-JBoss-{color} Fuse Tooling", removing the "{color:blue}*JBoss*{color}" segment. Correct? This means we would have Red Hat Fuse Tooling 10.3 go GA on April 24, as part of Red Hat {color:blue}*JBoss*{color} Developer Studio 11.3 [1], inside of Red Hat Developer Suite 2.3 [2], in support of Red Hat {color:red}-JBoss-{color} Fuse 7.0 [3]. [1] https://developers.redhat.com/products/devtudio/overview/ [2] https://developers.redhat.com/products/devsuite/overview/ [3] https://developers.redhat.com/products/fuse/overview/ (needs to be rebranded too). Aside: if you're wondering why the {color:blue}*JBoss*{color} segment remains in Red Hat {color:blue}*JBoss*{color} Developer Studio, it's a long story. TL;DR, someone decided the JBoss brand was still strong & important. Considering we get 10x more startups of {color:blue}*JBoss*{color} Tools than Red Hat {color:blue}*JBoss*{color} Developer Studio, I'm not surprised that it was decided to keep the {color:blue}*JBoss*{color} in there. #consistent > Rename "Jboss Fuse" to "Red Hat Fuse" for version >7.x > ------------------------------------------------------ > > Key: JBDS-4687 > URL: https://issues.jboss.org/browse/JBDS-4687 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Task > Components: installer > Reporter: Aurélien Pupier > Assignee: Nick Boldt > Fix For: 11.3.0.AM3 > > > Rename "Jboss Fuse" to "Red Hat Fuse" for version >7.x (and in place in common?) -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-25814) Server adapter wizard: should use selected or recent connetion, not simply the 1st in the list

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-25814?page=com.atlassian.jira.plugi... ] Andre Dietisheim commented on JBIDE-25814: ------------------------------------------ [~rob.stryker] we have the concept of the most recently used connection: {code:title=ConnectionsRegistry} public IConnection getRecentConnection() { return recentConnection; } {code} The connection wizard is using this most recently used connection if none was provided that should be selected. {code:title=ConnectionWizard} public ConnectionWizard() { this(ConnectionsRegistrySingleton.getInstance().getRecentConnection(), NEW_CONNECTION_TITLE); } {code} The connection that one is using to connect is stored upon connecting: {code:title=ConnectionWizardPageModel} public IStatus connect() { ... ConnectionsRegistrySingleton.getInstance().setRecent(connection); ... } {code} > Server adapter wizard: should use selected or recent connetion, not simply the 1st in the list > ---------------------------------------------------------------------------------------------- > > Key: JBIDE-25814 > URL: https://issues.jboss.org/browse/JBIDE-25814 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.5.3.AM2 > Reporter: Andre Dietisheim > > steps: > # ASSERT: have several connections in the OpenShift explorer (ex. CDK, OpenShift online) > # EXEC: launch new application wizard via File > New > Other > OpenShift > OpenShift Application > # ASSERT: Connection selection page pops up > # EXEC: select your 2nd connection, get to the next page. But then, cancel, dont get any further. > # EXEC: launch server adapter wizard via File > New > Other > Server > OpenShift > OpenShift 3 Server adapter > # ASSERT: Connection selection page pops up > Result: > the connection selection page has the 1st connection selected, not the one that we used lately -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-25815) Fir Forge ITests failures on Jenkins

by Josef Kopriva (JIRA)

Josef Kopriva created JBIDE-25815: ------------------------------------- Summary: Fir Forge ITests failures on Jenkins Key: JBIDE-25815 URL: https://issues.jboss.org/browse/JBIDE-25815 Project: Tools (JBoss Tools) Issue Type: Task Components: forge, integration-tests Affects Versions: 4.5.3.AM3 Environment: Jenkins Reporter: Josef Kopriva Assignee: Josef Kopriva Stabilize ITests on Jenkins for forge. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-25815) Fix Forge ITests failures on Jenkins

by Josef Kopriva (JIRA)

[ https://issues.jboss.org/browse/JBIDE-25815?page=com.atlassian.jira.plugi... ] Josef Kopriva updated JBIDE-25815: ---------------------------------- Summary: Fix Forge ITests failures on Jenkins (was: Fir Forge ITests failures on Jenkins) > Fix Forge ITests failures on Jenkins > ------------------------------------ > > Key: JBIDE-25815 > URL: https://issues.jboss.org/browse/JBIDE-25815 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: forge, integration-tests > Affects Versions: 4.5.3.AM3 > Environment: Jenkins > Reporter: Josef Kopriva > Assignee: Josef Kopriva > > Stabilize ITests on Jenkins for forge. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBDS-4687) Rename "Jboss Fuse" to "Red Hat Fuse" for version >7.x

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBDS-4687?page=com.atlassian.jira.plugin.... ] Nick Boldt commented on JBDS-4687: ---------------------------------- OK, so the next release of Fuse Tooling will be "Red Hat Fuse Tooling" instead of "Red Hat {color:red}-JBoss-{color} Fuse Tooling", removing the "{color:blue}*JBoss*{color}" segment. Correct? This means we would have Red Hat Fuse Tooling 10.3 go GA on April 24, as part of Red Hat {color:blue}*JBoss*{color} Developer Studio 11.3 [1], inside of Red Hat Developer Suite 2.3 [2], in support of Red Hat {color:red}-JBoss-{color} Fuse 7.0 [3]. [1] https://developers.redhat.com/products/devtudio/overview/ [2] https://developers.redhat.com/products/devsuite/overview/ [3] https://developers.redhat.com/products/fuse/overview/ (needs to be rebranded too). Aside: if you're wondering why the {color:blue}*JBoss*{color} segment remains in Red Hat {color:blue}*JBoss*{color} Developer Studio, it's a long story. TL;DR, someone decided the JBoss brand was still strong & important. Considering we get 10x more startups of {color:blue}*JBoss*{color} Tools than Red Hat {color:blue}*JBoss*{color} Developer Studio, I'm not surprised that it was decided to keep the {color:blue}*JBoss*{color} in there. > Rename "Jboss Fuse" to "Red Hat Fuse" for version >7.x > ------------------------------------------------------ > > Key: JBDS-4687 > URL: https://issues.jboss.org/browse/JBDS-4687 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Task > Components: installer > Reporter: Aurélien Pupier > Assignee: Nick Boldt > Fix For: 11.3.0.AM3 > > > Rename "Jboss Fuse" to "Red Hat Fuse" for version >7.x (and in place in common?) -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBDS-4687) Rename "Jboss Fuse" to "Red Hat Fuse" for version >7.x

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBDS-4687?page=com.atlassian.jira.plugin.... ] Nick Boldt edited comment on JBDS-4687 at 3/14/18 9:58 AM: ----------------------------------------------------------- OK, so the next release of Fuse Tooling will be "Red Hat Fuse Tooling" instead of "Red Hat {color:red}-JBoss-{color} Fuse Tooling", removing the "{color:blue}*JBoss*{color}" segment. Correct? This means we would have Red Hat Fuse Tooling 10.3 go GA on April 24, as part of Red Hat {color:blue}*JBoss*{color} Developer Studio 11.3 [1], inside of Red Hat Developer Suite 2.3 [2], in support of Red Hat {color:red}-JBoss-{color} Fuse 7.0 [3]. [1] https://developers.redhat.com/products/devtudio/overview/ [2] https://developers.redhat.com/products/devsuite/overview/ [3] https://developers.redhat.com/products/fuse/overview/ (needs to be rebranded too). Aside: if you're wondering why the {color:blue}*JBoss*{color} segment remains in Red Hat {color:blue}*JBoss*{color} Developer Studio, it's a long story. TL;DR, someone decided the JBoss brand was still strong & important. Considering we get 10x more startups of {color:blue}*JBoss*{color} Tools than Red Hat {color:blue}*JBoss*{color} Developer Studio, I'm not surprised that it was decided to keep the {color:blue}*JBoss*{color} in there. #consistent was (Author: nickboldt): OK, so the next release of Fuse Tooling will be "Red Hat Fuse Tooling" instead of "Red Hat {color:red}-JBoss-{color} Fuse Tooling", removing the "{color:blue}*JBoss*{color}" segment. Correct? This means we would have Red Hat Fuse Tooling 10.3 go GA on April 24, as part of Red Hat {color:blue}*JBoss*{color} Developer Studio 11.3 [1], inside of Red Hat Developer Suite 2.3 [2], in support of Red Hat {color:red}-JBoss-{color} Fuse 7.0 [3]. [1] https://developers.redhat.com/products/devtudio/overview/ [2] https://developers.redhat.com/products/devsuite/overview/ [3] https://developers.redhat.com/products/fuse/overview/ (needs to be rebranded too). Aside: if you're wondering why the {color:blue}*JBoss*{color} segment remains in Red Hat {color:blue}*JBoss*{color} Developer Studio, it's a long story. TL;DR, someone decided the JBoss brand was still strong & important. Considering we get 10x more startups of {color:blue}*JBoss*{color} Tools than Red Hat {color:blue}*JBoss*{color} Developer Studio, I'm not surprised that it was decided to keep the {color:blue}*JBoss*{color} in there. > Rename "Jboss Fuse" to "Red Hat Fuse" for version >7.x > ------------------------------------------------------ > > Key: JBDS-4687 > URL: https://issues.jboss.org/browse/JBDS-4687 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Task > Components: installer > Reporter: Aurélien Pupier > Assignee: Nick Boldt > Fix For: 11.3.0.AM3 > > > Rename "Jboss Fuse" to "Red Hat Fuse" for version >7.x (and in place in common?) -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-25814) Server adapter wizard: should use selected or recent connetion, not simply the 1st in the list

by Andre Dietisheim (JIRA)

Andre Dietisheim created JBIDE-25814: ---------------------------------------- Summary: Server adapter wizard: should use selected or recent connetion, not simply the 1st in the list Key: JBIDE-25814 URL: https://issues.jboss.org/browse/JBIDE-25814 Project: Tools (JBoss Tools) Issue Type: Enhancement Components: openshift Affects Versions: 4.5.3.AM2 Reporter: Andre Dietisheim steps: # ASSERT: have several connections in the OpenShift explorer (ex. CDK, OpenShift online) # EXEC: launch new application wizard via File > New > Other > OpenShift > OpenShift Application # ASSERT: Connection selection page pops up # EXEC: select your 2nd connection, get to the next page. But then, cancel, dont get any further. # EXEC: launch server adapter wizard via File > New > Other > Server > OpenShift > OpenShift 3 Server adapter # ASSERT: Connection selection page pops up Result: the connection selection page has the 1st connection selected, not the one that we used lately -- This message was sent by Atlassian JIRA (v7.5.0#75005)

7 years, 10 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 March 2018