[JBoss JIRA] (JBIDE-19343) integration tests do not fetch their required runtimes if not present in the cache folder
by Vlado Pakan (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19343?page=com.atlassian.jira.plugi... ]
Vlado Pakan commented on JBIDE-19343:
-------------------------------------
PR for integration tests applied thans
> integration tests do not fetch their required runtimes if not present in the cache folder
> -----------------------------------------------------------------------------------------
>
> Key: JBIDE-19343
> URL: https://issues.jboss.org/browse/JBIDE-19343
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: arquillian, build, server
> Affects Versions: 4.2.3.Beta1, 4.3.0.Alpha1
> Reporter: Nick Boldt
> Assignee: Mickael Istria
> Priority: Minor
> Fix For: 4.3.0.Alpha2
>
>
> There's a problem w/ integration tests not properly bootstrapping (downloading) their runtimes if not present in the cache folder (see jbosstools-dev thread: http://lists.jboss.org/pipermail/jbosstools-dev/2015-February/009770.html )
> Looks like default maven lifecycle causes the pre-integration-test phase to fire, which is fine when we plan to run tests.
> There are a number of such phase bindings in this test:
> https://github.com/jbosstools/jbosstools-server/blob/jbosstools-4.2.x/as/...
> And I think this step can be skipped w/ *-DskipTests*.
> But the bigger problem is... why won't Jenkins fetch missing deps when they're not in the cache folder?
> Here are some console log snipped from builds 119 - 123:
> {code}
> 11:38:04 [ERROR] Failed to execute goal com.googlecode.maven-download-plugin:maven-download-plugin:1.1.0:wget (install-eap-6.1.0) on project org.jboss.tools.as.test.core: IO Error: /home/hudson/static_build_env/jbds/download-cache/jboss-eap-6.1.1.zip (No such file or directory) -> [Help 1]
> 13:29:23 [ERROR] Failed to execute goal com.googlecode.maven-download-plugin:maven-download-plugin:1.1.0:wget (install-wildfly-8.0.0.Beta1) on project org.jboss.tools.as.test.core: IO Error: /home/hudson/static_build_env/jbds/download-cache/wildfly-8.0.0.Beta1.zip (No such file or directory) -> [Help 1]
> 16:15:15 [ERROR] Failed to execute goal com.googlecode.maven-download-plugin:maven-download-plugin:1.1.0:wget (install-tomcat6) on project org.jboss.tools.wtp.runtimes.tomcat.tests: IO Error: /home/hudson/static_build_env/jbds/download-cache/apache-tomcat-6.0.39.zip (No such file or directory) -> [Help 1]
> {code} -- https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-server_4....
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years
[JBoss JIRA] (JBIDE-19343) integration tests do not fetch their required runtimes if not present in the cache folder
by Vlado Pakan (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19343?page=com.atlassian.jira.plugi... ]
Vlado Pakan edited comment on JBIDE-19343 at 4/7/15 6:45 AM:
-------------------------------------------------------------
PR for integration tests applied thanks
was (Author: vpakan):
PR for integration tests applied thans
> integration tests do not fetch their required runtimes if not present in the cache folder
> -----------------------------------------------------------------------------------------
>
> Key: JBIDE-19343
> URL: https://issues.jboss.org/browse/JBIDE-19343
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: arquillian, build, server
> Affects Versions: 4.2.3.Beta1, 4.3.0.Alpha1
> Reporter: Nick Boldt
> Assignee: Mickael Istria
> Priority: Minor
> Fix For: 4.3.0.Alpha2
>
>
> There's a problem w/ integration tests not properly bootstrapping (downloading) their runtimes if not present in the cache folder (see jbosstools-dev thread: http://lists.jboss.org/pipermail/jbosstools-dev/2015-February/009770.html )
> Looks like default maven lifecycle causes the pre-integration-test phase to fire, which is fine when we plan to run tests.
> There are a number of such phase bindings in this test:
> https://github.com/jbosstools/jbosstools-server/blob/jbosstools-4.2.x/as/...
> And I think this step can be skipped w/ *-DskipTests*.
> But the bigger problem is... why won't Jenkins fetch missing deps when they're not in the cache folder?
> Here are some console log snipped from builds 119 - 123:
> {code}
> 11:38:04 [ERROR] Failed to execute goal com.googlecode.maven-download-plugin:maven-download-plugin:1.1.0:wget (install-eap-6.1.0) on project org.jboss.tools.as.test.core: IO Error: /home/hudson/static_build_env/jbds/download-cache/jboss-eap-6.1.1.zip (No such file or directory) -> [Help 1]
> 13:29:23 [ERROR] Failed to execute goal com.googlecode.maven-download-plugin:maven-download-plugin:1.1.0:wget (install-wildfly-8.0.0.Beta1) on project org.jboss.tools.as.test.core: IO Error: /home/hudson/static_build_env/jbds/download-cache/wildfly-8.0.0.Beta1.zip (No such file or directory) -> [Help 1]
> 16:15:15 [ERROR] Failed to execute goal com.googlecode.maven-download-plugin:maven-download-plugin:1.1.0:wget (install-tomcat6) on project org.jboss.tools.wtp.runtimes.tomcat.tests: IO Error: /home/hudson/static_build_env/jbds/download-cache/apache-tomcat-6.0.39.zip (No such file or directory) -> [Help 1]
> {code} -- https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-server_4....
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years
[JBoss JIRA] (JBIDE-18055) NullPionterException in VPE Preview Editor initialization
by Konstantin Marmalyukov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-18055?page=com.atlassian.jira.plugi... ]
Konstantin Marmalyukov resolved JBIDE-18055.
--------------------------------------------
Release Notes Text: Cannot reproduce this issue
Fix Version/s: 4.3.0.Alpha2
(was: 4.3.x)
Resolution: Cannot Reproduce Bug
> NullPionterException in VPE Preview Editor initialization
> ---------------------------------------------------------
>
> Key: JBIDE-18055
> URL: https://issues.jboss.org/browse/JBIDE-18055
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: visual-page-editor-core
> Affects Versions: 4.2.0.Beta3
> Reporter: Denis Golovin
> Assignee: Konstantin Marmalyukov
> Priority: Minor
> Fix For: 4.3.0.Alpha2
>
>
> Exception below can happen sometimes in case re-sizing visual preview part while preview server serving the editor is not started yet.
> {code}java.lang.NullPointerException
> at org.jboss.tools.vpe.preview.core.server.VpvServer.getPort(VpvServer.java:66)
> at org.jboss.tools.vpe.preview.editor.VpvEditor.formRequestToServer(VpvEditor.java:503)
> at org.jboss.tools.vpe.preview.editor.VpvEditor.reload(VpvEditor.java:494)
> at org.jboss.tools.vpe.preview.editor.VpvEditorPart.updateVisualEditorVisibility(VpvEditorPart.java:769)
> at org.jboss.tools.vpe.preview.editor.VpvEditorPart$5.controlResized(VpvEditorPart.java:386)
> at org.eclipse.swt.widgets.TypedListener.handleEvent(TypedListener.java:235)
> at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84)
> at org.eclipse.swt.widgets.Display.sendEvent(Display.java:4486)
> at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1388)
> at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1412)
> at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1393)
> at org.eclipse.swt.widgets.Control.setBounds(Control.java:1042)
> at org.eclipse.swt.widgets.Composite.setBounds(Composite.java:1435)
> at org.eclipse.swt.widgets.Control.setBounds(Control.java:851)
> at org.eclipse.swt.custom.SashForm.onDragSash(SashForm.java:288)
> at org.eclipse.swt.custom.SashForm$1.handleEvent(SashForm.java:90)
> at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84)
> at org.eclipse.swt.widgets.Display.sendEvent(Display.java:4486)
> at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1388)
> at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1412)
> at org.eclipse.swt.widgets.Widget.sendSelectionEvent(Widget.java:1526)
> at org.eclipse.swt.widgets.Sash.gtk_motion_notify_event(Sash.java:396)
> at org.eclipse.swt.widgets.Widget.windowProc(Widget.java:2104)
> at org.eclipse.swt.widgets.Control.windowProc(Control.java:5510)
> at org.eclipse.swt.widgets.Display.windowProc(Display.java:4700)
> at org.eclipse.swt.internal.gtk.OS._gtk_main_do_event(Native Method)
> at org.eclipse.swt.internal.gtk.OS.gtk_main_do_event(OS.java:9074)
> at org.eclipse.swt.widgets.Display.eventProc(Display.java:1253)
> at org.eclipse.swt.internal.gtk.OS._g_main_context_iteration(Native Method)
> at org.eclipse.swt.internal.gtk.OS.g_main_context_iteration(OS.java:2473)
> at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3439)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$9.run(PartRenderingEngine.java:1151)
> at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.run(PartRenderingEngine.java:1032)
> at org.eclipse.e4.ui.internal.workbench.E4Workbench.createAndRunUI(E4Workbench.java:148)
> at org.eclipse.ui.internal.Workbench$5.run(Workbench.java:636)
> at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332)
> at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:579)
> at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:150)
> at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:135)
> 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:382)
> at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:236)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:606)
> at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:648)
> at org.eclipse.equinox.launcher.Main.basicRun(Main.java:603)
> at org.eclipse.equinox.launcher.Main.run(Main.java:1465)
> at org.eclipse.equinox.launcher.Main.main(Main.java:1438)
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years
[JBoss JIRA] (JBIDE-19564) Use background job to detect default connection settings
by Xavier Coulon (JIRA)
Xavier Coulon created JBIDE-19564:
-------------------------------------
Summary: Use background job to detect default connection settings
Key: JBIDE-19564
URL: https://issues.jboss.org/browse/JBIDE-19564
Project: Tools (JBoss Tools)
Issue Type: Enhancement
Components: docker
Affects Versions: 4.3.0.Alpha1
Reporter: Xavier Coulon
In its current form, the New Connection wizard blocks the UI during opening and this can take a few seconds if the default docker deamon is not running (eg: using the REST API). There should be a background job or an immediate opening with a job (and a progress bar) while trying to detect the settings.
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years
[JBoss JIRA] (JBIDE-19563) Save docker connections in plugin preferences
by Xavier Coulon (JIRA)
Xavier Coulon created JBIDE-19563:
-------------------------------------
Summary: Save docker connections in plugin preferences
Key: JBIDE-19563
URL: https://issues.jboss.org/browse/JBIDE-19563
Project: Tools (JBoss Tools)
Issue Type: Enhancement
Components: docker
Affects Versions: 4.3.0.Alpha1
Reporter: Xavier Coulon
Assignee: Xavier Coulon
Fix For: 4.3.0.Alpha2
In the current code, the Docker connections are not saved when exiting the workspace, so they need to be setup again after restart
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years