December 2015 - jbosstools-issues

[JBoss JIRA] (JBIDE-21348) Server Adapter wizard: should default to existing v3 connection (not <New Connection>)

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21348?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-21348: ------------------------------------- Summary: Server Adapter wizard: should default to existing v3 connection (not <New Connection>) (was: Server Adapter wizard: should default to existing v3 connection (not <New Connection>) > Server Adapter wizard: should default to existing v3 connection (not <New Connection>) > -------------------------------------------------------------------------------------- > > Key: JBIDE-21348 > URL: https://issues.jboss.org/browse/JBIDE-21348 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.3.1.Beta1 > Reporter: Andre Dietisheim > Assignee: Andre Dietisheim > Priority: Minor > Labels: connection_wizard > Fix For: 4.4.0.Alpha1 > > Attachments: defaults-to-new-connection.png > > > how to reproduce: > # ASSERT: make sure that you have at least 1 connection to a v3 server defined (showing up in OpenShift Explorer) > # EXEC: launch v3 OpenShift server adapter wizard via File > New > Server > OpenShift 3 > # ASSERT: connection dialog shows up as 1st wizard page > Result: > <New Connection> is preselected even though I have 1 v3 connection: > !defaults-to-new-connection.png! > Expected Result: > The last v3 connection that I used should be preselected (if it exists) -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21347) Server Adapter wizard: should default to existing v3 connection (not <New Connection>

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21347?page=com.atlassian.jira.plugi... ] Andre Dietisheim reassigned JBIDE-21347: ---------------------------------------- Assignee: Andre Dietisheim Resolution: Done merged and pushed to upstream/jbosstools-4.3.x > Server Adapter wizard: should default to existing v3 connection (not <New Connection> > ------------------------------------------------------------------------------------- > > Key: JBIDE-21347 > URL: https://issues.jboss.org/browse/JBIDE-21347 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.3.1.Beta1 > Reporter: Andre Dietisheim > Assignee: Andre Dietisheim > Priority: Minor > Labels: connection_wizard > Fix For: 4.3.1.Beta2 > > Attachments: defaults-to-new-connection.png > > > how to reproduce: > # ASSERT: make sure that you have at least 1 connection to a v3 server defined (showing up in OpenShift Explorer) > # EXEC: launch v3 OpenShift server adapter wizard via File > New > Server > OpenShift 3 > # ASSERT: connection dialog shows up as 1st wizard page > Result: > <New Connection> is preselected even though I have 1 v3 connection: > !defaults-to-new-connection.png! > Expected Result: > The last v3 connection that I used should be preselected (if it exists) -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21348) Server Adapter wizard: should default to existing v3 connection (not <New Connection>

by Andre Dietisheim (JIRA)

Andre Dietisheim created JBIDE-21348: ---------------------------------------- Summary: Server Adapter wizard: should default to existing v3 connection (not <New Connection> Key: JBIDE-21348 URL: https://issues.jboss.org/browse/JBIDE-21348 Project: Tools (JBoss Tools) Issue Type: Enhancement Components: openshift Affects Versions: 4.3.1.Beta1 Reporter: Andre Dietisheim Assignee: Andre Dietisheim Priority: Minor Fix For: 4.3.1.Beta2 how to reproduce: # ASSERT: make sure that you have at least 1 connection to a v3 server defined (showing up in OpenShift Explorer) # EXEC: launch v3 OpenShift server adapter wizard via File > New > Server > OpenShift 3 # ASSERT: connection dialog shows up as 1st wizard page Result: <New Connection> is preselected even though I have 1 v3 connection: !defaults-to-new-connection.png! Expected Result: The last v3 connection that I used should be preselected (if it exists) -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21348) Server Adapter wizard: should default to existing v3 connection (not <New Connection>

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21348?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-21348: ------------------------------------- Fix Version/s: 4.4.0.Alpha1 (was: 4.3.1.Beta2) > Server Adapter wizard: should default to existing v3 connection (not <New Connection> > ------------------------------------------------------------------------------------- > > Key: JBIDE-21348 > URL: https://issues.jboss.org/browse/JBIDE-21348 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.3.1.Beta1 > Reporter: Andre Dietisheim > Assignee: Andre Dietisheim > Priority: Minor > Labels: connection_wizard > Fix For: 4.4.0.Alpha1 > > Attachments: defaults-to-new-connection.png > > > how to reproduce: > # ASSERT: make sure that you have at least 1 connection to a v3 server defined (showing up in OpenShift Explorer) > # EXEC: launch v3 OpenShift server adapter wizard via File > New > Server > OpenShift 3 > # ASSERT: connection dialog shows up as 1st wizard page > Result: > <New Connection> is preselected even though I have 1 v3 connection: > !defaults-to-new-connection.png! > Expected Result: > The last v3 connection that I used should be preselected (if it exists) -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21347) Server Adapter wizard: should default to existing v3 connection (not <New Connection>

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21347?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-21347: ------------------------------------- Fix Version/s: 4.3.1.Beta2 > Server Adapter wizard: should default to existing v3 connection (not <New Connection> > ------------------------------------------------------------------------------------- > > Key: JBIDE-21347 > URL: https://issues.jboss.org/browse/JBIDE-21347 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.3.1.Beta1 > Reporter: Andre Dietisheim > Priority: Minor > Labels: connection_wizard > Fix For: 4.3.1.Beta2 > > Attachments: defaults-to-new-connection.png > > > how to reproduce: > # ASSERT: make sure that you have at least 1 connection to a v3 server defined (showing up in OpenShift Explorer) > # EXEC: launch v3 OpenShift server adapter wizard via File > New > Server > OpenShift 3 > # ASSERT: connection dialog shows up as 1st wizard page > Result: > <New Connection> is preselected even though I have 1 v3 connection: > !defaults-to-new-connection.png! > Expected Result: > The last v3 connection that I used should be preselected (if it exists) -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21347) Server Adapter wizard: should default to existing v3 connection (not <New Connection>

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21347?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-21347: ------------------------------------- Labels: connection_wizard (was: ) > Server Adapter wizard: should default to existing v3 connection (not <New Connection> > ------------------------------------------------------------------------------------- > > Key: JBIDE-21347 > URL: https://issues.jboss.org/browse/JBIDE-21347 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.3.1.Beta1 > Reporter: Andre Dietisheim > Priority: Minor > Labels: connection_wizard > Attachments: defaults-to-new-connection.png > > > how to reproduce: > # ASSERT: make sure that you have at least 1 connection to a v3 server defined (showing up in OpenShift Explorer) > # EXEC: launch v3 OpenShift server adapter wizard via File > New > Server > OpenShift 3 > # ASSERT: connection dialog shows up as 1st wizard page > Result: > <New Connection> is preselected even though I have 1 v3 connection: > !defaults-to-new-connection.png! > Expected Result: > The last v3 connection that I used should be preselected (if it exists) -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21347) Server Adapter wizard: should default to existing v3 connection (not <New Connection>

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21347?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-21347: ------------------------------------- Summary: Server Adapter wizard: should default to existing v3 connection (not <New Connection> (was: Server Adapter wizard: should default to 1st available v3 connection (not <New Connection>) > Server Adapter wizard: should default to existing v3 connection (not <New Connection> > ------------------------------------------------------------------------------------- > > Key: JBIDE-21347 > URL: https://issues.jboss.org/browse/JBIDE-21347 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.3.1.Beta1 > Reporter: Andre Dietisheim > Priority: Minor > Attachments: defaults-to-new-connection.png > > > how to reproduce: > # ASSERT: make sure that you have at least 1 connection to a v3 server defined (showing up in OpenShift Explorer) > # EXEC: launch v3 OpenShift server adapter wizard via File > New > Server > OpenShift 3 > # ASSERT: connection dialog shows up as 1st wizard page > Result: > <New Connection> is preselected even though I have 1 v3 connection: > !defaults-to-new-connection.png! -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21347) Server Adapter wizard: should default to existing v3 connection (not <New Connection>

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21347?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-21347: ------------------------------------- Description: how to reproduce: # ASSERT: make sure that you have at least 1 connection to a v3 server defined (showing up in OpenShift Explorer) # EXEC: launch v3 OpenShift server adapter wizard via File > New > Server > OpenShift 3 # ASSERT: connection dialog shows up as 1st wizard page Result: <New Connection> is preselected even though I have 1 v3 connection: !defaults-to-new-connection.png! Expected Result: The last v3 connection that I used should be preselected (if it exists) was: how to reproduce: # ASSERT: make sure that you have at least 1 connection to a v3 server defined (showing up in OpenShift Explorer) # EXEC: launch v3 OpenShift server adapter wizard via File > New > Server > OpenShift 3 # ASSERT: connection dialog shows up as 1st wizard page Result: <New Connection> is preselected even though I have 1 v3 connection: !defaults-to-new-connection.png! > Server Adapter wizard: should default to existing v3 connection (not <New Connection> > ------------------------------------------------------------------------------------- > > Key: JBIDE-21347 > URL: https://issues.jboss.org/browse/JBIDE-21347 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.3.1.Beta1 > Reporter: Andre Dietisheim > Priority: Minor > Attachments: defaults-to-new-connection.png > > > how to reproduce: > # ASSERT: make sure that you have at least 1 connection to a v3 server defined (showing up in OpenShift Explorer) > # EXEC: launch v3 OpenShift server adapter wizard via File > New > Server > OpenShift 3 > # ASSERT: connection dialog shows up as 1st wizard page > Result: > <New Connection> is preselected even though I have 1 v3 connection: > !defaults-to-new-connection.png! > Expected Result: > The last v3 connection that I used should be preselected (if it exists) -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21317) EA enablement status is not propagated to first page of Central

by Radim Hopp (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21317?page=com.atlassian.jira.plugi... ] Radim Hopp closed JBIDE-21317. ------------------------------ Verified in JBDS 9.1.0.Beta1-v20151216-2040-B197 > EA enablement status is not propagated to first page of Central > --------------------------------------------------------------- > > Key: JBIDE-21317 > URL: https://issues.jboss.org/browse/JBIDE-21317 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: central > Affects Versions: 4.3.1.Beta1 > Environment: JBDS 9.1.0.Beta1-v20151212-0638-B189 > Reporter: Radim Hopp > Assignee: Fred Bricon > Labels: respin-a > Fix For: 4.3.1.Beta1 > > > See steps to Reproduce. > Note, that this was working in JBDS 9.0.0.GA -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21347) Server Adapter wizard: should default to 1st available v3 connection (not <New Connection>

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21347?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-21347: ------------------------------------- Priority: Minor (was: Major) > Server Adapter wizard: should default to 1st available v3 connection (not <New Connection> > ------------------------------------------------------------------------------------------ > > Key: JBIDE-21347 > URL: https://issues.jboss.org/browse/JBIDE-21347 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.3.1.Beta1 > Reporter: Andre Dietisheim > Priority: Minor > Attachments: defaults-to-new-connection.png > > > how to reproduce: > # ASSERT: make sure that you have at least 1 connection to a v3 server defined (showing up in OpenShift Explorer) > # EXEC: launch v3 OpenShift server adapter wizard via File > New > Server > OpenShift 3 > # ASSERT: connection dialog shows up as 1st wizard page > Result: > <New Connection> is preselected even though I have 1 v3 connection: > !defaults-to-new-connection.png! -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 3 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 December 2015