February 2017 - jbosstools-issues

[JBoss JIRA] (JBIDE-21895) Application wizard: Resource name collisions after deleting and recreating the application

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21895?page=com.atlassian.jira.plugi... ] Andre Dietisheim edited comment on JBIDE-21895 at 2/3/17 10:34 AM: ------------------------------------------------------------------- [~psrna] In "oc" (starting with 1.4) you do "oc create service". Something that we dont offer in Eclipse yet. In "oc" versions prior to 1.4 you use a template. Something that we also offer in our tooling. In what regard do you believe our tooling is not flawless? The very same would also happen in you would do the very same steps with oc (apply a template, kill the service, re-apply the template). The only thing I see as being misleading is that you can get the impression that the item in the explorer is the application and that you can kill the application by killing the item (while what you see and kill is only the service). But you should notice that this can't be true since the wizard informed you of all resources that were created when you applied the template in the first place. So to improve the situation: * I added the resource kind in the properties view which should allow you to see that the item that you want to delete in the explorer actually is the service: JBIDE-23841 * I could also think of the application wizard to look ahead and tell you of resource conflicts that will occur if you apply the template that you have selected What would you change in the tooling? was (Author: adietish): [~psrna] In "oc" (starting with 1.4) you do "oc create service". Something that we dont offer in Eclipse yet. In "oc" versions prior to 1.4 you use a template. Something that we also offer in our tooling. In what regard do you believe our tooling is not flawless? The very same would also happen in you would do the very same steps with oc (apply a template, kill the service, re-apply the template). The only thing I see as being misleading is that you can get the impression that the item in the explorer is the application and that you can kill the application by killing the item (while what you see and kill is only the service). But you should notice that this can't be true since the wizard informed you of all resources that were created when you applied the template in the first place. So what would you change in the tooling? > Application wizard: Resource name collisions after deleting and recreating the application > ------------------------------------------------------------------------------------------ > > Key: JBIDE-21895 > URL: https://issues.jboss.org/browse/JBIDE-21895 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.1.CR1 > Reporter: Pavol Srna > Labels: application_wizard, openshift_v3 > Fix For: 4.4.3.Final > > Attachments: 1st-child-of-project.png, Screen Shot 2016-03-17 at 16.19.05.png, Screenshot 2017-02-02 18.22.34.png, Screenshot 2017-02-02 18.22.43.png > > > 1) Create e.g. node application in a openshift project > 2) Right click from project explorer -> Delete the application > 3) repeat step 1) > Result: > !Screen Shot 2016-03-17 at 16.19.05.png! -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21895) Application wizard: Resource name collisions after deleting and recreating the application

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21895?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-21895: ------------------------------------- Labels: application_wizard openshift_v3 (was: ) > Application wizard: Resource name collisions after deleting and recreating the application > ------------------------------------------------------------------------------------------ > > Key: JBIDE-21895 > URL: https://issues.jboss.org/browse/JBIDE-21895 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.1.CR1 > Reporter: Pavol Srna > Labels: application_wizard, openshift_v3 > Fix For: 4.4.3.Final > > Attachments: 1st-child-of-project.png, Screen Shot 2016-03-17 at 16.19.05.png, Screenshot 2017-02-02 18.22.34.png, Screenshot 2017-02-02 18.22.43.png > > > 1) Create e.g. node application in a openshift project > 2) Right click from project explorer -> Delete the application > 3) repeat step 1) > Result: > !Screen Shot 2016-03-17 at 16.19.05.png! -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21895) Application wizard: Resource name collisions after deleting and recreating the application

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21895?page=com.atlassian.jira.plugi... ] Andre Dietisheim edited comment on JBIDE-21895 at 2/3/17 10:31 AM: ------------------------------------------------------------------- [~psrna] In "oc" (starting with 1.4) you do "oc create service". Something that we dont offer in Eclipse yet. In "oc" versions prior to 1.4 you use a template. Something that we also offer in our tooling. In what regard do you believe our tooling is not flawless? The very same would also happen in you would do the very same steps with oc (apply a template, kill the service, re-apply the template). The only thing I see as being misleading is that you can get the impression that the item in the explorer is the application and that you can kill the application by killing the item (while what you see and kill is only the service). But you should notice that this can't be true since the wizard informed you of all resources that were created when you applied the template in the first place. So what would you change in the tooling? was (Author: adietish): [~psrna] In "oc" (starting with 1.4) you do "oc create service". Something that we dont offer in Eclipse yet. In "oc" versions prior to 1.4 you use a template. Something that we also offer in our tooling. In what regard do you believe our tooling is not flawless? The very same would also happen in you would do the very same steps with oc (apply a template, kill the service, re-apply the template). The only thing I see as being misleading is that you can get the impression that the item in the explorer is the application and that you can kill the application by killing the item. But you should notice that this can't be true since the wizard informed you of all resources that were created when you applied the template in the first place. So what would you change in the tooling? > Application wizard: Resource name collisions after deleting and recreating the application > ------------------------------------------------------------------------------------------ > > Key: JBIDE-21895 > URL: https://issues.jboss.org/browse/JBIDE-21895 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.1.CR1 > Reporter: Pavol Srna > Fix For: 4.4.3.Final > > Attachments: 1st-child-of-project.png, Screen Shot 2016-03-17 at 16.19.05.png, Screenshot 2017-02-02 18.22.34.png, Screenshot 2017-02-02 18.22.43.png > > > 1) Create e.g. node application in a openshift project > 2) Right click from project explorer -> Delete the application > 3) repeat step 1) > Result: > !Screen Shot 2016-03-17 at 16.19.05.png! -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23422) Server Adapter: Node.js debug session is terminated after ~1 minute and browser shows 502 error

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23422?page=com.atlassian.jira.plugi... ] Andre Dietisheim commented on JBIDE-23422: ------------------------------------------ [~rcernich] so this isnt a router problem, but a problem for all resources, is it? > Server Adapter: Node.js debug session is terminated after ~1 minute and browser shows 502 error > ----------------------------------------------------------------------------------------------- > > Key: JBIDE-23422 > URL: https://issues.jboss.org/browse/JBIDE-23422 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: javascript, openshift > Affects Versions: 4.4.2.AM2 > Environment: windows 10 > Fedora 24 > Reporter: Ilya Buziuk > Assignee: Andre Dietisheim > Priority: Critical > Labels: nodejs, openshift_v3, server_adapter > Fix For: 4.4.3.Final > > > We've found, that when one is debugging (the code is stopeed at breakpoint, stepping through code, inspecting variables, ...) longer than ~1 minute, browser displays error code 502 and the debug session gets terminated. This makes this feature not very useful, because all debugging must be quicker than that timeout. > The behavior is captured in this screencast: https://youtu.be/BJf7wcPqNmM (note how at the time 0:42 the page is finally loaded (502 error) and the debug session is terminated (in debug view)). > We were able to reproduce this issue on F24 and Win10 (using CDK and console.engint.openshift.com) -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21895) Application wizard: Resource name collisions after deleting and recreating the application

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21895?page=com.atlassian.jira.plugi... ] Andre Dietisheim commented on JBIDE-21895: ------------------------------------------ [~psrna] In "oc" (starting with 1.4) you do "oc create service". Something that we dont offer in Eclipse yet. In "oc" versions prior to 1.4 you use a template. Something that we also offer in our tooling. In what regard do you believe our tooling is not flawless? The very same would also happen in you would do the very same steps with oc (apply a template, kill the service, re-apply the template). The only thing I see as being misleading is that you can get the impression that the item in the explorer is the application and that you can kill the application by killing the item. But you should notice that this can't be true since the wizard informed you of all resources that were created when you applied the template in the first place. So what would you change in the tooling? > Application wizard: Resource name collisions after deleting and recreating the application > ------------------------------------------------------------------------------------------ > > Key: JBIDE-21895 > URL: https://issues.jboss.org/browse/JBIDE-21895 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.1.CR1 > Reporter: Pavol Srna > Fix For: 4.4.3.Final > > Attachments: 1st-child-of-project.png, Screen Shot 2016-03-17 at 16.19.05.png, Screenshot 2017-02-02 18.22.34.png, Screenshot 2017-02-02 18.22.43.png > > > 1) Create e.g. node application in a openshift project > 2) Right click from project explorer -> Delete the application > 3) repeat step 1) > Result: > !Screen Shot 2016-03-17 at 16.19.05.png! -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23862) Server adapter: if "oc" in preferences is set to path with a " " syncing fails

by Andre Dietisheim (JIRA)

Andre Dietisheim created JBIDE-23862: ---------------------------------------- Summary: Server adapter: if "oc" in preferences is set to path with a " " syncing fails Key: JBIDE-23862 URL: https://issues.jboss.org/browse/JBIDE-23862 Project: Tools (JBoss Tools) Issue Type: Bug Components: openshift Affects Versions: 4.4.3.Final Reporter: Andre Dietisheim Fix For: 4.4.3.Final -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBDS-4262) DevSuite installer should able to install Red Hat JBOSS Developer STUDIO

by Sudhir Verma (JIRA)

[ https://issues.jboss.org/browse/JBDS-4262?page=com.atlassian.jira.plugin.... ] Sudhir Verma reassigned JBDS-4262: ---------------------------------- Assignee: Sudhir Verma > DevSuite installer should able to install Red Hat JBOSS Developer STUDIO > ------------------------------------------------------------------------ > > Key: JBDS-4262 > URL: https://issues.jboss.org/browse/JBDS-4262 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Feature Request > Components: platform-installer > Environment: Windows > Reporter: Sudhir Verma > Assignee: Sudhir Verma > > jbds - Error: Invalid or corrupt jarfile C:\Users\sverma\AppData\Local\Temp\devstudio-10.3.0.AM2-v20170127-1155-B6970-installer-standalone.jar > jbds failed to install: Error: Command failed: C:\DevelopmentSuite\jdk8\jre\bin\java -DTRACE=true -jar C:\Users\sverma\AppData\Local\Temp\devstudio-10.3.0.AM2-v20170127-1155-B6970-installer-standalone.jar C:\Users\sverma\AppData\Local\Temp\jbds-autoinstall.xml > Error: Invalid or corrupt jarfile C:\Users\sverma\AppData\Local\Temp\devstudio-10.3.0.AM2-v20170127-1155-B6970-installer-standalone.jar -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBDS-4262) DevSuite installer should able to install Red Hat JBOSS Developer STUDIO

by Sudhir Verma (JIRA)

Sudhir Verma created JBDS-4262: ---------------------------------- Summary: DevSuite installer should able to install Red Hat JBOSS Developer STUDIO Key: JBDS-4262 URL: https://issues.jboss.org/browse/JBDS-4262 Project: Red Hat JBoss Developer Studio (devstudio) Issue Type: Feature Request Components: platform-installer Environment: Windows Reporter: Sudhir Verma jbds - Error: Invalid or corrupt jarfile C:\Users\sverma\AppData\Local\Temp\devstudio-10.3.0.AM2-v20170127-1155-B6970-installer-standalone.jar jbds failed to install: Error: Command failed: C:\DevelopmentSuite\jdk8\jre\bin\java -DTRACE=true -jar C:\Users\sverma\AppData\Local\Temp\devstudio-10.3.0.AM2-v20170127-1155-B6970-installer-standalone.jar C:\Users\sverma\AppData\Local\Temp\jbds-autoinstall.xml Error: Invalid or corrupt jarfile C:\Users\sverma\AppData\Local\Temp\devstudio-10.3.0.AM2-v20170127-1155-B6970-installer-standalone.jar -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBTIS-1038) Fix 'Data Sources Missing' dialogue

by Matus Makovy (JIRA)

Matus Makovy created JBTIS-1038: ----------------------------------- Summary: Fix 'Data Sources Missing' dialogue Key: JBTIS-1038 URL: https://issues.jboss.org/browse/JBTIS-1038 Project: JBoss Tools Integration Stack Issue Type: Bug Components: QE, teiid Affects Versions: 4.4.0.Final Reporter: Matus Makovy Assignee: Matus Makovy Fix For: 4.4.1.Final -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23861) CDI support is not enabled automatically with JBoss AS 7.1 runtime

by Lukáš Valach (JIRA)

Lukáš Valach created JBIDE-23861: ------------------------------------ Summary: CDI support is not enabled automatically with JBoss AS 7.1 runtime Key: JBIDE-23861 URL: https://issues.jboss.org/browse/JBIDE-23861 Project: Tools (JBoss Tools) Issue Type: Bug Components: cdi Affects Versions: 4.4.3.AM2 Environment: Devstudio AM2-v20170127-1155-B6970, Java 1.8.0_111-b15, JBoss AS 7.1.1.Final Reporter: Lukáš Valach Priority: Minor Fix For: 4.4.3.Final Attachments: CdiSupport1.png, CdiSupport2.png When I create a Dynamic Web Project or EJB Project the CDI support should be enabled automatically. It works properly when I have JBoss EAP 7 or Wildfly 10 as target platform, but it doesn't work with JBoss AS 7.1. There is no error in the log, there is only warning in the problems view. ??JBoss Tools Knowledge Base probelm: Nature/Builder is not installed on project. Use quick fix to enable %KB_REQUIRED_FOR_FACET and Faceted (test environment only) Content Assistant and Validation.?? -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 2 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 February 2017