[JBoss JIRA] (JBIDE-17466) Cleanup obsolete code after replacement of JAX-RS Wizard(s)
by Brian Fitzpatrick (JIRA)
[ https://issues.jboss.org/browse/JBIDE-17466?page=com.atlassian.jira.plugi... ]
Brian Fitzpatrick commented on JBIDE-17466:
-------------------------------------------
Yes, we should probably do that for beta3 to avoid confusion.
> Cleanup obsolete code after replacement of JAX-RS Wizard(s)
> -----------------------------------------------------------
>
> Key: JBIDE-17466
> URL: https://issues.jboss.org/browse/JBIDE-17466
> Project: Tools (JBoss Tools)
> Issue Type: Task
> Components: webservices
> Affects Versions: 4.2.0.Beta2
> Reporter: Xavier Coulon
> Assignee: Xavier Coulon
> Fix For: 4.2.0.Beta3
>
> Attachments: Screen Shot 2014-06-04 at 15.17.33.png
>
>
> Some classes and resouces related to the former "Create sample RESTful Service" wizard were moved from {{org.jboss.tools.ws.ui}} to {{org.jboss.tools.ws.jaxrs.ui}} as part of JBIDE-9223, then replaced with other classes and resources as part of JBIDE-17151, but some classes still required by the "Simple Web Service" wizard were lost in the process, as reported in JBIDE-17459. The most straightforward solution for JBT 4.2.0.Beta2 was to restore those files and simply comment out the extension for the "Create sample RESTful Service" in {{org.jboss.tools.ws.ui/plugin.xml}}
> But now it is time to do some cleanup.
--
This message was sent by Atlassian JIRA
(v6.2.3#6260)
11 years, 10 months
[JBoss JIRA] (JBIDE-17207) Run tests on all major OS
by Martin Malina (JIRA)
[ https://issues.jboss.org/browse/JBIDE-17207?page=com.atlassian.jira.plugi... ]
Martin Malina commented on JBIDE-17207:
---------------------------------------
[~mickael_istria] What are the specific issues you have on OS X? I'm just curious as we needed to deal with some issues there as well.
> Run tests on all major OS
> -------------------------
>
> Key: JBIDE-17207
> URL: https://issues.jboss.org/browse/JBIDE-17207
> Project: Tools (JBoss Tools)
> Issue Type: Task
> Components: qa
> Reporter: Alexey Kazakov
> Assignee: Mickael Istria
> Fix For: 4.2.0.Beta3, 4.2.0.CR1
>
>
> Currently, our jenkins server runs JBT jUnit tests on Linux only. It would be good if we also run the tests on Windows and Mac.
> For example, we recently ran base, jst and javaee tests on Windows and got more than a hundred failures. Some of them indicated real bugs (not just tests problems). See JBIDE-17200.
> We don't have to run them every day. Maybe once a week or month?
> cc: [~maxandersen], [~dgolovin], [~nickboldt], [~mickael_istria]
--
This message was sent by Atlassian JIRA
(v6.2.3#6260)
11 years, 10 months
[JBoss JIRA] (JBDS-3044) Align installation default path with installer filename (and add version string too?)
by Martin Malina (JIRA)
[ https://issues.jboss.org/browse/JBDS-3044?page=com.atlassian.jira.plugin.... ]
Martin Malina commented on JBDS-3044:
-------------------------------------
But we don't include spring by default, perhaps that's why we didn't hit this before. But this should be investigated more - I can try what happens in different situations.
> Align installation default path with installer filename (and add version string too?)
> -------------------------------------------------------------------------------------
>
> Key: JBDS-3044
> URL: https://issues.jboss.org/browse/JBDS-3044
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Feature Request
> Security Level: Public(Everyone can see)
> Components: installer
> Affects Versions: 8.0.0.Beta2
> Reporter: Martin Malina
> Assignee: Denis Golovin
> Priority: Blocker
> Labels: discuss
> Fix For: 8.0.0.Beta3
>
>
> Now that Nick changed the installer filenames to jboss-devstudio in JBIDE-16871 (was jbdevstudio), shouldn't the default install path be changed similarly? Because it just went out of sync.
> This question is open for discussion. Nick pointed out some reasons against this suggestion:
> {quote}
> Martin Malina Re: changing the installation folder, I'll hold off on that change for the moment for a few reasons:
> a) Max is AFK, and will want to vet/veto this idea
> b) long paths for Windows users (80% of our user base) = bad news, especially considering how long some file paths can get already within Eclipse workspaces
> c) short paths for Windows (c:\jbdevstudio) & long paths for everyone else ~/jboss-devstudio) would be ill-advised from a documentation and cross-platform user experience
> So, either we stick w/ jbdevstudio, or we shorten to devstudio (losing the "jb" branding fragment). If we move to "jboss-devstudio" we increase the path by only 4 characters.
> Max Rydahl Andersen WDYT?
> {quote}
--
This message was sent by Atlassian JIRA
(v6.2.3#6260)
11 years, 10 months
[JBoss JIRA] (JBIDE-17207) Run tests on all major OS
by Mickael Istria (JIRA)
[ https://issues.jboss.org/browse/JBIDE-17207?page=com.atlassian.jira.plugi... ]
Mickael Istria commented on JBIDE-17207:
----------------------------------------
Current blockers:
* UI Tests on MacOSX can't work because of CI slave configuration
* Some files can't be deleted on Windows, leading to test failures. Investigation in progress.
> Run tests on all major OS
> -------------------------
>
> Key: JBIDE-17207
> URL: https://issues.jboss.org/browse/JBIDE-17207
> Project: Tools (JBoss Tools)
> Issue Type: Task
> Components: qa
> Reporter: Alexey Kazakov
> Assignee: Mickael Istria
> Fix For: 4.2.0.Beta3, 4.2.0.CR1
>
>
> Currently, our jenkins server runs JBT jUnit tests on Linux only. It would be good if we also run the tests on Windows and Mac.
> For example, we recently ran base, jst and javaee tests on Windows and got more than a hundred failures. Some of them indicated real bugs (not just tests problems). See JBIDE-17200.
> We don't have to run them every day. Maybe once a week or month?
> cc: [~maxandersen], [~dgolovin], [~nickboldt], [~mickael_istria]
--
This message was sent by Atlassian JIRA
(v6.2.3#6260)
11 years, 10 months
[JBoss JIRA] (JBIDE-17207) Run tests on all major OS
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-17207?page=com.atlassian.jira.plugi... ]
Nick Boldt commented on JBIDE-17207:
------------------------------------
Aerogear appears to only have one test class w/ UI in it: org/jboss/tools/aerogear/hybrid/ui/wizard/project/HybridProjectCreatorTest
Jobs that notoriously have test failures due to UI: JavaEE, VPE, Server, Hibernate, Central. Please experiment with those.
> Run tests on all major OS
> -------------------------
>
> Key: JBIDE-17207
> URL: https://issues.jboss.org/browse/JBIDE-17207
> Project: Tools (JBoss Tools)
> Issue Type: Task
> Components: qa
> Reporter: Alexey Kazakov
> Assignee: Mickael Istria
> Fix For: 4.2.0.Beta3, 4.2.0.CR1
>
>
> Currently, our jenkins server runs JBT jUnit tests on Linux only. It would be good if we also run the tests on Windows and Mac.
> For example, we recently ran base, jst and javaee tests on Windows and got more than a hundred failures. Some of them indicated real bugs (not just tests problems). See JBIDE-17200.
> We don't have to run them every day. Maybe once a week or month?
> cc: [~maxandersen], [~dgolovin], [~nickboldt], [~mickael_istria]
--
This message was sent by Atlassian JIRA
(v6.2.3#6260)
11 years, 10 months
[JBoss JIRA] (JBDS-3044) Align installation default path with installer filename (and add version string too?)
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBDS-3044?page=com.atlassian.jira.plugin.... ]
Nick Boldt commented on JBDS-3044:
----------------------------------
{quote}
When using an API to create a directory, the specified path cannot be so long that you cannot append an 8.3 file name (that is, the directory name cannot exceed MAX_PATH minus 12).
{quote}
-- http://msdn.microsoft.com/en-us/library/aa365247.aspx#maxpath
If this is accurate then the effective MAX_PATH is 260-12 = *248 chars* (which is LESS than _studio/configuration/org.eclipse.osgi/949/data/c7ff8a0a591e0e90fe36069138e75f68/1012-1401176993555/org.springframework.ide.eclipse.core.java.ProjectClassLoaderCache$SourceAndOutputLocationResourceChangeListener$SourceAndOutputLocationResourceVisitor_, at 249 chars) ... unless we somehow manage to use \\?\ prefix in the jbdevstudio.bat (or, if renamed, in jboss-devstudio.bat) to work around that path length limit.
> Align installation default path with installer filename (and add version string too?)
> -------------------------------------------------------------------------------------
>
> Key: JBDS-3044
> URL: https://issues.jboss.org/browse/JBDS-3044
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Feature Request
> Security Level: Public(Everyone can see)
> Components: installer
> Affects Versions: 8.0.0.Beta2
> Reporter: Martin Malina
> Assignee: Denis Golovin
> Priority: Blocker
> Labels: discuss
> Fix For: 8.0.0.Beta3
>
>
> Now that Nick changed the installer filenames to jboss-devstudio in JBIDE-16871 (was jbdevstudio), shouldn't the default install path be changed similarly? Because it just went out of sync.
> This question is open for discussion. Nick pointed out some reasons against this suggestion:
> {quote}
> Martin Malina Re: changing the installation folder, I'll hold off on that change for the moment for a few reasons:
> a) Max is AFK, and will want to vet/veto this idea
> b) long paths for Windows users (80% of our user base) = bad news, especially considering how long some file paths can get already within Eclipse workspaces
> c) short paths for Windows (c:\jbdevstudio) & long paths for everyone else ~/jboss-devstudio) would be ill-advised from a documentation and cross-platform user experience
> So, either we stick w/ jbdevstudio, or we shorten to devstudio (losing the "jb" branding fragment). If we move to "jboss-devstudio" we increase the path by only 4 characters.
> Max Rydahl Andersen WDYT?
> {quote}
--
This message was sent by Atlassian JIRA
(v6.2.3#6260)
11 years, 10 months
[JBoss JIRA] (JBIDE-17460) Exception when back button on mouse is pressed
by Vlado Pakan (JIRA)
[ https://issues.jboss.org/browse/JBIDE-17460?page=com.atlassian.jira.plugi... ]
Vlado Pakan commented on JBIDE-17460:
-------------------------------------
Any multi button mouse should be fine. I have tested with two different mouses both successfully throws exception.
I can test your fix once it's done before you create PR if you want.
> Exception when back button on mouse is pressed
> ----------------------------------------------
>
> Key: JBIDE-17460
> URL: https://issues.jboss.org/browse/JBIDE-17460
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: browsersim
> Affects Versions: 4.2.0.Beta2
> Environment: JBDS 8.0.0.Beta2-v20140525-2146-B104
> Linux 64bit
> Java 1.7.0_51
> Reporter: Vlado Pakan
> Assignee: Konstantin Marmalyukov
> Priority: Critical
> Fix For: 4.2.0.Beta3
>
>
> 1.Open BrowserSim with empty page. BrowserSim is run with JavaFX engine
> 2.Click on empty page within BrowserSim
> 3.Click on Back button on mouse (back action is defined for back button on mouse within OS)
> ERROR:
> {noformat}
> 2014-05-28 11:52:08.348:INFO:oejs.AbstractConnector:Started SelectChannelConnector@0.0.0.0:56505
> Exception in runnable
> java.lang.NullPointerException
> at javafx.scene.Scene$ClickCounter.access$7600(Scene.java:3030)
> at javafx.scene.Scene$ClickGenerator.preProcess(Scene.java:3126)
> at javafx.scene.Scene$ClickGenerator.access$8400(Scene.java:3096)
> at javafx.scene.Scene$MouseHandler.process(Scene.java:3347)
> at javafx.scene.Scene$MouseHandler.process(Scene.java:3209)
> at javafx.scene.Scene$MouseHandler.access$1900(Scene.java:3164)
> at javafx.scene.Scene.impl_processMouseEvent(Scene.java:1582)
> at javafx.scene.Scene$ScenePeerListener.mouseEvent(Scene.java:2267)
> at com.sun.javafx.tk.quantum.EmbeddedScene$2$1.run(EmbeddedScene.java:194)
> at com.sun.javafx.tk.quantum.EmbeddedScene$2$1.run(EmbeddedScene.java:176)
> at java.security.AccessController.doPrivileged(Native Method)
> at com.sun.javafx.tk.quantum.EmbeddedScene$2.run(EmbeddedScene.java:176)
> at com.sun.javafx.application.PlatformImpl$4$1.run(PlatformImpl.java:182)
> at com.sun.javafx.application.PlatformImpl$4$1.run(PlatformImpl.java:179)
> at java.security.AccessController.doPrivileged(Native Method)
> at com.sun.javafx.application.PlatformImpl$4.run(PlatformImpl.java:179)
> at com.sun.glass.ui.InvokeLaterDispatcher$Future.run(InvokeLaterDispatcher.java:76)
> 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:3414)
> at org.jboss.tools.vpe.browsersim.BrowserSimRunner.main(BrowserSimRunner.java:114)
> Exception in runnable
> java.lang.NullPointerException
> at javafx.scene.Scene$ClickCounter.access$7900(Scene.java:3030)
> at javafx.scene.Scene$ClickGenerator.postProcess(Scene.java:3157)
> at javafx.scene.Scene$ClickGenerator.access$8600(Scene.java:3096)
> at javafx.scene.Scene$MouseHandler.process(Scene.java:3378)
> at javafx.scene.Scene$MouseHandler.process(Scene.java:3209)
> at javafx.scene.Scene$MouseHandler.access$1900(Scene.java:3164)
> at javafx.scene.Scene.impl_processMouseEvent(Scene.java:1582)
> at javafx.scene.Scene$ScenePeerListener.mouseEvent(Scene.java:2267)
> at com.sun.javafx.tk.quantum.EmbeddedScene$2$1.run(EmbeddedScene.java:194)
> at com.sun.javafx.tk.quantum.EmbeddedScene$2$1.run(EmbeddedScene.java:176)
> at java.security.AccessController.doPrivileged(Native Method)
> at com.sun.javafx.tk.quantum.EmbeddedScene$2.run(EmbeddedScene.java:176)
> at com.sun.javafx.application.PlatformImpl$4$1.run(PlatformImpl.java:182)
> at com.sun.javafx.application.PlatformImpl$4$1.run(PlatformImpl.java:179)
> at java.security.AccessController.doPrivileged(Native Method)
> at com.sun.javafx.application.PlatformImpl$4.run(PlatformImpl.java:179)
> at com.sun.glass.ui.InvokeLaterDispatcher$Future.run(InvokeLaterDispatcher.java:76)
> 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:3414)
> at org.jboss.tools.vpe.browsersim.BrowserSimRunner.main(BrowserSimRunner.java:114)
> 2014-05-28 11:52:24.202:INFO:oejsh.ContextHandler:stopped o.e.j.s.ServletContextHandler{/,null}
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.2.3#6260)
11 years, 10 months
[JBoss JIRA] (JBIDE-17460) Exception when back button on mouse is pressed
by Ilya Buziuk (JIRA)
[ https://issues.jboss.org/browse/JBIDE-17460?page=com.atlassian.jira.plugi... ]
Ilya Buziuk commented on JBIDE-17460:
-------------------------------------
[~vpakan], mouse specific issue ;-). Need to go to our warehouse manager and grab a brand-new mouse
> Exception when back button on mouse is pressed
> ----------------------------------------------
>
> Key: JBIDE-17460
> URL: https://issues.jboss.org/browse/JBIDE-17460
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: browsersim
> Affects Versions: 4.2.0.Beta2
> Environment: JBDS 8.0.0.Beta2-v20140525-2146-B104
> Linux 64bit
> Java 1.7.0_51
> Reporter: Vlado Pakan
> Assignee: Konstantin Marmalyukov
> Priority: Critical
> Fix For: 4.2.0.Beta3
>
>
> 1.Open BrowserSim with empty page. BrowserSim is run with JavaFX engine
> 2.Click on empty page within BrowserSim
> 3.Click on Back button on mouse (back action is defined for back button on mouse within OS)
> ERROR:
> {noformat}
> 2014-05-28 11:52:08.348:INFO:oejs.AbstractConnector:Started SelectChannelConnector@0.0.0.0:56505
> Exception in runnable
> java.lang.NullPointerException
> at javafx.scene.Scene$ClickCounter.access$7600(Scene.java:3030)
> at javafx.scene.Scene$ClickGenerator.preProcess(Scene.java:3126)
> at javafx.scene.Scene$ClickGenerator.access$8400(Scene.java:3096)
> at javafx.scene.Scene$MouseHandler.process(Scene.java:3347)
> at javafx.scene.Scene$MouseHandler.process(Scene.java:3209)
> at javafx.scene.Scene$MouseHandler.access$1900(Scene.java:3164)
> at javafx.scene.Scene.impl_processMouseEvent(Scene.java:1582)
> at javafx.scene.Scene$ScenePeerListener.mouseEvent(Scene.java:2267)
> at com.sun.javafx.tk.quantum.EmbeddedScene$2$1.run(EmbeddedScene.java:194)
> at com.sun.javafx.tk.quantum.EmbeddedScene$2$1.run(EmbeddedScene.java:176)
> at java.security.AccessController.doPrivileged(Native Method)
> at com.sun.javafx.tk.quantum.EmbeddedScene$2.run(EmbeddedScene.java:176)
> at com.sun.javafx.application.PlatformImpl$4$1.run(PlatformImpl.java:182)
> at com.sun.javafx.application.PlatformImpl$4$1.run(PlatformImpl.java:179)
> at java.security.AccessController.doPrivileged(Native Method)
> at com.sun.javafx.application.PlatformImpl$4.run(PlatformImpl.java:179)
> at com.sun.glass.ui.InvokeLaterDispatcher$Future.run(InvokeLaterDispatcher.java:76)
> 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:3414)
> at org.jboss.tools.vpe.browsersim.BrowserSimRunner.main(BrowserSimRunner.java:114)
> Exception in runnable
> java.lang.NullPointerException
> at javafx.scene.Scene$ClickCounter.access$7900(Scene.java:3030)
> at javafx.scene.Scene$ClickGenerator.postProcess(Scene.java:3157)
> at javafx.scene.Scene$ClickGenerator.access$8600(Scene.java:3096)
> at javafx.scene.Scene$MouseHandler.process(Scene.java:3378)
> at javafx.scene.Scene$MouseHandler.process(Scene.java:3209)
> at javafx.scene.Scene$MouseHandler.access$1900(Scene.java:3164)
> at javafx.scene.Scene.impl_processMouseEvent(Scene.java:1582)
> at javafx.scene.Scene$ScenePeerListener.mouseEvent(Scene.java:2267)
> at com.sun.javafx.tk.quantum.EmbeddedScene$2$1.run(EmbeddedScene.java:194)
> at com.sun.javafx.tk.quantum.EmbeddedScene$2$1.run(EmbeddedScene.java:176)
> at java.security.AccessController.doPrivileged(Native Method)
> at com.sun.javafx.tk.quantum.EmbeddedScene$2.run(EmbeddedScene.java:176)
> at com.sun.javafx.application.PlatformImpl$4$1.run(PlatformImpl.java:182)
> at com.sun.javafx.application.PlatformImpl$4$1.run(PlatformImpl.java:179)
> at java.security.AccessController.doPrivileged(Native Method)
> at com.sun.javafx.application.PlatformImpl$4.run(PlatformImpl.java:179)
> at com.sun.glass.ui.InvokeLaterDispatcher$Future.run(InvokeLaterDispatcher.java:76)
> 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:3414)
> at org.jboss.tools.vpe.browsersim.BrowserSimRunner.main(BrowserSimRunner.java:114)
> 2014-05-28 11:52:24.202:INFO:oejsh.ContextHandler:stopped o.e.j.s.ServletContextHandler{/,null}
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.2.3#6260)
11 years, 10 months
[JBoss JIRA] (JBIDE-17207) Run tests on all major OS
by Mickael Istria (JIRA)
[ https://issues.jboss.org/browse/JBIDE-17207?page=com.atlassian.jira.plugi... ]
Mickael Istria edited comment on JBIDE-17207 at 6/4/14 9:30 AM:
----------------------------------------------------------------
First job of this kind: https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-aerogear_...
I'm not sure it has UI tests though... UI test might be the next challenge since I don't know if Windows/OSX configuration of slaves are able to start a SWT display without additional configuration.
> Run tests on all major OS
> -------------------------
>
> Key: JBIDE-17207
> URL: https://issues.jboss.org/browse/JBIDE-17207
> Project: Tools (JBoss Tools)
> Issue Type: Task
> Components: qa
> Reporter: Alexey Kazakov
> Assignee: Mickael Istria
> Fix For: 4.2.0.Beta3, 4.2.0.CR1
>
>
> Currently, our jenkins server runs JBT jUnit tests on Linux only. It would be good if we also run the tests on Windows and Mac.
> For example, we recently ran base, jst and javaee tests on Windows and got more than a hundred failures. Some of them indicated real bugs (not just tests problems). See JBIDE-17200.
> We don't have to run them every day. Maybe once a week or month?
> cc: [~maxandersen], [~dgolovin], [~nickboldt], [~mickael_istria]
--
This message was sent by Atlassian JIRA
(v6.2.3#6260)
11 years, 10 months