October 2017 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBDS-3837) Installer UI does not communicate errors to the user properly

by Mohit Suman (JIRA)

[ https://issues.jboss.org/browse/JBDS-3837?page=com.atlassian.jira.plugin.... ] Mohit Suman commented on JBDS-3837: ----------------------------------- We have implemented the error labels in the UI if any component fails with proper color coding. Hence closing this JIRA. > Installer UI does not communicate errors to the user properly > ------------------------------------------------------------- > > Key: JBDS-3837 > URL: https://issues.jboss.org/browse/JBDS-3837 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Bug > Components: platform-installer > Affects Versions: 9.1.0.CR1 > Reporter: Pavol Srna > Assignee: Denis Golovin > Labels: ui > Fix For: 11.x > > Attachments: screen-installer2.png > > > The installation has failed with no reason given. Please see screenshot attached. > We need to improve the UI too - If something fails the progress bar should be changed to red color etc. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3837) Installer UI does not communicate errors to the user properly

by Mohit Suman (JIRA)

[ https://issues.jboss.org/browse/JBDS-3837?page=com.atlassian.jira.plugin.... ] Mohit Suman closed JBDS-3837. ----------------------------- Resolution: Done > Installer UI does not communicate errors to the user properly > ------------------------------------------------------------- > > Key: JBDS-3837 > URL: https://issues.jboss.org/browse/JBDS-3837 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Bug > Components: platform-installer > Affects Versions: 9.1.0.CR1 > Reporter: Pavol Srna > Assignee: Denis Golovin > Labels: ui > Fix For: 11.x > > Attachments: screen-installer2.png > > > The installation has failed with no reason given. Please see screenshot attached. > We need to improve the UI too - If something fails the progress bar should be changed to red color etc. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-25170) Using empty profile in CDK 3.2+ server adapter should work with cdk's default profile (minishift)

by Ondrej Dockal (JIRA)

[ https://issues.jboss.org/browse/JBIDE-25170?page=com.atlassian.jira.plugi... ] Ondrej Dockal commented on JBIDE-25170: --------------------------------------- [~rob.stryker], it is "minishift", isn't it? But let's wait for [~kumarpraveen] to confirm. > Using empty profile in CDK 3.2+ server adapter should work with cdk's default profile (minishift) > ------------------------------------------------------------------------------------------------- > > Key: JBIDE-25170 > URL: https://issues.jboss.org/browse/JBIDE-25170 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: cdk > Affects Versions: 4.5.1.AM3 > Reporter: Ondrej Dockal > Assignee: Rob Stryker > Fix For: 4.5.1.Final > > > I have two running CDK 3.2+ server adapters, and if I operate the one where profile is not defined (I would expect that it is set to default one aka 'minishift') it works with actually active profile. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-25042) Server New and Noteworthy for 4.5.1.AM3

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-25042?page=com.atlassian.jira.plugi... ] Rob Stryker commented on JBIDE-25042: ------------------------------------- double-checked. Nothing here > Server New and Noteworthy for 4.5.1.AM3 > --------------------------------------------------- > > Key: JBIDE-25042 > URL: https://issues.jboss.org/browse/JBIDE-25042 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: archives, jmx, server > Reporter: Jeff MAURY > Assignee: Rob Stryker > Priority: Critical > Labels: task > Fix For: 4.5.1.AM3 > > > Rob Stryker, > Search for your component's New and Noteworthy issues: > Queries: > * [Completed Server JIRAs marked N&N|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and+...] > * [All Completed JIRAs marked N&N|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and+...] > * [N&N Task JIRAs for this milestone|https://issues.jboss.org/issues/?jql=summary+%7E+%22New+and+Not...] > * [All N&N Task JIRAs|https://issues.jboss.org/issues/?jql=summary+%7E+%22New+and+Notewor...] > If no N&N issues are found for Server, check if there are issues that SHOULD have been labelled with *Labels =* _new_and_noteworthy_, and add them. > Document the ones relevant for Server by submitting a pull request against: > * https://github.com/jbosstools/jbosstools-website/tree/master/documentatio... > If your PR's commit comment is of the form... {code}JBIDE-25020 #comment Create N&N for Server 4.5.1.AM3 #close{code}... and your github user's email address is the same as your JIRA one, then this JIRA should be closed automatically when the PR is applied. > If there is nothing new or noteworthy for Server for this milestone, please *reject* and *close* this issue. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-25170) Using empty profile in CDK 3.2+ server adapter should work with cdk's default profile (minishift)

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-25170?page=com.atlassian.jira.plugi... ] Rob Stryker updated JBIDE-25170: -------------------------------- Fix Version/s: 4.5.1.Final > Using empty profile in CDK 3.2+ server adapter should work with cdk's default profile (minishift) > ------------------------------------------------------------------------------------------------- > > Key: JBIDE-25170 > URL: https://issues.jboss.org/browse/JBIDE-25170 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: cdk > Affects Versions: 4.5.1.AM3 > Reporter: Ondrej Dockal > Assignee: Rob Stryker > Fix For: 4.5.1.Final > > > I have two running CDK 3.2+ server adapters, and if I operate the one where profile is not defined (I would expect that it is set to default one aka 'minishift') it works with actually active profile. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-25131) Expand credentials API to allow different credential types

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-25131?page=com.atlassian.jira.plugi... ] Rob Stryker updated JBIDE-25131: -------------------------------- Fix Version/s: 4.5.2.AM1 > Expand credentials API to allow different credential types > ---------------------------------------------------------- > > Key: JBIDE-25131 > URL: https://issues.jboss.org/browse/JBIDE-25131 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: foundation > Affects Versions: 4.5.1.AM2 > Reporter: Rob Stryker > Assignee: Rob Stryker > Fix For: 4.5.2.AM1 > > > The Credentials API is pretty much restricted to a simple user/pass combination. This may be insufficient for the needs of the future. Make something more extendable ;) -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-24960) JBDS 11 produces warnings about missing schemas inconsistently

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-24960?page=com.atlassian.jira.plugi... ] Rob Stryker commented on JBIDE-24960: ------------------------------------- [~aurelien.pupier] recent updates added the schemas. Is this still replicatable? [~mmalina] Can you check? > JBDS 11 produces warnings about missing schemas inconsistently > -------------------------------------------------------------- > > Key: JBIDE-24960 > URL: https://issues.jboss.org/browse/JBIDE-24960 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: jsp/jsf/xml/html-source-editing > Affects Versions: 4.5.0.Final > Reporter: Michal Jurc > Assignee: Rob Stryker > Fix For: 4.5.1.Final > > > The following warning is produced by JBDS11 consistently upon import of {{ejb-security-jaas}} quickstart: > ||Description||Resource||Path||Location||Type|| > |No grammar constraints (DTD or XML Schema) referenced in the document.|wildfly-config.xml|/ejb-security-jaas/src/main/resources|line 1|XML Problem| > The {{ejb-remote}} quickstart uses the same configuration file ({{wildfly-config.xml}}), however no such warning is produced unless the user selects the file to validate it. > This is inconsistent, confusing and it is not at all obvious where the JBDS is taking schemas from - after all, {{wildlfy-config.xml}} is standard descriptor file for any application using Elytron client with EAP7.1. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-25168) cdk 3.2+ is tech preview in one place and not in another

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-25168?page=com.atlassian.jira.plugi... ] Rob Stryker resolved JBIDE-25168. --------------------------------- Resolution: Done commit e7c1072ad776f3b5e00cfdfd99953f5862aec23d Author: Rob Stryker <rob(a)oxbeef.net> Date: Wed Oct 11 20:02:11 2017 -0400 > cdk 3.2+ is tech preview in one place and not in another > -------------------------------------------------------- > > Key: JBIDE-25168 > URL: https://issues.jboss.org/browse/JBIDE-25168 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: cdk > Affects Versions: 4.5.1.AM3 > Reporter: Martin Malina > Assignee: Rob Stryker > Fix For: 4.5.1.Final > > > Currently for AM3, the new cdk 3.2+ runtime detector is listed as Tech Preview (as seen in Preferences -> JBoss Runtime Detection). But the server adapter does not say Tech Preview (as seen in New Server wizard). > These two should be consistent, no? Ideally both should say tech preview. > But... since this won't be fixed for AM3, what happens next? The adapter should no longer be Tech Preview for JBT 4.5.1.Final, right? Because CDK 3.2 will be released at the same time and then 3.1 will be no longer maintained. Yes, the profiles may not be fully supported, but the server adapter as a whole should be supported. > So it's quite likely that this will be Out of date before it can be fixed - the adapter/detector will no longer be tech preview. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-25020) Create New and Noteworthy for 4.5.1.AM3

by Jeff MAURY (JIRA)

[ https://issues.jboss.org/browse/JBIDE-25020?page=com.atlassian.jira.plugi... ] Jeff MAURY closed JBIDE-25020. ------------------------------ Resolution: Done > Create New and Noteworthy for 4.5.1.AM3 > --------------------------------------- > > Key: JBIDE-25020 > URL: https://issues.jboss.org/browse/JBIDE-25020 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: website > Reporter: Jeff MAURY > Assignee: Jeff MAURY > Priority: Blocker > Labels: task > Fix For: 4.5.1.AM3 > > > This [query|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+an...] contains the search for all N&N. See subtasks below. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-25042) Server New and Noteworthy for 4.5.1.AM3

by Jeff MAURY (JIRA)

[ https://issues.jboss.org/browse/JBIDE-25042?page=com.atlassian.jira.plugi... ] Jeff MAURY closed JBIDE-25042. ------------------------------ Resolution: Rejected > Server New and Noteworthy for 4.5.1.AM3 > --------------------------------------------------- > > Key: JBIDE-25042 > URL: https://issues.jboss.org/browse/JBIDE-25042 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: archives, jmx, server > Reporter: Jeff MAURY > Assignee: Rob Stryker > Priority: Critical > Labels: task > Fix For: 4.5.1.AM3 > > > Rob Stryker, > Search for your component's New and Noteworthy issues: > Queries: > * [Completed Server JIRAs marked N&N|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and+...] > * [All Completed JIRAs marked N&N|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and+...] > * [N&N Task JIRAs for this milestone|https://issues.jboss.org/issues/?jql=summary+%7E+%22New+and+Not...] > * [All N&N Task JIRAs|https://issues.jboss.org/issues/?jql=summary+%7E+%22New+and+Notewor...] > If no N&N issues are found for Server, check if there are issues that SHOULD have been labelled with *Labels =* _new_and_noteworthy_, and add them. > Document the ones relevant for Server by submitting a pull request against: > * https://github.com/jbosstools/jbosstools-website/tree/master/documentatio... > If your PR's commit comment is of the form... {code}JBIDE-25020 #comment Create N&N for Server 4.5.1.AM3 #close{code}... and your github user's email address is the same as your JIRA one, then this JIRA should be closed automatically when the PR is applied. > If there is nothing new or noteworthy for Server for this milestone, please *reject* and *close* this issue. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 5 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