October 2017 - 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 Mohit Suman (JIRA)

[ https://issues.jboss.org/browse/JBDS-3622?page=com.atlassian.jira.plugin.... ] Mohit Suman updated JBDS-3622: ------------------------------ Story Points: 5 > 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: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Bug > Components: platform-installer > Reporter: Len DiMaggio > Assignee: Mohit Suman > Labels: ui > Fix For: 11.x > > Attachments: install_error.png, installing.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 (v7.5.0#75005)

8 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24491) CDK Server adapter: allow users to look up the address of the docker registry

by Jeff MAURY (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24491?page=com.atlassian.jira.plugi... ] Jeff MAURY updated JBIDE-24491: ------------------------------- Sprint: devex #137 September 2017, devex #139 October 2017 (was: devex #137 September 2017) > CDK Server adapter: allow users to look up the address of the docker registry > ----------------------------------------------------------------------------- > > Key: JBIDE-24491 > URL: https://issues.jboss.org/browse/JBIDE-24491 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: cdk > Affects Versions: 4.4.4.Final > Reporter: Andre Dietisheim > Assignee: Rob Stryker > Fix For: 4.5.x > > > if you want to push a docker image to the docker registry within OpenShift you need the address of the docker registry. > When launching the cdk in Eclipse our tooling creates the OpenShift connection for the tooling filling out that address. > Users that didnt launch the cdk via the server adapter or had their connection already defined when launching it, would have to look the address up manually. One does this on the command line via {code}./minishift openshift registry{code} > It would be nice if the server adapter would offer a way to look it up so that the user does not have to go the command line. > I dont know yet how to look it up for the OpenShift online variant though. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3631) When an install fails, the user is able to view the error log to debug the cause of the failure, but the UI does not display any details

by Mohit Suman (JIRA)

[ https://issues.jboss.org/browse/JBDS-3631?page=com.atlassian.jira.plugin.... ] Mohit Suman updated JBDS-3631: ------------------------------ Story Points: 13 > When an install fails, the user is able to view the error log to debug the cause of the failure, but the UI does not display any details > ---------------------------------------------------------------------------------------------------------------------------------------- > > Key: JBDS-3631 > URL: https://issues.jboss.org/browse/JBDS-3631 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Enhancement > Components: platform-installer > Reporter: Len DiMaggio > Assignee: Mohit Suman > Labels: havoc, ui > Fix For: 11.x > > Attachments: install_error.png > > > It would be helpful to provide the user either a summary of the last failure, or a window that displays the install log, inside the installer UI. Thx! -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-25127) Work to improve webtools releng

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-25127?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-25127: ------------------------------- Story Points: 100 Sprint: devex #139 October 2017 > Work to improve webtools releng > ------------------------------- > > Key: JBIDE-25127 > URL: https://issues.jboss.org/browse/JBIDE-25127 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: upstream > Affects Versions: 4.5.1.AM2 > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 4.5.x > > > Epic to track work done upstream at Eclipse for webtools project -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-25127) Work to improve webtools releng

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-25127?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-25127: ------------------------------- Component/s: build > Work to improve webtools releng > ------------------------------- > > Key: JBIDE-25127 > URL: https://issues.jboss.org/browse/JBIDE-25127 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build, upstream > Affects Versions: 4.5.1.AM2 > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 4.5.x > > > Epic to track work done upstream at Eclipse for webtools project -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24243) migrate Fuse Tools builds to JBT infrastructure/process

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24243?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-24243: ------------------------------- Sprint: devex #132 May 2017, devex #139 October 2017 (was: devex #132 May 2017, devex #138 September 2017) > migrate Fuse Tools builds to JBT infrastructure/process > ------------------------------------------------------- > > Key: JBIDE-24243 > URL: https://issues.jboss.org/browse/JBIDE-24243 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: build, fusetools, updatesite > Affects Versions: 4.5.0.AM1 > Reporter: Nick Boldt > Assignee: Lars Heinemann > Fix For: 4.5.x > > > Fuse Tooling currently has jobs under this view: https://fusesource-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/Fuse%20To... > * https://fusesource-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/Fuse%20To... -> http://download.jboss.org/jbosstools/neon/staging/builds/integration-stac... > ** https://fusesource-jenkins.rhev-ci-vms.eng.rdu2.redhat.com/view/Fuse%20To... -> http://download.jboss.org/jbosstools/neon/integration/updates/integration... > which publish integration, development or stable update sites. > As part of the migration of Fuse Tooling into JBoss Tools 4.5 for Oxygen, this path will change to something like: > * http://download.jboss.org/jbosstools/*oxygen*/snapshots/builds/fuse-tooling/ > * http://download.jboss.org/jbosstools/*oxygen*/staging/updates/fuse-tooling/ > We will also need to ensure that JBT composites/aggregates are configured to pick up these features/plugins. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24835) Remove integration tests checks from OpenShift, base and server and create Jenkins jobs for running integration tests on code changes

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24835?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-24835: ------------------------------- Sprint: devex #139 October 2017 (was: devex #138 September 2017) > Remove integration tests checks from OpenShift, base and server and create Jenkins jobs for running integration tests on code changes > ------------------------------------------------------------------------------------------------------------------------------------- > > Key: JBIDE-24835 > URL: https://issues.jboss.org/browse/JBIDE-24835 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: build > Affects Versions: 4.5.0.Final > Reporter: Pavol Srna > Assignee: Pavol Srna > Fix For: 4.5.1.Final > > -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24797) Code formatter: define and hook code formatting enforcement for github PRs

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24797?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-24797: ------------------------------- Sprint: devex #139 October 2017 (was: devex #138 September 2017) > Code formatter: define and hook code formatting enforcement for github PRs > -------------------------------------------------------------------------- > > Key: JBIDE-24797 > URL: https://issues.jboss.org/browse/JBIDE-24797 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: devdoc, hibernate, openshift, server > Affects Versions: 4.5.0.Final > Reporter: Andre Dietisheim > Assignee: Dmitrii Bocharov > Fix For: 4.5.x > > > Code formatting differs across developers. We should be at least consistent since odd formatting makes reading code more difficult for obvious reasons. > The most prominent differences I am aware of are > * use spaces vs tabs > * differences in formatting "if statements" (as displayed [here|https://github.com/jbosstools/jbosstools-openshift/pull/1536/files#d...]): > {code} > if(XX){ > {code} > vs > {code} > if (XX) { > {code} > * insonsitent code identations like displayed [here|https://github.com/jbosstools/jbosstools-openshift/pull/1535/files#d...]: > {code} > public void method() { > int i = 0; > i++; > i +=2; > {code} > * odd identations of whole anonymous classes as displayed [here|https://github.com/jbosstools/jbosstools-openshift/pull/1531/files#d...] > {code} > class Listener { > int i = 0; > public void method() { > } > } > {code} > * multiple empty lines for no obvious reason like shown [here|https://github.com/jbosstools/jbosstools-openshift/pull/1535/files#d...] > {code} > public class ZZ { > int i = 0; > i++ > } > {code} -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3631) When an install fails, the user is able to view the error log to debug the cause of the failure, but the UI does not display any details

by Mohit Suman (JIRA)

[ https://issues.jboss.org/browse/JBDS-3631?page=com.atlassian.jira.plugin.... ] Mohit Suman updated JBDS-3631: ------------------------------ Sprint: devex #139 October 2017 > When an install fails, the user is able to view the error log to debug the cause of the failure, but the UI does not display any details > ---------------------------------------------------------------------------------------------------------------------------------------- > > Key: JBDS-3631 > URL: https://issues.jboss.org/browse/JBDS-3631 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Enhancement > Components: platform-installer > Reporter: Len DiMaggio > Assignee: Mohit Suman > Labels: havoc, ui > Fix For: 11.x > > Attachments: install_error.png > > > It would be helpful to provide the user either a summary of the last failure, or a window that displays the install log, inside the installer UI. Thx! -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3631) When an install fails, the user is able to view the error log to debug the cause of the failure, but the UI does not display any details

by Mohit Suman (JIRA)

[ https://issues.jboss.org/browse/JBDS-3631?page=com.atlassian.jira.plugin.... ] Mohit Suman reassigned JBDS-3631: --------------------------------- Assignee: Mohit Suman (was: Denis Golovin) > When an install fails, the user is able to view the error log to debug the cause of the failure, but the UI does not display any details > ---------------------------------------------------------------------------------------------------------------------------------------- > > Key: JBDS-3631 > URL: https://issues.jboss.org/browse/JBDS-3631 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Enhancement > Components: platform-installer > Reporter: Len DiMaggio > Assignee: Mohit Suman > Labels: havoc, ui > Fix For: 11.x > > Attachments: install_error.png > > > It would be helpful to provide the user either a summary of the last failure, or a window that displays the install log, inside the installer UI. Thx! -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 6 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 October 2017