April 2016 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-22057) Changes done to OpenShift application are thrown away when debugging is enabled

by Marián Labuda (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22057?page=com.atlassian.jira.plugi... ] Marián Labuda commented on JBIDE-22057: --------------------------------------- I am not aware of any. Maybe pushing local changes to remote git repo. I will try it once I have some time. > Changes done to OpenShift application are thrown away when debugging is enabled > ------------------------------------------------------------------------------- > > Key: JBIDE-22057 > URL: https://issues.jboss.org/browse/JBIDE-22057 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.3.1.CR1 > Reporter: Marián Labuda > Priority: Critical > Labels: openshift_v3, server_adapter > Fix For: 4.4.0.Alpha1 > > > When I have an OpenShift application and I do any changes locally which are either incrementally or fully published, enabling of debugging discard those changes and start debugging on something different. > I think this is caused because enabling debugging inject another env. vars to OpenShift and it spin up a new pod but does not keep changes. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (JBTIS-624) Fixed XmlSchemalessTest, Added SAP Hana import tests

by Andrej Podhradsky (JIRA)

[ https://issues.jboss.org/browse/JBTIS-624?page=com.atlassian.jira.plugin.... ] Andrej Podhradsky closed JBTIS-624. ----------------------------------- I'm closing this issue. Feel free to reopen this issue if you want to add another PR. > Fixed XmlSchemalessTest, Added SAP Hana import tests > ----------------------------------------------------- > > Key: JBTIS-624 > URL: https://issues.jboss.org/browse/JBTIS-624 > Project: JBoss Tools Integration Stack > Issue Type: Bug > Components: QE, teiid > Affects Versions: 4.2.5.Final, 4.3.0.Beta1 > Reporter: stanislav kaleta > Assignee: stanislav kaleta > Fix For: 4.3.0.Beta1, 4.2.6.CR2 > > -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (JBTIS-624) Fixed XmlSchemalessTest, Added SAP Hana import tests

by Andrej Podhradsky (JIRA)

[ https://issues.jboss.org/browse/JBTIS-624?page=com.atlassian.jira.plugin.... ] Andrej Podhradsky commented on JBTIS-624: ----------------------------------------- [~skaleta] I pushed your PR to the master branch. If you wish to push it also to the jbtis-4.2.x branch then please create a new PR in guthub and attach the link to this issue (one jira issue can contain more lPR links). > Fixed XmlSchemalessTest, Added SAP Hana import tests > ----------------------------------------------------- > > Key: JBTIS-624 > URL: https://issues.jboss.org/browse/JBTIS-624 > Project: JBoss Tools Integration Stack > Issue Type: Bug > Components: QE, teiid > Affects Versions: 4.2.5.Final, 4.3.0.Beta1 > Reporter: stanislav kaleta > Assignee: stanislav kaleta > Fix For: 4.3.0.Beta1, 4.2.6.CR2 > > -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (JBTIS-574) Adapt UI tests to 8.0.0

by Andrej Podhradsky (JIRA)

[ https://issues.jboss.org/browse/JBTIS-574?page=com.atlassian.jira.plugin.... ] Andrej Podhradsky closed JBTIS-574. ----------------------------------- all subtasks were closed so this issue can be closed > Adapt UI tests to 8.0.0 > ----------------------- > > Key: JBTIS-574 > URL: https://issues.jboss.org/browse/JBTIS-574 > Project: JBoss Tools Integration Stack > Issue Type: Task > Components: Fuse IDE, QE > Affects Versions: 4.3.0.Alpha2 > Reporter: Tomáš Sedmík > Assignee: Tomáš Sedmík > Priority: Critical > Fix For: 4.3.0.CR1 > > Original Estimate: 1 week > Remaining Estimate: 1 week > > There are some changes in Fuse Tooling (new Camel Editor, ...), so our automated tests have to be adapted to reflect these changes. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (JBTIS-577) Adapt 'DataTransformationTest' to 8.0.0

by Andrej Podhradsky (JIRA)

[ https://issues.jboss.org/browse/JBTIS-577?page=com.atlassian.jira.plugin.... ] Andrej Podhradsky closed JBTIS-577. ----------------------------------- pushed > Adapt 'DataTransformationTest' to 8.0.0 > --------------------------------------- > > Key: JBTIS-577 > URL: https://issues.jboss.org/browse/JBTIS-577 > Project: JBoss Tools Integration Stack > Issue Type: Sub-task > Components: Fuse IDE, QE > Affects Versions: 4.3.0.Alpha2 > Reporter: Tomáš Sedmík > Assignee: Tomáš Sedmík > Fix For: 4.3.0.CR1 > > Time Spent: 2 days > Remaining Estimate: 0 minutes > > SSIA -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-22056) OperationCanceledException in CheatSheetUtil.promptToShowCheatsheets

by Radim Hopp (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22056?page=com.atlassian.jira.plugi... ] Radim Hopp closed JBIDE-22056. ------------------------------ Closing as duplicate. > OperationCanceledException in CheatSheetUtil.promptToShowCheatsheets > -------------------------------------------------------------------- > > Key: JBIDE-22056 > URL: https://issues.jboss.org/browse/JBIDE-22056 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: project-examples > Affects Versions: 4.3.1.CR1 > Reporter: Automated Error Reporting Bot > Fix For: 4.4.0.Alpha1 > > > The following incident was reported via the automated error reporting: > The user(s) left the following comments: > --- rawagner wrote: --- > already reported https://issues.jboss.org/browse/JBIDE-22041 > > code: 0 > plugin: org.eclipse.ui_3.107.0.v20150507-1945 > message: Unhandled event loop exception > fingerprint: dec4298512ae6459942d54a3c5a40bda > exception class: org.eclipse.swt.SWTException > exception message: Failed to execute runnable (org.eclipse.core.runtime.OperationCanceledException) > number of children: 0 > > {noformat} > org.eclipse.swt.SWTException: Failed to execute runnable (org.eclipse.core.runtime.OperationCanceledException) > at org.eclipse.swt.SWT.error(SWT.java:4491) > at org.eclipse.swt.SWT.error(SWT.java:4406) > at org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchronizer.java:138) > at org.eclipse.swt.widgets.Display.runAsyncMessages(Display.java:3794) > at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3433) > at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$4.run(PartRenderingEngine.java:1127) > at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:337) > at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.run(PartRenderingEngine.java:1018) > at org.eclipse.e4.ui.internal.workbench.E4Workbench.createAndRunUI(E4Workbench.java:156) > at org.eclipse.ui.internal.Workbench$5.run(Workbench.java:694) > at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:337) > at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:606) > at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:150) > at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:139) > at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:196) > at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:134) > at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:104) > at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:380) > at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:235) > at sun.reflect.NativeMethodAccessorImpl.invoke0(NativeMethodAccessorImpl.java:-2) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:497) > at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:669) > at org.eclipse.equinox.launcher.Main.basicRun(Main.java:608) > at org.eclipse.equinox.launcher.Main.run(Main.java:1515) > at org.eclipse.equinox.launcher.Main.main(Main.java:1488) > caused by: org.eclipse.core.runtime.OperationCanceledException: null > at org.jboss.tools.project.examples.cheatsheet.internal.util.CheatSheetUtil.promptToShowCheatsheets(CheatSheetUtil.java:434)[TOPMOST, REQUIRED] > at org.jboss.tools.project.examples.cheatsheet.internal.util.CheatSheetUtil.access$1(CheatSheetUtil.java:394) > at org.jboss.tools.project.examples.cheatsheet.internal.util.CheatSheetUtil$1.run(CheatSheetUtil.java:378) > at org.eclipse.ui.internal.UILockListener.doPendingWork(UILockListener.java:162)[REQUIRED] > at org.eclipse.ui.internal.UISynchronizer$3.run(UISynchronizer.java:154) > at org.eclipse.swt.widgets.RunnableLock.run(RunnableLock.java:35) > at org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchronizer.java:135) > at org.eclipse.swt.widgets.Display.runAsyncMessages(Display.java:3794) > at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3433) > at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$4.run(PartRenderingEngine.java:1127) > at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:337) > at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.run(PartRenderingEngine.java:1018) > at org.eclipse.e4.ui.internal.workbench.E4Workbench.createAndRunUI(E4Workbench.java:156) > at org.eclipse.ui.internal.Workbench$5.run(Workbench.java:694) > at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:337) > at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:606) > at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:150) > at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:139) > at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:196) > at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:134) > at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:104) > at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:380) > at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:235) > at sun.reflect.NativeMethodAccessorImpl.invoke0(NativeMethodAccessorImpl.java:-2) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:497) > at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:669) > at org.eclipse.equinox.launcher.Main.basicRun(Main.java:608) > at org.eclipse.equinox.launcher.Main.run(Main.java:1515) > at org.eclipse.equinox.launcher.Main.main(Main.java:1488) > {noformat} > > General Information: > reported-by: rawagner > anonymous-id: 8ec9bf96-4ab2-4e82-9870-c12985cbff45 > eclipse-build-id: 9.1.0.CR1-v20160326-0059-B443 > eclipse-product: com.jboss.devstudio.core.product > operating system: Linux 4.0.4 (x86_64) - gtk > jre-version: 1.8.0_66-b17 > The following plug-ins were present on the execution stack (*): > 1. org.eclipse.core.databinding.observable_1.5.0.v20150422-0725 > 2. org.eclipse.core.databinding_1.5.0.v20150422-0725 > 3. org.eclipse.core.runtime_3.11.1.v20150903-1804 > 4. org.eclipse.e4.ui.workbench_1.3.1.v20160203-0951 > 5. org.eclipse.e4.ui.workbench.swt_0.13.0.v20150504-0621 > 6. org.eclipse.equinox.app_1.3.300.v20150423-1356 > 7. org.eclipse.equinox.launcher_1.3.100.v20150511-1540 > 8. org.eclipse.swt_3.104.2.v20160212-1350 > 9. org.eclipse.ui_3.107.0.v20150507-1945 > 10. org.eclipse.ui.ide.application_1.1.0.v20150422-0725 > 11. org.eclipse.ui.ide_3.11.0.v20150825-2158 > 12. org.jboss.tools.project.examples.cheatsheet_3.0.1.CR1-v20160324-1911-B99 > 13. org.jboss.tools.project.examples_3.0.1.CR1-v20160324-1911-B99 > Please note that: > * Messages, stacktraces, and nested status objects may be shortened. > * Bug fields like status, resolution, and whiteboard are sent > back to reporters. > * The list of present bundles and their respective versions was > calculated by package naming heuristics. This may or may not reflect reality. > Other Resources: > * Report: https://redhat.ctrlflow.com/committers/#/problems/56fd094ce4b08ccb7be35871 > * Manual: https://redhat.ctrlflow.com/community/#/guide > Thank you for your assistance. > Your friendly error-reports-inbox. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (JBDS-3759) Installer - Documentation should advise user to run commands from the correct directory

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBDS-3759?page=com.atlassian.jira.plugin.... ] Denis Golovin commented on JBDS-3759: ------------------------------------- This is something for CDK Documentation, Developer Studio takes care about it by having CDK Server configured OOTB and what user needs is just start it. > Installer - Documentation should advise user to run commands from the correct directory > --------------------------------------------------------------------------------------- > > Key: JBDS-3759 > URL: https://issues.jboss.org/browse/JBDS-3759 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Components: documentation, installer > Affects Versions: 9.1.0.GA > Environment: Installer: Setup-bundled-0.0.2-20160401-33.exe > Reporter: Len DiMaggio > Assignee: Misha Ali > Labels: havoc > > C:\Users\jbossqa>vagrant ssh > A Vagrant environment or target machine is required to run this > command. Run `vagrant init` to create a new Vagrant environment. Or, > get an ID of a target machine from `vagrant global-status` to run > this command on. A final option is to change to a directory with a > Vagrantfile and to try again. > C:\>cd DeveloperPlatform\cdk\components\rhel\rhel-ose > C:\DeveloperPlatform\cdk\components\rhel\rhel-ose>vagrant ssh > VM must be running to open SSH connection. Run `vagrant up` > to start the virtual machine. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (JBDS-3742) Cygwin setup executable should be installed as well

by CDW Engine (JIRA)

[ https://issues.jboss.org/browse/JBDS-3742?page=com.atlassian.jira.plugin.... ] CDW Engine updated JBDS-3742: ----------------------------- > Cygwin setup executable should be installed as well > --------------------------------------------------- > > Key: JBDS-3742 > URL: https://issues.jboss.org/browse/JBDS-3742 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Enhancement > Components: installer > Affects Versions: 9.1.0.CR1 > Reporter: Hardy Ferentschik > Priority: Minor > Labels: havoc > Fix For: 9.1.0.GA > > > As part of the installer Cygwin gets installed. However, the setup executable and package manager of Cygwin does not seem to get copied as well. Without it the user won't be able to extend/change the Cygwin configuration. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (JBDS-3742) Cygwin setup executable should be installed as well

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBDS-3742?page=com.atlassian.jira.plugin.... ] Denis Golovin updated JBDS-3742: -------------------------------- > Cygwin setup executable should be installed as well > --------------------------------------------------- > > Key: JBDS-3742 > URL: https://issues.jboss.org/browse/JBDS-3742 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Enhancement > Components: installer > Affects Versions: 9.1.0.CR1 > Reporter: Hardy Ferentschik > Priority: Minor > Labels: havoc > Fix For: 9.1.0.GA > > > As part of the installer Cygwin gets installed. However, the setup executable and package manager of Cygwin does not seem to get copied as well. Without it the user won't be able to extend/change the Cygwin configuration. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (JBDS-3742) Cygwin setup executable should be installed as well

by CDW Engine (JIRA)

[ https://issues.jboss.org/browse/JBDS-3742?page=com.atlassian.jira.plugin.... ] CDW Engine updated JBDS-3742: ----------------------------- > Cygwin setup executable should be installed as well > --------------------------------------------------- > > Key: JBDS-3742 > URL: https://issues.jboss.org/browse/JBDS-3742 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Enhancement > Components: installer > Affects Versions: 9.1.0.CR1 > Reporter: Hardy Ferentschik > Priority: Minor > Labels: havoc > Fix For: 9.1.0.GA > > > As part of the installer Cygwin gets installed. However, the setup executable and package manager of Cygwin does not seem to get copied as well. Without it the user won't be able to extend/change the Cygwin configuration. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

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