September 2016 - jbosstools-issues

[JBoss JIRA] (JBDS-4062) Error about space in User's Profile location (home) folder should be reported on confirmation page

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBDS-4062?page=com.atlassian.jira.plugin.... ] Denis Golovin updated JBDS-4062: -------------------------------- Component/s: platform-installer > Error about space in User's Profile location (home) folder should be reported on confirmation page > -------------------------------------------------------------------------------------------------- > > Key: JBDS-4062 > URL: https://issues.jboss.org/browse/JBDS-4062 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Bug > Components: platform-installer > Reporter: Denis Golovin > -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3627) Installer needs to help move past lack of t/c signing

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBDS-3627?page=com.atlassian.jira.plugin.... ] Denis Golovin resolved JBDS-3627. --------------------------------- Resolution: Done > Installer needs to help move past lack of t/c signing > ----------------------------------------------------- > > Key: JBDS-3627 > URL: https://issues.jboss.org/browse/JBDS-3627 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Epic > Components: platform-installer > Affects Versions: 10.0.0.GA > Reporter: Joshua Wilson > Assignee: Denis Golovin > Labels: havoc > Fix For: 10.2.0.GA > > Attachments: Installer-not-signed-tc.PNG > > > DevSuite installer uses "REST services in JBoss Download Manager" explained here https://mojo.redhat.com/docs/DOC-940689. > DevSuite Intsaller follows the explanation for tc-accepted entry point [code is here|https://github.com/redhat-developer-tooling/developer-platform-insta...]. It uses file from previous CDK release (published in cdn and available through download manager) to do verification: > 1. that provided credentials are valid; > 2. that required T&C's are signed. > There are two major use cases for developers installing DevSuite using Installer: > 1. Direct download - when developer sign in to developers.redhat.com and download installer himeslf; > 2. Shared installer - when someone share installer with developers without account. > There two kind of users involved in those scenarios above: > 1. New users that must go through registration process; > 2. Registered users. > *Direct download* > For new ones registration process is really simple now. After creating RHD account and downloading installer there is no additional steps to get through installation. > For already registered users there could be problems related to T&C's and authentication reported here https://issues.jboss.org/browse/RHDENG-579. > So far there are two kind of problems: > 1. Users can login and download DevSuite installer, but cannot use the same credentials to install; > 2. Users that can login in to developers.redhat.com and get request to sign additional T&C's but credentials for the same user in DevSuite Installer reported as invalid when REST tc-accepted entry point is used > *Shared Download* > In this scenario new users without account can press Register link, then go through registration process in browser return back to installer and use new account credentials for installation. > Registered users could need to sign additional T&C's if missing and would be good to show external link to do so. Current entry point tc-accepted does not provide any hints where missing T&C's could be signed. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3627) Installer needs to help move past lack of t/c signing

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBDS-3627?page=com.atlassian.jira.plugin.... ] Denis Golovin updated JBDS-3627: -------------------------------- Sprint: devex #120 September 2016 (was: devex #121 September 2016) > Installer needs to help move past lack of t/c signing > ----------------------------------------------------- > > Key: JBDS-3627 > URL: https://issues.jboss.org/browse/JBDS-3627 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Epic > Components: platform-installer > Affects Versions: 10.0.0.GA > Reporter: Joshua Wilson > Assignee: Denis Golovin > Labels: havoc > Fix For: 10.2.0.GA > > Attachments: Installer-not-signed-tc.PNG > > > DevSuite installer uses "REST services in JBoss Download Manager" explained here https://mojo.redhat.com/docs/DOC-940689. > DevSuite Intsaller follows the explanation for tc-accepted entry point [code is here|https://github.com/redhat-developer-tooling/developer-platform-insta...]. It uses file from previous CDK release (published in cdn and available through download manager) to do verification: > 1. that provided credentials are valid; > 2. that required T&C's are signed. > There are two major use cases for developers installing DevSuite using Installer: > 1. Direct download - when developer sign in to developers.redhat.com and download installer himeslf; > 2. Shared installer - when someone share installer with developers without account. > There two kind of users involved in those scenarios above: > 1. New users that must go through registration process; > 2. Registered users. > *Direct download* > For new ones registration process is really simple now. After creating RHD account and downloading installer there is no additional steps to get through installation. > For already registered users there could be problems related to T&C's and authentication reported here https://issues.jboss.org/browse/RHDENG-579. > So far there are two kind of problems: > 1. Users can login and download DevSuite installer, but cannot use the same credentials to install; > 2. Users that can login in to developers.redhat.com and get request to sign additional T&C's but credentials for the same user in DevSuite Installer reported as invalid when REST tc-accepted entry point is used > *Shared Download* > In this scenario new users without account can press Register link, then go through registration process in browser return back to installer and use new account credentials for installation. > Registered users could need to sign additional T&C's if missing and would be good to show external link to do so. Current entry point tc-accepted does not provide any hints where missing T&C's could be signed. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3978) Getting started page shows guide for Devstudio 9.x

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBDS-3978?page=com.atlassian.jira.plugin.... ] Denis Golovin updated JBDS-3978: -------------------------------- Sprint: devex #120 September 2016 (was: devex #121 September 2016) > Getting started page shows guide for Devstudio 9.x > -------------------------------------------------- > > Key: JBDS-3978 > URL: https://issues.jboss.org/browse/JBDS-3978 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Bug > Components: platform-installer > Affects Versions: 10.1.0.AM2 > Reporter: Jan Richter > Assignee: Denis Golovin > Priority: Minor > Fix For: 10.1.0.GA > > > The getting started link in devsuite leads to http://developers.redhat.com/devstudio-preview which redirects to https://access.redhat.com/articles/2255401 > The very fact that it is named > {noformat}Using JBoss Developer Studio 9.x's Container Development Kit Tooling {noformat} - refers to CDK 2.0 and JBoss Developer Studio 9.0 - looks suspicious. There might not be much difference to the current workflow, but it definitely is worth updating, especially since the devsuite installer is no longer a Technology Preview. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3978) Getting started page shows guide for Devstudio 9.x

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBDS-3978?page=com.atlassian.jira.plugin.... ] Denis Golovin resolved JBDS-3978. --------------------------------- Resolution: Done > Getting started page shows guide for Devstudio 9.x > -------------------------------------------------- > > Key: JBDS-3978 > URL: https://issues.jboss.org/browse/JBDS-3978 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Bug > Components: platform-installer > Affects Versions: 10.1.0.AM2 > Reporter: Jan Richter > Assignee: Denis Golovin > Priority: Minor > Fix For: 10.1.0.GA > > > The getting started link in devsuite leads to http://developers.redhat.com/devstudio-preview which redirects to https://access.redhat.com/articles/2255401 > The very fact that it is named > {noformat}Using JBoss Developer Studio 9.x's Container Development Kit Tooling {noformat} - refers to CDK 2.0 and JBoss Developer Studio 9.0 - looks suspicious. There might not be much difference to the current workflow, but it definitely is worth updating, especially since the devsuite installer is no longer a Technology Preview. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23267) New application created by JBDS cannot specify "medium" or "large" size.

by Kenjiro Nakayama (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23267?page=com.atlassian.jira.plugi... ] Kenjiro Nakayama updated JBIDE-23267: ------------------------------------- Description: * New application created by JBDS cannot specify "medium" or "large" size. * NOTE: This issue is critical if the users environment doesn't allow to create small gears. Since they cannot create any application via JBDS. was:* New application created by JBDS cannot specify "medium" or "large" size. > New application created by JBDS cannot specify "medium" or "large" size. > ------------------------------------------------------------------------ > > Key: JBIDE-23267 > URL: https://issues.jboss.org/browse/JBIDE-23267 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Environment: * All versions > * I confirmed with latest version devstudio-10.0.0.GA-installer-standalone.jar > Reporter: Kenjiro Nakayama > Priority: Critical > > * New application created by JBDS cannot specify "medium" or "large" size. > * NOTE: This issue is critical if the users environment doesn't allow to create small gears. Since they cannot create any application via JBDS. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23267) New application created by JBDS cannot specify "medium" or "large" size.

by Kenjiro Nakayama (JIRA)

Kenjiro Nakayama created JBIDE-23267: ---------------------------------------- Summary: New application created by JBDS cannot specify "medium" or "large" size. Key: JBIDE-23267 URL: https://issues.jboss.org/browse/JBIDE-23267 Project: Tools (JBoss Tools) Issue Type: Bug Components: openshift Environment: * All versions * I confirmed with latest version devstudio-10.0.0.GA-installer-standalone.jar Reporter: Kenjiro Nakayama Priority: Critical * New application created by JBDS cannot specify "medium" or "large" size. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21611) Reduce bloat in CDK server adapter menus

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21611?page=com.atlassian.jira.plugi... ] Rob Stryker resolved JBIDE-21611. --------------------------------- Fix Version/s: 4.4.2.AM1 (was: 4.4.x) Resolution: Won't Fix The server log stuff will be removed in jbt 4.5 The show in -> web browser will remain for consistency with other server adapters. We can get into a whole debate over whether removing the action is worth changing whole bunches of api when simply disabling it is the current behavior, but I'd rather not waste time debating something so trivial for only 1 action. I realize it seems bloated for people who haven't used server adapters, but there's very little we can do here. 90% of the actions are contributed by WTP. > Reduce bloat in CDK server adapter menus > ---------------------------------------- > > Key: JBIDE-21611 > URL: https://issues.jboss.org/browse/JBIDE-21611 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: cdk > Affects Versions: 4.3.1.Beta2 > Reporter: Fred Bricon > Assignee: Rob Stryker > Priority: Minor > Fix For: 4.4.2.AM1 > > Attachments: cdk-server-menus.png > > > The CDK server adapter menus display a lot of useless/disabled menus: > !cdk-server-menus.png|width=650! > It'd be nice to clean that up. Keep > -(re)start > -stop > -Show in> OpenShift, Docker > -Delete > -rename > -properties > It reckon it might not be possible to get rid of all the cruft (when menus are defined upstream), but we might be able to clean some of the menus we "own". -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23023) Valiadation of credentials does not work for some runtimes in Download Runtime Wizard

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23023?page=com.atlassian.jira.plugi... ] Rob Stryker updated JBIDE-23023: -------------------------------- Sprint: devex #121 October 2016 > Valiadation of credentials does not work for some runtimes in Download Runtime Wizard > ------------------------------------------------------------------------------------- > > Key: JBIDE-23023 > URL: https://issues.jboss.org/browse/JBIDE-23023 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: runtime-detection > Affects Versions: 4.4.1.AM3 > Environment: Devstudio 10.1.0.AM3-v20160819-0530-B5800 > Reporter: Radim Hopp > Assignee: Rob Stryker > Priority: Critical > > Valiadation of username and password in DownloadRuntimesWizard does not work for JBoss EAP 6.0 to 6.2 and JBoss Portal Platform 6.1.0. It does work for JBoss EAP 6.3 to 7.0, JBoss FSW 6.0, JBoss Data Virtualization 6.1.0 and 6.2.0. > For the mentioned runtimes, where it does not work it lets you accept license, but fails on download. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-9720) Issues when starting and stopping an EAP or SOA-P server using -Djboss.service.binding.set=ports-03 in JBDS

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-9720?page=com.atlassian.jira.plugin... ] Rob Stryker resolved JBIDE-9720. -------------------------------- Resolution: Won't Fix Unfortunately this is 100% a wont-fix. We do have a jira open to allow users who change port settings in the server editor to also go and pass those flags to jboss. But we definitely will not parse the user-customized vm args to look for changes and change our UI for that. It could create a circular loop and lead to each part trying to update the other. > Issues when starting and stopping an EAP or SOA-P server using -Djboss.service.binding.set=ports-03 in JBDS > ----------------------------------------------------------------------------------------------------------- > > Key: JBIDE-9720 > URL: https://issues.jboss.org/browse/JBIDE-9720 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: server > Reporter: Debbie Steigner > Assignee: Rob Stryker > Priority: Minor > Fix For: LATER > > Original Estimate: 0 minutes > Remaining Estimate: 0 minutes > > Changed my open launch configuration for SOA-P v5.1 to use ports-03(-Djboss.service.binding.set=ports-03). When starting the server, the server starts successfully, but on the lower right hand side of the JBDS IDE, the message "Starting JBoss Server...." does not remove itself once the server has successfully started. Also, when attempting to shutdown the server from the JBDS IDE, the server aborts abruptly, an error dialog is created stating to look at the log for more errors. Using the default ports, the server behavior for starting and shutdown works successfully with no errors. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 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 September 2016