September 2016 - jbosstools-issues

[JBoss JIRA] (ERT-409) Content assist doesn't work for bower/npm [EBZ#500805]

by Gorkem Ercan (JIRA)

[ https://issues.jboss.org/browse/ERT-409?page=com.atlassian.jira.plugin.sy... ] Gorkem Ercan closed ERT-409. ---------------------------- Resolution: Done > Content assist doesn't work for bower/npm [EBZ#500805] > ------------------------------------------------------- > > Key: ERT-409 > URL: https://issues.jboss.org/browse/ERT-409 > Project: Eclipse Release Train > Issue Type: Task > Components: WTP Source Editing > Reporter: Friendly Jira Robot > Labels: bzira, wst.json > > CA doesn't recognize a schema file in a jarred plugins. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23127) blog about the improvements RH Eclipse teams did to Neon

by Mickael Istria (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23127?page=com.atlassian.jira.plugi... ] Mickael Istria commented on JBIDE-23127: ---------------------------------------- [~lincolnthree] When the post is ready, I just hit "Submit for Review", right? > blog about the improvements RH Eclipse teams did to Neon > -------------------------------------------------------- > > Key: JBIDE-23127 > URL: https://issues.jboss.org/browse/JBIDE-23127 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: website > Reporter: Max Rydahl Andersen > Assignee: Mickael Istria > > Neon is out and we did a lot of great stuff in the platform > around smart import, auto download of extensions, zoom, etc. > I thought it would be great to do a blog posting about this work > on tools.jboss.org for the Eclipse Neon release > Audience: users of Eclipse and making internal and external to Red Hat aware of the improvements made. > The target would be http://developers.redhat.com/blog > _The following is the current ToC of the blog, it's going to evolve as content is gathered_ > Neon.0: > * JavaScript plugins and “Eclipse for JavaScript Developers” package > * JSon Editor > * Docker Tools > * Vagrant Tools > * Smarter and easier Import of projects in the IDE > * Zoom In/Out with Ctrl+/Ctrl- in text editors > * Discovery and proposal of Marketplace extensions for unknown file types > * SWT on GTK3 > * Theming off > For Neon.1 - released September 28th: > * More Docker: https://wiki.eclipse.org/Linux_Tools_Project/News/NewIn51 > * Image viewer in the Eclipse IDE > For Eclipse Oxygen, next major release to be shipped in June 2018, here are our plans: > * generic and extensible code editor > * Integration with the language server protocol > * UI/UX efforts -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23127) blog about the improvements RH Eclipse teams did to Neon

by Martha Benitez (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23127?page=com.atlassian.jira.plugi... ] Martha Benitez commented on JBIDE-23127: ---------------------------------------- Reviewed and discussed on IRC. > blog about the improvements RH Eclipse teams did to Neon > -------------------------------------------------------- > > Key: JBIDE-23127 > URL: https://issues.jboss.org/browse/JBIDE-23127 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: website > Reporter: Max Rydahl Andersen > Assignee: Mickael Istria > > Neon is out and we did a lot of great stuff in the platform > around smart import, auto download of extensions, zoom, etc. > I thought it would be great to do a blog posting about this work > on tools.jboss.org for the Eclipse Neon release > Audience: users of Eclipse and making internal and external to Red Hat aware of the improvements made. > The target would be http://developers.redhat.com/blog > _The following is the current ToC of the blog, it's going to evolve as content is gathered_ > Neon.0: > * JavaScript plugins and “Eclipse for JavaScript Developers” package > * JSon Editor > * Docker Tools > * Vagrant Tools > * Smarter and easier Import of projects in the IDE > * Zoom In/Out with Ctrl+/Ctrl- in text editors > * Discovery and proposal of Marketplace extensions for unknown file types > * SWT on GTK3 > * Theming off > For Neon.1 - released September 28th: > * More Docker: https://wiki.eclipse.org/Linux_Tools_Project/News/NewIn51 > * Image viewer in the Eclipse IDE > For Eclipse Oxygen, next major release to be shipped in June 2018, here are our plans: > * generic and extensible code editor > * Integration with the language server protocol > * UI/UX efforts -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23127) blog about the improvements RH Eclipse teams did to Neon

by Mickael Istria (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23127?page=com.atlassian.jira.plugi... ] Mickael Istria commented on JBIDE-23127: ---------------------------------------- [~mbenitez]: Did you have the opportunity to review the blog proposal? Should I try to publish it now? > blog about the improvements RH Eclipse teams did to Neon > -------------------------------------------------------- > > Key: JBIDE-23127 > URL: https://issues.jboss.org/browse/JBIDE-23127 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: website > Reporter: Max Rydahl Andersen > Assignee: Mickael Istria > > Neon is out and we did a lot of great stuff in the platform > around smart import, auto download of extensions, zoom, etc. > I thought it would be great to do a blog posting about this work > on tools.jboss.org for the Eclipse Neon release > Audience: users of Eclipse and making internal and external to Red Hat aware of the improvements made. > The target would be http://developers.redhat.com/blog > _The following is the current ToC of the blog, it's going to evolve as content is gathered_ > Neon.0: > * JavaScript plugins and “Eclipse for JavaScript Developers” package > * JSon Editor > * Docker Tools > * Vagrant Tools > * Smarter and easier Import of projects in the IDE > * Zoom In/Out with Ctrl+/Ctrl- in text editors > * Discovery and proposal of Marketplace extensions for unknown file types > * SWT on GTK3 > * Theming off > For Neon.1 - released September 28th: > * More Docker: https://wiki.eclipse.org/Linux_Tools_Project/News/NewIn51 > * Image viewer in the Eclipse IDE > For Eclipse Oxygen, next major release to be shipped in June 2018, here are our plans: > * generic and extensible code editor > * Integration with the language server protocol > * UI/UX efforts -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBDS-4014) Track rh-eclipse46-devstudio-*.rpm version usage

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBDS-4014?page=com.atlassian.jira.plugin.... ] Alexey Kazakov updated JBDS-4014: --------------------------------- Sprint: devex #121 October 2016 (was: devex #120 September 2016) > Track rh-eclipse46-devstudio-*.rpm version usage > ------------------------------------------------ > > Key: JBDS-4014 > URL: https://issues.jboss.org/browse/JBDS-4014 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Feature Request > Components: usage > Reporter: Alexey Kazakov > Assignee: Alexey Kazakov > Priority: Critical > Fix For: 10.2.0.AM1 > > > We need to distinguish the following use cases: > 1) Devstudio installed via RPM > 2) Devstudio installed via P2 but on top of the "base" eclipse rpm > 3) Devstudio installed traditionally (jar installer or p2) > As a bonus we could want to track if the DTS + devstudio rpms were both installed. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 6 months

1
0
0 / 0

[JBoss JIRA] (ERT-426) Change label in Run Configuration [EBZ#502261]

by Friendly Jira Robot (JIRA)

Friendly Jira Robot created ERT-426: --------------------------------------- Summary: Change label in Run Configuration [EBZ#502261] Key: ERT-426 URL: https://issues.jboss.org/browse/ERT-426 Project: Eclipse Release Train Issue Type: Task Components: Linux Tools Reporter: Friendly Jira Robot Priority: Minor Created attachment 264450 label Please change label "Name:" in "Run Docker Image" (in Run Configurations) on "Main" tab to for example "Container Name:". Current naming can be confusing for users. -- 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 Radim Hopp (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23267?page=com.atlassian.jira.plugi... ] Radim Hopp commented on JBIDE-23267: ------------------------------------ Hi, I haven't had time to try this PR and I'm leaving for PTO in few minutes (and Marian is already on PTO) thus I'm giving this PR +1 to be merged. If you still need somebody to actually try this PR, please send a mail to jboss-jbds-qe(a)redhat.com. (Note that Wednesday is bank holiday in Czech Rep.) > 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 > Affects Versions: 4.4.1.Final > Environment: * All versions > * I confirmed with latest version devstudio-10.0.0.GA-installer-standalone.jar > Reporter: Kenjiro Nakayama > Assignee: Andre Dietisheim > Priority: Critical > Labels: application_wizard, gear, openshift_v2 > Fix For: 4.4.2.AM2 > > Original Estimate: 4 hours > Time Spent: 1 hour > Remaining Estimate: 3 hours > > * 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-23023) Valiadation of credentials does not work for some runtimes in Download Runtime Wizard

by Radim Hopp (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23023?page=com.atlassian.jira.plugi... ] Radim Hopp reassigned JBIDE-23023: ---------------------------------- Assignee: Radim Hopp (was: Rob Stryker) > 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: Radim Hopp > 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-23271) When passing of SUB_USERNAME is unchecked in server editor, it's still included in launch config

by Martin Malina (JIRA)

Martin Malina created JBIDE-23271: ------------------------------------- Summary: When passing of SUB_USERNAME is unchecked in server editor, it's still included in launch config Key: JBIDE-23271 URL: https://issues.jboss.org/browse/JBIDE-23271 Project: Tools (JBoss Tools) Issue Type: Bug Components: cdk Affects Versions: 4.4.2.AM1 Reporter: Martin Malina Assignee: Rob Stryker Even if you uncheck "Pass credentials to environment" in cdk server editor and save, you will still see the variable in the Environment tab of Launch config. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23039) Need an interactive terminal that fits specific requirements

by Martin Malina (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23039?page=com.atlassian.jira.plugi... ] Martin Malina closed JBIDE-23039. --------------------------------- This works properly for me in devstudio 10.2.0.AM1, except I cannot use backspace on Mac. Logged here: JBIDE-23269 Closing. > Need an interactive terminal that fits specific requirements > ------------------------------------------------------------ > > Key: JBIDE-23039 > URL: https://issues.jboss.org/browse/JBIDE-23039 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: server > Affects Versions: 4.4.1.AM2 > Reporter: Rob Stryker > Assignee: Rob Stryker > Labels: cdk, new_and_noteworthy > Fix For: 4.4.2.AM1 > > Attachments: vagranttty.png > > > CDK Tools requires a terminal that allows interactivity of i/o. The full set of requirements is a bit difficult to find a solution for. > 1) I must be able to get a Process or IProcess object when a command is run > 2) I must be able to get an event or know when the process terminates > 3) The terminal or console must be interactive and allow user input when prompted. > 4) It must behave as in 3) for 'vagrant' commands and any and all associated plugins. > These three requirements thus far seem impossible to solve. Solutions that have been attempted are: > 1) Creating a java Process by myself via Runtime.exec. The interactive prompts never arrive and there is no API for Process to know when it is waiting for input. > 2) Using the external-tools launch configuration. When running a command like mvn, the console that pops up seems to allow input from the user, and functions as expected. However, when running a command such as vagrant, such prompts are not provided. In our usecase, the following behavior is observed: > a) During vagrant-registration prompts, the console indicates it is not a TTY terminal and cannot allow input > b) During a landrush prompt for superuser status, no prompt is made, no TTY message is listed, and the process appears to have frozen > 3) Launching / Opening a tm.terminal view. This solution fails requirements 1 and 2. We are not able to get a Process or an IProcess when a command is launched in a proper interactive terminal. This means we can have no way to know when the process has completed. > Other options have been explored but ended up at dead ends and not worth mentioning. The real question is why interactive behavior is visible when using external-tools launch config for maven, but is not visible when running vagrant. > Is this a function of the way the vagrant commands display or prompt for input? Why does vagrant-registration require a TTY terminal, but maven does not? Is this something that can be fixed upstream? > No other obvious solutions have presented themselves in the past year. -- 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