March 2018 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-25814) Server adapter wizard: should preselected most recently used connection, 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: ------------------------------------- Summary: Server adapter wizard: should preselected most recently used connection, not simply the 1st in the list (was: Server adapter wizard: should use selected or recent connetion, not simply the 1st in the list) > Server adapter wizard: should preselected most recently used connection, 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 the wizard, 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 most recently. > (If you use the application wizard again, you'll notice how it is using the 2nd connection, the one that we used most recently) -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years

1
0
0 / 0

[JBoss JIRA] (JBTIS-1214) Cannot drag and drop install link for JBTIS into Central to install JBTIS

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBTIS-1214?page=com.atlassian.jira.plugin... ] Nick Boldt commented on JBTIS-1214: ----------------------------------- When I use the URLs in Paul's fix in https://github.com/jbosstools/jbosstools-website/pull/804 ... I get fewer errors (as discussed in the PR) but one connector (bundle.ds) is still missing: !jbtis-still-missing-connector-bundle.ds.png|thumbnail! > Cannot drag and drop install link for JBTIS into Central to install JBTIS > ------------------------------------------------------------------------- > > Key: JBTIS-1214 > URL: https://issues.jboss.org/browse/JBTIS-1214 > Project: JBoss Tools Integration Stack > Issue Type: Bug > Components: distribution > Affects Versions: 4.5.2.Final > Reporter: Nick Boldt > Assignee: Paul Leacu > Fix For: 4.5.3.Final > > Attachments: jbtis-still-missing-connector-bundle.ds.png, no-ds-is-11.2.ga.png, no-jbtis-452.final.png > > > On the JBTIS 4.5.2 page [1] there's a draggable button which links to this URL [2]. > When I drag that button to *Eclipse Java EE bundle Oxygen.3 Release (4.7.3RC2)* with JBoss Tools' Red Hat Central (org.jboss.tools.community.central.feature 2.1.102.v20171124-1125) installed from the latest Oxygen stable site [3], I get an error. See screenshot: > !no-jbtis-452.final.png|thumbnail! > [1] http://tools.jboss.org/downloads/jbosstools_is/oxygen/4.5.2.Final.html#ce... > [2] http://download.jboss.org/jbosstools/central/install?connectors=jboss.int... > [3] http://download.jboss.org/jbosstools/oxygen/stable/updates -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years

1
0
0 / 0

[JBoss JIRA] (JBTIS-1214) Cannot drag and drop install link for JBTIS into Central to install JBTIS

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBTIS-1214?page=com.atlassian.jira.plugin... ] Nick Boldt updated JBTIS-1214: ------------------------------ Attachment: jbtis-still-missing-connector-bundle.ds.png > Cannot drag and drop install link for JBTIS into Central to install JBTIS > ------------------------------------------------------------------------- > > Key: JBTIS-1214 > URL: https://issues.jboss.org/browse/JBTIS-1214 > Project: JBoss Tools Integration Stack > Issue Type: Bug > Components: distribution > Affects Versions: 4.5.2.Final > Reporter: Nick Boldt > Assignee: Paul Leacu > Fix For: 4.5.3.Final > > Attachments: jbtis-still-missing-connector-bundle.ds.png, no-ds-is-11.2.ga.png, no-jbtis-452.final.png > > > On the JBTIS 4.5.2 page [1] there's a draggable button which links to this URL [2]. > When I drag that button to *Eclipse Java EE bundle Oxygen.3 Release (4.7.3RC2)* with JBoss Tools' Red Hat Central (org.jboss.tools.community.central.feature 2.1.102.v20171124-1125) installed from the latest Oxygen stable site [3], I get an error. See screenshot: > !no-jbtis-452.final.png|thumbnail! > [1] http://tools.jboss.org/downloads/jbosstools_is/oxygen/4.5.2.Final.html#ce... > [2] http://download.jboss.org/jbosstools/central/install?connectors=jboss.int... > [3] http://download.jboss.org/jbosstools/oxygen/stable/updates -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years

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: ------------------------------------- Description: 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 the wizard, 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 most recently. (If you use the application wizard again, you'll notice how it is using the 2nd connection, the one that we used most recently) was: 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 > 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 the wizard, 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 most recently. > (If you use the application wizard again, you'll notice how it is using the 2nd connection, the one that we used most recently) -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years

1
0
0 / 0

[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)

8 years

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)

8 years

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)

8 years

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)

8 years

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)

8 years

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)

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