[JBoss JIRA] (JBIDE-23780) Import Application: uncheck "Use default clone destination" wont recheck if I removed the folder that it''s complaining about
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-23780?page=com.atlassian.jira.plugi... ]
Andre Dietisheim updated JBIDE-23780:
-------------------------------------
Fix Version/s: 4.5.0.AM1
(was: 4.4.3.AM2)
> Import Application: uncheck "Use default clone destination" wont recheck if I removed the folder that it''s complaining about
> -----------------------------------------------------------------------------------------------------------------------------
>
> Key: JBIDE-23780
> URL: https://issues.jboss.org/browse/JBIDE-23780
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.4.3.AM1
> Reporter: Andre Dietisheim
> Labels: import_wizard, openshift_v3
> Fix For: 4.5.0.AM1
>
> Attachments: clone-destination-already-exists.png, error-even-though-clone-destination-doesnt-exist.png
>
>
> steps to reproduce:
> # ASSERT: make sure that you have a folder "jboss-eap-quickstarts" in your default Eclipse git clone destination (if you didnt change your preferences, it will point to ~/git/. If you dont have it yet git clone it from https://github.com/jboss-developer/jboss-eap-quickstarts.git)
> # EXEC: create a new application using the "eap64-basic-s2i" template
> # ASSERT: the OpenShift resources for your application are created, the import wizard pops up with the following error that complains about the directory already existing:
> !clone-destination-already-exists.png!
> # EXEC: manually remove the directory (ex. in cmd-line)
> # EXEC: uncheck "Use default clone destination:"
> Result:
> The error wont go away, the wizard is still complaining even though the folder isnt in the way any more.
> !error-even-though-clone-destination-doesnt-exist.png!
> Hitting "Browse" and pointing to the same folder, that doesnt containt the folder anymore, wont help. The error persists. There'
> s no way to work around this, you have to cancel the import and start over again.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 2 months
[JBoss JIRA] (JBTIS-1036) Fuse - Fix SAP tests
by Andrej Podhradsky (JIRA)
Andrej Podhradsky created JBTIS-1036:
----------------------------------------
Summary: Fuse - Fix SAP tests
Key: JBTIS-1036
URL: https://issues.jboss.org/browse/JBTIS-1036
Project: JBoss Tools Integration Stack
Issue Type: Task
Components: Fuse IDE, QE
Affects Versions: 4.4.1.CR1
Reporter: Andrej Podhradsky
Assignee: Andrej Podhradsky
There are errors in the SAP tests. It seems that the config.xml is not correctly mapped to Java objects.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 2 months
[JBoss JIRA] (JBTIS-1034) Disable any check for available printers in all tests
by Tomáš Sedmík (JIRA)
[ https://issues.jboss.org/browse/JBTIS-1034?page=com.atlassian.jira.plugin... ]
Tomáš Sedmík closed JBTIS-1034.
-------------------------------
PR was pushed to master
> Disable any check for available printers in all tests
> -----------------------------------------------------
>
> Key: JBTIS-1034
> URL: https://issues.jboss.org/browse/JBTIS-1034
> Project: JBoss Tools Integration Stack
> Issue Type: Task
> Components: QE
> Affects Versions: 4.4.0.Final
> Reporter: Andrej Podhradsky
> Assignee: Andrej Podhradsky
> Fix For: 4.4.0.Final
>
>
> It seems that we are still getting the old issue reported at
> https://bugs.eclipse.org/bugs/show_bug.cgi?id=215234
> I've found the following thread
> {code}
> "main" #1 prio=6 os_prio=0 tid=0x00007f431000a800 nid=0xb6b runnable [0x00007f431958a000]
> java.lang.Thread.State: RUNNABLE
> at org.eclipse.swt.internal.gtk.OS._gtk_enumerate_printers(Native Method)
> at org.eclipse.swt.internal.gtk.OS.gtk_enumerate_printers(OS.java:10689)
> at org.eclipse.swt.printing.Printer.getPrinterList(Printer.java:98)
> at org.eclipse.gef.ui.actions.PrintAction.calculateEnabled(PrintAction.java:45)
> at org.eclipse.gef.ui.actions.WorkbenchPartAction.refresh(WorkbenchPartAction.java:131)
> at org.eclipse.gef.ui.actions.WorkbenchPartAction.update(WorkbenchPartAction.java:173)
> at org.eclipse.gef.ui.parts.GraphicalEditor.updateActions(GraphicalEditor.java:458)
> at org.eclipse.bpel.common.ui.palette.GraphicalEditorWithPalette.access$1(GraphicalEditorWithPalette.java:1)
> at org.eclipse.bpel.common.ui.palette.GraphicalEditorWithPalette$3.run(GraphicalEditorWithPalette.java:134)
> at org.eclipse.swt.widgets.RunnableLock.run(RunnableLock.java:35)
> at org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchronizer.java:182)
> - locked <0x00000000ebc45b78> (a org.eclipse.swt.widgets.RunnableLock)
> at org.eclipse.swt.widgets.Display.runAsyncMessages(Display.java:4528)
> at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:4146)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$4.run(PartRenderingEngine.java:1121)
> at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:336)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.run(PartRenderingEngine.java:1022)
> at org.eclipse.e4.ui.internal.workbench.E4Workbench.createAndRunUI(E4Workbench.java:150)
> at org.eclipse.ui.internal.Workbench$5.run(Workbench.java:687)
> at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:336)
> at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:604)
> at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:148)
> at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:138)
> at org.eclipse.tycho.surefire.osgibooter.UITestApplication.runApplication(UITestApplication.java:31)
> at org.eclipse.tycho.surefire.osgibooter.AbstractUITestApplication.run(AbstractUITestApplication.java:120)
> at org.eclipse.tycho.surefire.osgibooter.UITestApplication.start(UITestApplication.java:37)
> 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:388)
> at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:243)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:498)
> at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:673)
> at org.eclipse.equinox.launcher.Main.basicRun(Main.java:610)
> at org.eclipse.equinox.launcher.Main.run(Main.java:1519)
> at org.eclipse.equinox.launcher.Main.main(Main.java:1492)
> {code}
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 2 months
[JBoss JIRA] (JBTIS-1011) Create UI test for language / dataformats properties
by Paul Leacu (JIRA)
[ https://issues.jboss.org/browse/JBTIS-1011?page=com.atlassian.jira.plugin... ]
Paul Leacu updated JBTIS-1011:
------------------------------
Fix Version/s: 10.1.0.GA
(was: 10.0.0.GA)
> Create UI test for language / dataformats properties
> ----------------------------------------------------
>
> Key: JBTIS-1011
> URL: https://issues.jboss.org/browse/JBTIS-1011
> Project: JBoss Tools Integration Stack
> Issue Type: Task
> Components: Fuse IDE, QE
> Affects Versions: 10.0.0.Alpha1
> Reporter: Lars Heinemann
> Assignee: Andrej Podhradsky
> Fix For: 10.1.0.GA
>
>
> If you select a "transform" endpoint in the diagram and set a new expression language the pom.xml should be updated to contain the dependency of the new language if not yet there.
> Same applies to dataformats (for instance "marshal" endpoints). Whenever you change the dataformat in the properties view to some other data format the dependency for that data format should be added to the pom.xml if its not yet there.
> Please find more information on this issue in FUSETOOLS-2186.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years, 2 months