June 2016 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-22115) Connection wizard: Truncated error message display connecting to server

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22115?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-22115: ------------------------------------- Fix Version/s: 4.4.1.Alpha1 (was: 4.4.x) > Connection wizard: Truncated error message display connecting to server > ----------------------------------------------------------------------- > > Key: JBIDE-22115 > URL: https://issues.jboss.org/browse/JBIDE-22115 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.1.Final > Environment: Version: 9.1.0.GA > Build id: GA-v20160403-1700-B477 > Build date: 20160403-1700 > Reporter: Len DiMaggio > Assignee: Jeff MAURY > Priority: Minor > Labels: connection_wizard, openshift_v3 > Fix For: 4.4.1.Alpha1 > > Attachments: bad_token_1.png, bad_token_2.png, use-basic-insteadof-oauth.png, use-oauth-insteadof-basic.png > > > See attached screenshot - the error message is truncated until the user expands the width of the dialog. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22115) Connection wizard: Truncated error message display connecting to server

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22115?page=com.atlassian.jira.plugi... ] Andre Dietisheim commented on JBIDE-22115: ------------------------------------------ merged into master > Connection wizard: Truncated error message display connecting to server > ----------------------------------------------------------------------- > > Key: JBIDE-22115 > URL: https://issues.jboss.org/browse/JBIDE-22115 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.1.Final > Environment: Version: 9.1.0.GA > Build id: GA-v20160403-1700-B477 > Build date: 20160403-1700 > Reporter: Len DiMaggio > Assignee: Jeff MAURY > Priority: Minor > Labels: connection_wizard, openshift_v3 > Fix For: 4.4.x > > Attachments: bad_token_1.png, bad_token_2.png, use-basic-insteadof-oauth.png, use-oauth-insteadof-basic.png > > > See attached screenshot - the error message is truncated until the user expands the width of the dialog. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22115) Connection wizard: Truncated error message display connecting to server

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22115?page=com.atlassian.jira.plugi... ] Andre Dietisheim commented on JBIDE-22115: ------------------------------------------ The basic reason for the additional info in front of the server provided message was to help the user. Nowadays errors seem good enough: ex. if you use the wrong auth methods * use basic auth where oauth is required: !use-basic-insteadof-oauth.png! * use oauth where basic is required: * !use-oauth-insteadof-basic.png! > Connection wizard: Truncated error message display connecting to server > ----------------------------------------------------------------------- > > Key: JBIDE-22115 > URL: https://issues.jboss.org/browse/JBIDE-22115 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.1.Final > Environment: Version: 9.1.0.GA > Build id: GA-v20160403-1700-B477 > Build date: 20160403-1700 > Reporter: Len DiMaggio > Assignee: Jeff MAURY > Priority: Minor > Labels: connection_wizard, openshift_v3 > Fix For: 4.4.x > > Attachments: bad_token_1.png, bad_token_2.png, use-basic-insteadof-oauth.png, use-oauth-insteadof-basic.png > > > See attached screenshot - the error message is truncated until the user expands the width of the dialog. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22115) Connection wizard: Truncated error message display connecting to server

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22115?page=com.atlassian.jira.plugi... ] Andre Dietisheim edited comment on JBIDE-22115 at 6/16/16 5:18 AM: ------------------------------------------------------------------- The basic reason for the additional info in front of the server provided message was to help the user. Nowadays errors seem good enough: ex. if you use the wrong auth methods * use basic auth where oauth is required: !use-basic-insteadof-oauth.png! * use oauth where basic is required: !use-oauth-insteadof-basic.png! was (Author: adietish): The basic reason for the additional info in front of the server provided message was to help the user. Nowadays errors seem good enough: ex. if you use the wrong auth methods * use basic auth where oauth is required: !use-basic-insteadof-oauth.png! * use oauth where basic is required: * !use-oauth-insteadof-basic.png! > Connection wizard: Truncated error message display connecting to server > ----------------------------------------------------------------------- > > Key: JBIDE-22115 > URL: https://issues.jboss.org/browse/JBIDE-22115 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.1.Final > Environment: Version: 9.1.0.GA > Build id: GA-v20160403-1700-B477 > Build date: 20160403-1700 > Reporter: Len DiMaggio > Assignee: Jeff MAURY > Priority: Minor > Labels: connection_wizard, openshift_v3 > Fix For: 4.4.x > > Attachments: bad_token_1.png, bad_token_2.png, use-basic-insteadof-oauth.png, use-oauth-insteadof-basic.png > > > See attached screenshot - the error message is truncated until the user expands the width of the dialog. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22115) Connection wizard: Truncated error message display connecting to server

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22115?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-22115: ------------------------------------- Attachment: use-oauth-insteadof-basic.png use-basic-insteadof-oauth.png > Connection wizard: Truncated error message display connecting to server > ----------------------------------------------------------------------- > > Key: JBIDE-22115 > URL: https://issues.jboss.org/browse/JBIDE-22115 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.1.Final > Environment: Version: 9.1.0.GA > Build id: GA-v20160403-1700-B477 > Build date: 20160403-1700 > Reporter: Len DiMaggio > Assignee: Jeff MAURY > Priority: Minor > Labels: connection_wizard, openshift_v3 > Fix For: 4.4.x > > Attachments: bad_token_1.png, bad_token_2.png, use-basic-insteadof-oauth.png, use-oauth-insteadof-basic.png > > > See attached screenshot - the error message is truncated until the user expands the width of the dialog. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21290) CDK 2 is detected as version 1.0

by Martin Malina (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21290?page=com.atlassian.jira.plugi... ] Martin Malina commented on JBIDE-21290: --------------------------------------- {code} Support in which sense? Then we don't document how to do it? {code} Yes, it's not documented. And it depends what exactly is new in a newer version. If the plugins, you can easily upgrade them. If the Vagrantfile, you can just start using it. If it's the vagrant box, then I don't know how you can update your existing box to the new one. > CDK 2 is detected as version 1.0 > -------------------------------- > > Key: JBIDE-21290 > URL: https://issues.jboss.org/browse/JBIDE-21290 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: cdk, runtime-detection, upstream > Affects Versions: 4.3.1.Beta1 > Reporter: Martin Malina > Assignee: Rob Stryker > Priority: Minor > Fix For: 4.4.x > > Attachments: cdk-runtime-detection.png, Screenshot 2016-01-07 09.16.12.png > > > When you detect CDK using runtime detection, it will show you the name cdk-v2 which clearly shows it's version 2 (this is actually just based on the folder it seems). But the Version column says Version 1.0. > !cdk-runtime-detection.png! > Could we change it to version 2? > I know that this probably doesn't have any meaning right now - I noticed there is no runtime anymore, so the version is nowhere to be seen once you create the cdk server adapter. But it would still be nicer to show the correct version if possible. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21382) remove dependency from o.j.t.common.model.ui to org.eclipse.core.runtime.compatibility_3.2.300.v20150423-0821 (removed from Neon in M3)

by Martin Malina (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21382?page=com.atlassian.jira.plugi... ] Martin Malina closed JBIDE-21382. --------------------------------- This plugin is now gone, but there is still org.eclipse.core.runtime.compatibility.auth - I created JBIDE-22602 to check if that should be removed also. Closing. > remove dependency from o.j.t.common.model.ui to org.eclipse.core.runtime.compatibility_3.2.300.v20150423-0821 (removed from Neon in M3) > --------------------------------------------------------------------------------------------------------------------------------------- > > Key: JBIDE-21382 > URL: https://issues.jboss.org/browse/JBIDE-21382 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: common/jst/core > Affects Versions: 4.4.0.Alpha1 > Reporter: Nick Boldt > Assignee: Nick Boldt > Priority: Blocker > Fix For: 4.4.0.Final > > > org.eclipse.core.runtime.compatibility 3.2.300.v20150423-0821 was removed from Neon as of M3. It is required by these IUs: > * o.j.t.common.model.ui, > * o.e.platform.feature, > * o.e.m2e.feature, > * o.e.datatools.oda.cshelp, > * o.aspectj.ajde, > * o.e.wst.xml.xpath.core, and > * o.e.birt.feature -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3929) Tweaks to content.xml / artifacts.xml lost (regression)

by Jan Richter (JIRA)

[ https://issues.jboss.org/browse/JBDS-3929?page=com.atlassian.jira.plugin.... ] Jan Richter closed JBDS-3929. ----------------------------- As of respin-b neither https://devstudio.redhat.com/10.0/staging/updates/ nor http://download.jboss.org/jbosstools/neon/staging/updates/ display the uncategorized category, closing. > Tweaks to content.xml / artifacts.xml lost (regression) > ------------------------------------------------------- > > Key: JBDS-3929 > URL: https://issues.jboss.org/browse/JBDS-3929 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Bug > Components: updatesite > Affects Versions: 10.0.0.GA > Reporter: Andrej Podhradsky > Assignee: Nick Boldt > Priority: Blocker > Labels: respin-b > Fix For: 10.0.0.GA > > Attachments: jbds-update-no-uncatg.png, jbt-uncat.png, jbt-update-no-uncatg.png, uncategorized_20160614.png > > > The category 'Uncategorized' is on the following update site > https://devstudio.redhat.com/10.0/staging/updates/ > Note that this category contains source features which should not be in any category. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3936) devstudio.exe has eclipse icon

by Jan Richter (JIRA)

[ https://issues.jboss.org/browse/JBDS-3936?page=com.atlassian.jira.plugin.... ] Jan Richter closed JBDS-3936. ----------------------------- Verified with 10.0.0.GA-b. > devstudio.exe has eclipse icon > ------------------------------ > > Key: JBDS-3936 > URL: https://issues.jboss.org/browse/JBDS-3936 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Bug > Components: installer > Affects Versions: 10.0.0.GA > Reporter: Radim Hopp > Assignee: Nick Boldt > Priority: Blocker > Labels: respin-b > Fix For: 10.0.0.GA > > Attachments: devstudio.ico.10.png, jbds.ico.9.1.png, jbds.ico.9.1export-layers.png, jbds.ico_vs_devstudio.ico.png > > > [installFolder]/studio/devstudio.exe has eclipse icon instead of redhat developer icon. > http://i.imgur.com/ZKjeJGC.png -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22608) Support scenario when cdk is stopped from cli and then in devstudio

by Martin Malina (JIRA)

Martin Malina created JBIDE-22608: ------------------------------------- Summary: Support scenario when cdk is stopped from cli and then in devstudio Key: JBIDE-22608 URL: https://issues.jboss.org/browse/JBIDE-22608 Project: Tools (JBoss Tools) Issue Type: Feature Request Components: cdk Affects Versions: 4.4.0.Final Reporter: Martin Malina Assignee: Rob Stryker Assume your cdk is started and it's shown as started in devstudio, now what if you stop cdk from cli for whatever reason? Currently the tooling can't handle such situation. If you then try to stop cdk in devstudio, you get an error pop-up: Server Container Development Environment failed to stop. And the console will just say: ==> default: VM not created. Moving on... But most importantly, the server adapter will stay in the Started state. We should probably support this scenario - it's quite likely that it will happen to users. Right now there are several ways out of this situation: a) Start cdk from cli again and everything will probably work as expected b) Restart your IDE So I suggest we improve the tooling in such a way that when you stop cdk, it will be able to detect that it's actually not running and just change the state to Stopped. It may be still ok to pop up the error saying it failed to stop. But at least you can now start it again from the IDE. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 9 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 June 2016