March 2016 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-21813) Delete of OpenShift application via server adapter is disabled

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21813?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-21813: ------------------------------------- Fix Version/s: 4.3.1.CR1 (was: 4.4.0.Alpha1) > Delete of OpenShift application via server adapter is disabled > -------------------------------------------------------------- > > Key: JBIDE-21813 > URL: https://issues.jboss.org/browse/JBIDE-21813 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.1.CR1 > Reporter: Marián Labuda > Assignee: Viacheslav Kabanovich > Labels: openshift_v2 > Fix For: 4.3.1.CR1 > > Attachments: video.ogg-1.ogv > > > Earlier it was possible to delete an OpenShift application via context menu of a server adapter "OpenShift" - "Delete application(s)...". While fixing JBIDE-21563, binding was commented out and some changes were done. Currently the context menu item is disabled so it is not possible to delete application via context menu item. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-21813) Delete of OpenShift application via server adapter is disabled

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21813?page=com.atlassian.jira.plugi... ] Andre Dietisheim commented on JBIDE-21813: ------------------------------------------ cherry-picked into jbosstools-4.3.x > Delete of OpenShift application via server adapter is disabled > -------------------------------------------------------------- > > Key: JBIDE-21813 > URL: https://issues.jboss.org/browse/JBIDE-21813 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.1.CR1 > Reporter: Marián Labuda > Assignee: Viacheslav Kabanovich > Labels: openshift_v2 > Fix For: 4.3.1.CR1 > > Attachments: video.ogg-1.ogv > > > Earlier it was possible to delete an OpenShift application via context menu of a server adapter "OpenShift" - "Delete application(s)...". While fixing JBIDE-21563, binding was commented out and some changes were done. Currently the context menu item is disabled so it is not possible to delete application via context menu item. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBDS-3656) The installer should use Vagrantfile provided by CDK

by Hardy Ferentschik (JIRA)

[ https://issues.jboss.org/browse/JBDS-3656?page=com.atlassian.jira.plugin.... ] Hardy Ferentschik commented on JBDS-3656: ----------------------------------------- {quote} are we ready to switch the installer to the CDK one? Or we still need to push your stuff upstream first? {quote} I'll wait for the Beta5 release this week. Once it is out I will make sure that all remaining issues are resolved. I'll also try to figure out whether there is possibility to consume weekly builds as complete zip bundles. This would allow for faster integration of the latest CDK changes. > The installer should use Vagrantfile provided by CDK > ---------------------------------------------------- > > Key: JBDS-3656 > URL: https://issues.jboss.org/browse/JBDS-3656 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Feature Request > Components: installer > Reporter: Hardy Ferentschik > Assignee: Denis Golovin > Priority: Blocker > Labels: havoc > Fix For: 9.1.0.CR1 > > > The installer should be using the {{Vagrantfile}} provided by the CDK (provided it reaches feature parity) instead of the {{Vagrantfile}} provided by the [openshift-vagrant|https://github.com/redhat-developer-tooling/openshift-v...]. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBDS-3651) Reduce the delay between the main window opening and the first page being rendered

by Jan Richter (JIRA)

[ https://issues.jboss.org/browse/JBDS-3651?page=com.atlassian.jira.plugin.... ] Jan Richter commented on JBDS-3651: ----------------------------------- Sounds like the easiest solution for me. Making the bootstrap faster would be a plus, but it would require some complex changes. > Reduce the delay between the main window opening and the first page being rendered > ---------------------------------------------------------------------------------- > > Key: JBDS-3651 > URL: https://issues.jboss.org/browse/JBDS-3651 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Enhancement > Components: installer > Reporter: Jan Richter > Assignee: Denis Golovin > Labels: havoc, ui > Fix For: 9.1.0.CR1 > > > Starting the installer right now leaves the user with about 3 seconds of staring at an empty window before the content shows up. > I've done a few tests on this matter and it seems majority of those 3 seconds is spent on angular bootstrap - mainly loading the required files and registering controllers. Replacing the index with simple static HTML causes the page to render almost instantaneously. > We should consider some way of showing the GUI before the user falls asleep (before angular fully loads the entire app). -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (ERT-86) Remove ECMAScript Compliance level from project properties [EBZ#488373]

by Shane Bryzak (JIRA)

[ https://issues.jboss.org/browse/ERT-86?page=com.atlassian.jira.plugin.sys... ] Shane Bryzak resolved ERT-86. ----------------------------- Resolution: Done > Remove ECMAScript Compliance level from project properties [EBZ#488373] > ----------------------------------------------------------------------- > > Key: ERT-86 > URL: https://issues.jboss.org/browse/ERT-86 > Project: Eclipse Release Train > Issue Type: Task > Components: JSDT > Reporter: Friendly Jira Robot > Assignee: Shane Bryzak > Labels: Debug, bzira > > This option can be found under Project properties -> JavaScript -> Validation. > This setting should be removed, and ES6 supported by default. Currently the highest available version that can be set by this property is ES3. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBDS-3657) Installer should set updated default username and password in .cdk

by Joshua Wilson (JIRA)

[ https://issues.jboss.org/browse/JBDS-3657?page=com.atlassian.jira.plugin.... ] Joshua Wilson updated JBDS-3657: -------------------------------- Labels: havoc (was: ) > Installer should set updated default username and password in .cdk > ------------------------------------------------------------------ > > Key: JBDS-3657 > URL: https://issues.jboss.org/browse/JBDS-3657 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Components: cdk, installer > Affects Versions: 9.1.0.Beta2 > Reporter: Rob Stryker > Assignee: Denis Golovin > Labels: havoc > Fix For: 9.1.0.CR1, 10.0.0.Alpha1 > > > openshift.auth.username=openshift-dev > openshift.auth.password=devel -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBDS-3656) The installer should use Vagrantfile provided by CDK

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBDS-3656?page=com.atlassian.jira.plugin.... ] Denis Golovin reassigned JBDS-3656: ----------------------------------- Assignee: Denis Golovin > The installer should use Vagrantfile provided by CDK > ---------------------------------------------------- > > Key: JBDS-3656 > URL: https://issues.jboss.org/browse/JBDS-3656 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Feature Request > Components: installer > Reporter: Hardy Ferentschik > Assignee: Denis Golovin > Priority: Blocker > Labels: havoc > Fix For: 9.1.0.CR1 > > > The installer should be using the {{Vagrantfile}} provided by the CDK (provided it reaches feature parity) instead of the {{Vagrantfile}} provided by the [openshift-vagrant|https://github.com/redhat-developer-tooling/openshift-v...]. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBDS-3658) CDK server start times out after 900s at the first start

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBDS-3658?page=com.atlassian.jira.plugin.... ] Alexey Kazakov commented on JBDS-3658: -------------------------------------- +1 > CDK server start times out after 900s at the first start > -------------------------------------------------------- > > Key: JBDS-3658 > URL: https://issues.jboss.org/browse/JBDS-3658 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Components: installer > Reporter: Fred Bricon > Fix For: 9.1.0.CR1 > > > Starting the CDK for the 1st time on my win10 laptop (5yo thinkpad t510, 8GB ram, no SSD, dual Core i7) timed out after 900s. > We might want to double that timeout. > This is using the installer on windows. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-21791) Forge addon - Changing the current file may cause a "file has changed in file vs memory" issue in Eclipse

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21791?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen commented on JBIDE-21791: --------------------------------------------- [~gastaldi] I say its very crappy because no other wizards in eclipse force-saves all open editors just because I start them. It is not an expected behavior. I would say if you want the minimal solution then have forge eclipse integration check if the current editor is unsaved and ask the user if he wants to save it before he continues (and let him save what he chooses). Then the user will be informed about the editor needs saving for forge to work best - and he can accept that to happen always in the future. ps. remember to add a reset for this setting in preferences ;) > Forge addon - Changing the current file may cause a "file has changed in file vs memory" issue in Eclipse > --------------------------------------------------------------------------------------------------------- > > Key: JBIDE-21791 > URL: https://issues.jboss.org/browse/JBIDE-21791 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: forge > Affects Versions: 4.3.1.Beta2 > Reporter: Claus Ibsen > Assignee: George Gastaldi > Fix For: 4.3.1.CR1 > > Attachments: eclipse-add.png > > > Similar problem as FORGE-2605 but this time its in Eclipse. > See the attached screenshot, where I have edited the file camel-context.xml, and then run my forge command, which would insert a Camel endpoint at the cursor position. But eclipse has detected a file conflict as in that dialog. > I wonder if the fix should be like in IDEA to save the file before the command is run. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBDS-3658) CDK server start times out after 900s at the first start

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBDS-3658?page=com.atlassian.jira.plugin.... ] Fred Bricon commented on JBDS-3658: ----------------------------------- We'll see how long it takes when the installer uses the latest Vagrantfile, then we can decide whether extending the timeout is relevant or not > CDK server start times out after 900s at the first start > -------------------------------------------------------- > > Key: JBDS-3658 > URL: https://issues.jboss.org/browse/JBDS-3658 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Components: installer > Reporter: Fred Bricon > Fix For: 9.1.0.CR1 > > > Starting the CDK for the 1st time on my win10 laptop (5yo thinkpad t510, 8GB ram, no SSD, dual Core i7) timed out after 900s. > We might want to double that timeout. > This is using the installer on windows. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 1 month

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 March 2016