March 2016 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBDS-3622) Installer - When an install fails, the install UI simply stops - the user is not presented with a cancel/quit button

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBDS-3622?page=com.atlassian.jira.plugin.... ] Fred Bricon updated JBDS-3622: ------------------------------ Component/s: (was: cdk) > Installer - When an install fails, the install UI simply stops - the user is not presented with a cancel/quit button > -------------------------------------------------------------------------------------------------------------------- > > Key: JBDS-3622 > URL: https://issues.jboss.org/browse/JBDS-3622 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Components: installer > Reporter: Len DiMaggio > Assignee: Denis Golovin > Priority: Blocker > Labels: havoc, ui > Fix For: 9.1.0.CR1 > > Attachments: install_error.png > > > See the attached screenshot - the install has failed - the only option for the user is to close the installer window. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (JBDS-3613) Support OpenShift 3.2

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBDS-3613?page=com.atlassian.jira.plugin.... ] Fred Bricon resolved JBDS-3613. ------------------------------- Assignee: Fred Bricon (was: Andre Dietisheim) Resolution: Done Using Hardy's Vagrantfile, everything seems to work as expected. Handing over to QE for more in-depth testing > Support OpenShift 3.2 > --------------------- > > Key: JBDS-3613 > URL: https://issues.jboss.org/browse/JBDS-3613 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Epic > Components: openshift > Affects Versions: 9.1.0.Beta2 > Reporter: Max Rydahl Andersen > Assignee: Fred Bricon > Priority: Blocker > Fix For: 9.1.0.CR1 > > > CDK will GA with OpenShift 3.2 we will need to support 3.2 in OpenShift tooling. > -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (JBDS-3613) Support OpenShift 3.2

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBDS-3613?page=com.atlassian.jira.plugin.... ] Fred Bricon updated JBDS-3613: ------------------------------ > Support OpenShift 3.2 > --------------------- > > Key: JBDS-3613 > URL: https://issues.jboss.org/browse/JBDS-3613 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Epic > Components: openshift > Affects Versions: 9.1.0.Beta2 > Reporter: Max Rydahl Andersen > Assignee: Andre Dietisheim > Priority: Blocker > Fix For: 9.1.0.CR1 > > > CDK will GA with OpenShift 3.2 we will need to support 3.2 in OpenShift tooling. > -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (JBDS-3613) Support OpenShift 3.2

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBDS-3613?page=com.atlassian.jira.plugin.... ] Fred Bricon updated JBDS-3613: ------------------------------ > Support OpenShift 3.2 > --------------------- > > Key: JBDS-3613 > URL: https://issues.jboss.org/browse/JBDS-3613 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Epic > Components: openshift > Affects Versions: 9.1.0.Beta2 > Reporter: Max Rydahl Andersen > Assignee: Andre Dietisheim > Priority: Blocker > Fix For: 9.1.0.CR1 > > > CDK will GA with OpenShift 3.2 we will need to support 3.2 in OpenShift tooling. > -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (JBDS-3613) Support OpenShift 3.2

by CDW Engine (JIRA)

[ https://issues.jboss.org/browse/JBDS-3613?page=com.atlassian.jira.plugin.... ] CDW Engine updated JBDS-3613: ----------------------------- > Support OpenShift 3.2 > --------------------- > > Key: JBDS-3613 > URL: https://issues.jboss.org/browse/JBDS-3613 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Epic > Components: openshift > Affects Versions: 9.1.0.Beta2 > Reporter: Max Rydahl Andersen > Assignee: Andre Dietisheim > Priority: Blocker > Fix For: 9.1.0.CR1 > > > CDK will GA with OpenShift 3.2 we will need to support 3.2 in OpenShift tooling. > -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (JBDS-3613) Support OpenShift 3.2

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBDS-3613?page=com.atlassian.jira.plugin.... ] Fred Bricon updated JBDS-3613: ------------------------------ Status: New (was: New) Target Release: 9.1.0.GA > Support OpenShift 3.2 > --------------------- > > Key: JBDS-3613 > URL: https://issues.jboss.org/browse/JBDS-3613 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Epic > Components: openshift > Affects Versions: 9.1.0.Beta2 > Reporter: Max Rydahl Andersen > Assignee: Andre Dietisheim > Priority: Blocker > Fix For: 9.1.0.CR1 > > > CDK will GA with OpenShift 3.2 we will need to support 3.2 in OpenShift tooling. > -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (JBDS-3613) Support OpenShift 3.2

by CDW Engine (JIRA)

[ https://issues.jboss.org/browse/JBDS-3613?page=com.atlassian.jira.plugin.... ] CDW Engine reassigned JBDS-3613: -------------------------------- > Support OpenShift 3.2 > --------------------- > > Key: JBDS-3613 > URL: https://issues.jboss.org/browse/JBDS-3613 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Epic > Components: openshift > Affects Versions: 9.1.0.Beta2 > Reporter: Max Rydahl Andersen > Assignee: Andre Dietisheim > Priority: Blocker > Fix For: 9.1.0.CR1 > > > CDK will GA with OpenShift 3.2 we will need to support 3.2 in OpenShift tooling. > -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-21852) Use {noformat} tag for the stacktrace when creating a new JIRA

by Marcel Bruch (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21852?page=com.atlassian.jira.plugi... ] Marcel Bruch commented on JBIDE-21852: -------------------------------------- Feel free to post further requests. I'm not used to JIRA markup but using more tags makes sense. > Use {noformat} tag for the stacktrace when creating a new JIRA > -------------------------------------------------------------- > > Key: JBIDE-21852 > URL: https://issues.jboss.org/browse/JBIDE-21852 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: aeri > Reporter: Aurélien Pupier > Fix For: 4.3.1.CR1 > > > For an example see https://issues.jboss.org/browse/FUSETOOLS-1702 > around the stacktrace, it would be nice to have {noformat} tags, it will help having a better description with a too long scrolldown to see detains of the report. it will display the stacktrac like that: -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-21852) Use {noformat} tag for the stacktrace when creating a new JIRA

by Marcel Bruch (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21852?page=com.atlassian.jira.plugi... ] Marcel Bruch edited comment on JBIDE-21852 at 3/11/16 10:43 AM: ---------------------------------------------------------------- Makes sense for Jira. Added the \{noformat\} tags around stack trace template calls: {noformat} ${status.exception!} {noformat} was (Author: marcel.bruch): Makes sense for Jira. Added the {noformat} tags around stack trace template calls: {noformat} ${status.exception!} {noformat} > Use {noformat} tag for the stacktrace when creating a new JIRA > -------------------------------------------------------------- > > Key: JBIDE-21852 > URL: https://issues.jboss.org/browse/JBIDE-21852 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: aeri > Reporter: Aurélien Pupier > Fix For: 4.3.1.CR1 > > > For an example see https://issues.jboss.org/browse/FUSETOOLS-1702 > around the stacktrace, it would be nice to have {noformat} tags, it will help having a better description with a too long scrolldown to see detains of the report. it will display the stacktrac like that: -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-21852) Use {noformat} tag for the stacktrace when creating a new JIRA

by Marcel Bruch (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21852?page=com.atlassian.jira.plugi... ] Marcel Bruch resolved JBIDE-21852. ---------------------------------- Fix Version/s: 4.3.1.CR1 Resolution: Done > Use {noformat} tag for the stacktrace when creating a new JIRA > -------------------------------------------------------------- > > Key: JBIDE-21852 > URL: https://issues.jboss.org/browse/JBIDE-21852 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: aeri > Reporter: Aurélien Pupier > Fix For: 4.3.1.CR1 > > > For an example see https://issues.jboss.org/browse/FUSETOOLS-1702 > around the stacktrace, it would be nice to have {noformat} tags, it will help having a better description with a too long scrolldown to see detains of the report. it will display the stacktrac like that: -- 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