[JBoss JIRA] (JBIDE-14537) BrowserSim 4.1.0.Beta1 - JUnit failure WebKitTests.testWebKitSetDefaultUserAgent
by Yahor Radtsevich (JIRA)
[ https://issues.jboss.org/browse/JBIDE-14537?page=com.atlassian.jira.plugi... ]
Yahor Radtsevich commented on JBIDE-14537:
------------------------------------------
Konstantin created JBIDE-14835: Test testAddRemovingDOMElements fails.
> BrowserSim 4.1.0.Beta1 - JUnit failure WebKitTests.testWebKitSetDefaultUserAgent
> --------------------------------------------------------------------------------
>
> Key: JBIDE-14537
> URL: https://issues.jboss.org/browse/JBIDE-14537
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: browsersim
> Affects Versions: 4.1.0.Beta1
> Reporter: Yahor Radtsevich
> Assignee: Nick Boldt
> Fix For: 4.1.0.Beta2
>
>
> https://hudson.jboss.org/hudson/view/JBossTools/view/JBossTools_4.1.keple...
> org.jboss.tools.vpe.browsersim.browser.test.WebKitTests.testWebKitSetDefaultUserAgent
> {code}
> org.eclipse.swt.SWTError: No more handles
> at org.eclipse.swt.SWT.error(SWT.java:4418)
> at org.eclipse.swt.SWT.error(SWT.java:4307)
> at org.eclipse.swt.SWT.error(SWT.java:4278)
> at org.eclipse.swt.browser.Browser.<init>(Browser.java:103)
> at org.jboss.tools.vpe.browsersim.browser.BrowserSimBrowser.<init>(BrowserSimBrowser.java:9)
> at org.jboss.tools.vpe.browsersim.browser.AbstractWebKitBrowser.<init>(AbstractWebKitBrowser.java:24)
> at org.jboss.tools.vpe.browsersim.browser.internal.WebKitBrowser_gtk_linux_x86_64.<init>(WebKitBrowser_gtk_linux_x86_64.java:38)
> at org.jboss.tools.vpe.browsersim.browser.WebKitBrowserFactory.createBrowser(WebKitBrowserFactory.java:36)
> at org.jboss.tools.vpe.browsersim.browser.test.WebKitTests.testWebKitSetDefaultUserAgent(WebKitTests.java:39)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
> at java.lang.reflect.Method.invoke(Method.java:597)
> at junit.framework.TestCase.runTest(TestCase.java:176)
> at junit.framework.TestCase.runBare(TestCase.java:141)
> at junit.framework.TestResult$1.protect(TestResult.java:122)
> at junit.framework.TestResult.runProtected(TestResult.java:142)
> at junit.framework.TestResult.run(TestResult.java:125)
> at junit.framework.TestCase.run(TestCase.java:129)
> at junit.framework.TestSuite.runTest(TestSuite.java:255)
> at junit.framework.TestSuite.run(TestSuite.java:250)
> at junit.framework.TestSuite.runTest(TestSuite.java:255)
> at junit.framework.TestSuite.run(TestSuite.java:250)
> at org.junit.internal.runners.JUnit38ClassRunner.run(JUnit38ClassRunner.java:84)
> at org.apache.maven.surefire.junit4.JUnit4TestSet.execute(JUnit4TestSet.java:53)
> at org.apache.maven.surefire.junit4.JUnit4Provider.executeTestSet(JUnit4Provider.java:123)
> at org.apache.maven.surefire.junit4.JUnit4Provider.invoke(JUnit4Provider.java:104)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
> at java.lang.reflect.Method.invoke(Method.java:597)
> at org.apache.maven.surefire.util.ReflectionUtils.invokeMethodWithArray(ReflectionUtils.java:164)
> at org.apache.maven.surefire.booter.ProviderFactory$ProviderProxy.invoke(ProviderFactory.java:110)
> at org.apache.maven.surefire.booter.SurefireStarter.invokeProvider(SurefireStarter.java:175)
> at org.apache.maven.surefire.booter.SurefireStarter.runSuitesInProcess(SurefireStarter.java:123)
> at org.eclipse.tycho.surefire.osgibooter.OsgiSurefireBooter.run(OsgiSurefireBooter.java:85)
> at org.eclipse.tycho.surefire.osgibooter.AbstractUITestApplication$1.run(AbstractUITestApplication.java:35)
> 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:3692)
> at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3341)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$9.run(PartRenderingEngine.java:1108)
> at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.run(PartRenderingEngine.java:992)
> at org.eclipse.e4.ui.internal.workbench.E4Workbench.createAndRunUI(E4Workbench.java:137)
> at org.eclipse.ui.internal.Workbench$5.run(Workbench.java:600)
> at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332)
> at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:555)
> at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:149)
> at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:124)
> at org.eclipse.tycho.surefire.osgibooter.UITestApplication.runApplication(UITestApplication.java:31)
> at org.eclipse.tycho.surefire.osgibooter.AbstractUITestApplication.run(AbstractUITestApplication.java:114)
> 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:110)
> at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:79)
> at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:354)
> at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:181)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
> at java.lang.reflect.Method.invoke(Method.java:597)
> at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:636)
> at org.eclipse.equinox.launcher.Main.basicRun(Main.java:591)
> at org.eclipse.equinox.launcher.Main.run(Main.java:1450)
> at org.eclipse.equinox.launcher.Main.main(Main.java:1426)
> {code}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 10 months
[JBoss JIRA] (JBIDE-14830) CordovaSim: Weinre doesn't work
by Yahor Radtsevich (JIRA)
[ https://issues.jboss.org/browse/JBIDE-14830?page=com.atlassian.jira.plugi... ]
Yahor Radtsevich updated JBIDE-14830:
-------------------------------------
Fix Version/s: 4.1.0.Beta2
> CordovaSim: Weinre doesn't work
> -------------------------------
>
> Key: JBIDE-14830
> URL: https://issues.jboss.org/browse/JBIDE-14830
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: browsersim
> Affects Versions: 4.1.0.Beta1
> Environment: Fedora 18 or 19
> JBDS 7.0.0.Beta1
> with following updates from JBoss Tools 4.1.0.Beta1 update site [1]:
> {code}
> JBoss Mobile Hybrid Application Development Tools (Experimental) 1.0.0.Beta1-v20130523-2211-B7
> JBoss Tools Apache Cordova Simulator 3.5.0.Beta1-v20130525-0825-B60
> JBoss Tools Mobile Browser Simulator 3.5.0.Beta1-v20130525-0825-B60
> {code}
> java version "1.7.0_19"
> OpenJDK Runtime Environment (fedora-2.3.9.5.fc18-x86_64)
> OpenJDK 64-Bit Server VM (build 23.7-b01, mixed mode)
> [1] http://download.jboss.org/jbosstools/updates/development/kepler/
> Reporter: Lukáš Fryč
> Assignee: Konstantin Marmalyukov
> Fix For: 4.1.0.Beta2
>
>
> Steps to Reproduce:
> 1) create new Hybrid Mobile (Cordova) Application Project
> 2) Project.. Run As > Run with CordovaSim
> app works as expected
> 3) start Debug > Weinre (BrowserSim context menu)
> FAIL: new window opens but nothing is visible there (just blank white window)
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 10 months
[JBoss JIRA] (JBIDE-14830) CordovaSim: Weinre doesn't work
by Yahor Radtsevich (JIRA)
[ https://issues.jboss.org/browse/JBIDE-14830?page=com.atlassian.jira.plugi... ]
Yahor Radtsevich reassigned JBIDE-14830:
----------------------------------------
Assignee: Konstantin Marmalyukov
> CordovaSim: Weinre doesn't work
> -------------------------------
>
> Key: JBIDE-14830
> URL: https://issues.jboss.org/browse/JBIDE-14830
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: browsersim
> Affects Versions: 4.1.0.Beta1
> Environment: Fedora 18 or 19
> JBDS 7.0.0.Beta1
> with following updates from JBoss Tools 4.1.0.Beta1 update site [1]:
> {code}
> JBoss Mobile Hybrid Application Development Tools (Experimental) 1.0.0.Beta1-v20130523-2211-B7
> JBoss Tools Apache Cordova Simulator 3.5.0.Beta1-v20130525-0825-B60
> JBoss Tools Mobile Browser Simulator 3.5.0.Beta1-v20130525-0825-B60
> {code}
> java version "1.7.0_19"
> OpenJDK Runtime Environment (fedora-2.3.9.5.fc18-x86_64)
> OpenJDK 64-Bit Server VM (build 23.7-b01, mixed mode)
> [1] http://download.jboss.org/jbosstools/updates/development/kepler/
> Reporter: Lukáš Fryč
> Assignee: Konstantin Marmalyukov
>
> Steps to Reproduce:
> 1) create new Hybrid Mobile (Cordova) Application Project
> 2) Project.. Run As > Run with CordovaSim
> app works as expected
> 3) start Debug > Weinre (BrowserSim context menu)
> FAIL: new window opens but nothing is visible there (just blank white window)
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 10 months
[JBoss JIRA] (TOOLSDOC-345) NeedInfo: Distinction between Eclipse and JBDS/JBT Server Tools
by Rob Stryker (JIRA)
[ https://issues.jboss.org/browse/TOOLSDOC-345?page=com.atlassian.jira.plug... ]
Rob Stryker commented on TOOLSDOC-345:
--------------------------------------
In general you're pretty close to the mark. The new -> Server action basically creates what I call a server adapter, while I call the actual thing in c:\apps\jboss\jboss-as-7.1.0 either the server or the runtime or the server's runtime. There's always this underlying feeling that the server involves some type of running state, whereas a runtime is just the thing that is a bunch of jars and classes glued together. The runtime can be used to compile projects, be on the classpath of a project, or, can be used by a server adapter to launch or start a server.
In genereal though you're right. You're creating the configuration changes, command line args, and other customizations that will make it into the running server.
But in my head I typically call the thing inside eclipse a server just to be short. It really is a server adapter, and I feel the server (or runtime) is what lives on your hard-drive. You're never *really* creating one, or deleting one.... except in rare situations (such as download-runtimes)
> NeedInfo: Distinction between Eclipse and JBDS/JBT Server Tools
> ---------------------------------------------------------------
>
> Key: TOOLSDOC-345
> URL: https://issues.jboss.org/browse/TOOLSDOC-345
> Project: Documentation for JBoss Tools and Developer Studio
> Issue Type: Task
> Security Level: Public(Everyone can see)
> Components: User Guide - JBoss Server Tools
> Affects Versions: 4.1.0
> Reporter: Michelle Murray
> Assignee: Rob Stryker
> Fix For: 4.1.0
>
>
> I am trying to distinguish which features are provided by Eclipse and which are provided by JBoss Server Tools so that I can accurately document JBoss Server Tools.
> The unique JBoss Server Tools features I have are:
> * automatic runtime detection
> * ability to download and install a JBoss runtime
> * JBoss Server Editor - lots of the panes in the overview tab are unique and * the deployment tab is completely unique
> * set a default server icon
> * set default filesets
> * set default classpath entries
> * create new server wizard also seems different for JBoss enterprise and community servers than in the wizard in Eclipse alone
> What have I missed?
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 10 months
[JBoss JIRA] (JBIDE-14838) Manage SSH Keys: Auth error on fresh start
by Stefan Bunciak (JIRA)
Stefan Bunciak created JBIDE-14838:
--------------------------------------
Summary: Manage SSH Keys: Auth error on fresh start
Key: JBIDE-14838
URL: https://issues.jboss.org/browse/JBIDE-14838
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: openshift
Affects Versions: 4.1.0.Beta1
Reporter: Stefan Bunciak
Fix For: 4.1.0.Beta2
{code}
com.openshift.client.OpenShiftEndpointException: Could not request https://openshift.redhat.com/broker/rest/user/keys: Operation failed.Reason given: "Unable to complete the requested operation due to: OpenShift::AuthServiceException.
Reference ID: 2cf923693cafe4085e20365c714d22d6"
at com.openshift.internal.client.RestService.request(RestService.java:117)
at com.openshift.internal.client.RestService.request(RestService.java:102)
at com.openshift.internal.client.RestService.request(RestService.java:87)
at com.openshift.internal.client.AbstractOpenShiftResource$ServiceRequest.execute(AbstractOpenShiftResource.java:123)
at com.openshift.internal.client.UserResource$GetSShKeysRequest.execute(UserResource.java:245)
at com.openshift.internal.client.UserResource.loadKeys(UserResource.java:137)
at com.openshift.internal.client.UserResource.getCachedOrLoadSSHKeys(UserResource.java:129)
at com.openshift.internal.client.UserResource.getSSHKeys(UserResource.java:122)
at org.jboss.tools.openshift.express.internal.core.connection.Connection.getSSHKeys(Connection.java:392)
at org.jboss.tools.openshift.express.internal.ui.job.LoadKeysJob.run(LoadKeysJob.java:38)
at org.eclipse.core.internal.jobs.Worker.run(Worker.java:53)
Caused by: com.openshift.internal.client.httpclient.HttpClientException: {"data":null,"messages":[{"exit_code":null,"field":null,"severity":"error","text":"Unable to complete the requested operation due to: OpenShift::AuthServiceException.\nReference ID: 2cf923693cafe4085e20365c714d22d6"}],"status":"internal_server_error","supported_api_versions":[1.0,1.1,1.2,1.3,1.4],"type":null,"version":"1.2"}
at com.openshift.internal.client.httpclient.UrlConnectionHttpClient.createException(UrlConnectionHttpClient.java:208)
at com.openshift.internal.client.httpclient.UrlConnectionHttpClient.write(UrlConnectionHttpClient.java:180)
at com.openshift.internal.client.httpclient.UrlConnectionHttpClient.get(UrlConnectionHttpClient.java:111)
at com.openshift.internal.client.RestService.request(RestService.java:153)
at com.openshift.internal.client.RestService.request(RestService.java:109)
... 10 more
Caused by: java.io.IOException: Server returned HTTP response code: 500 for URL: https://openshift.redhat.com/broker/rest/user/keys
at sun.net.www.protocol.http.HttpURLConnection.getInputStream(HttpURLConnection.java:1436)
at sun.net.www.protocol.https.HttpsURLConnectionImpl.getInputStream(HttpsURLConnectionImpl.java:234)
at com.openshift.internal.client.httpclient.UrlConnectionHttpClient.write(UrlConnectionHttpClient.java:178)
... 13 more
{code}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 10 months
[JBoss JIRA] (TOOLSDOC-345) NeedInfo: Distinction between Eclipse and JBDS/JBT Server Tools
by Michelle Murray (JIRA)
[ https://issues.jboss.org/browse/TOOLSDOC-345?page=com.atlassian.jira.plug... ]
Michelle Murray commented on TOOLSDOC-345:
------------------------------------------
Wow! Thanks for writing such a detailed comment. I really appreciate it and certainly needed it as I was way off the mark and using the wrong names for things, which only lead to further confusion.
Things are a lot clearer now:
* You have an application server on your system. For example, EAP 6.0.
* To use an application server with the IDE, you need to create at least one server runtime environment (abbrev. here to SRE). An SRE informs the IDE about the application server's local location, which config file and JRE to use.
* You can have multiple SREs for one application server, each with config variations. For example, one SRE with EAP 6.0 & JDK 1.6 and then another SRE with EAP 6.0 & JDK 1.6.
* Config of individual SREs is under Preferences > Servers > Runtime Environments, also accessible via new server wizard.
* To deploy an app to an application server using a specific SRE, you need to create at least one server adapter (or 'server'). A server adapter informs the IDE of further config details that specify an application server's management, such as launching and publishing.
* You can have multiple server adapters for one SRE, each with config variations. For example, two server adapters can use the same SRE, one for a local application server and one for a remote application server; or one server adapter in which publishing happens when changes are detected and the other only publishing with manual republish.
* Config of individual server adapters is via the new server wizard or in the servers editor.
I was finding it hard to know when to use 'server adapter' or 'server' as the IDE seems to use the latter for the former. For instance in the context menu of the servers tab, specifically New > Server. To me, this action creates a server adapter. So I have reconciled this in my head as follows: When you create a server adapter you are in essence creating a server; you specify the management settings that define a specific 'server instance' = you define a server of application server type x with config settings y to which apps can be deployed. *What do you think?*
> NeedInfo: Distinction between Eclipse and JBDS/JBT Server Tools
> ---------------------------------------------------------------
>
> Key: TOOLSDOC-345
> URL: https://issues.jboss.org/browse/TOOLSDOC-345
> Project: Documentation for JBoss Tools and Developer Studio
> Issue Type: Task
> Security Level: Public(Everyone can see)
> Components: User Guide - JBoss Server Tools
> Affects Versions: 4.1.0
> Reporter: Michelle Murray
> Assignee: Rob Stryker
> Fix For: 4.1.0
>
>
> I am trying to distinguish which features are provided by Eclipse and which are provided by JBoss Server Tools so that I can accurately document JBoss Server Tools.
> The unique JBoss Server Tools features I have are:
> * automatic runtime detection
> * ability to download and install a JBoss runtime
> * JBoss Server Editor - lots of the panes in the overview tab are unique and * the deployment tab is completely unique
> * set a default server icon
> * set default filesets
> * set default classpath entries
> * create new server wizard also seems different for JBoss enterprise and community servers than in the wizard in Eclipse alone
> What have I missed?
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 10 months
[JBoss JIRA] (JBDS-1234) Installer could check OS architecture
by Jiri Peterka (JIRA)
[ https://issues.jboss.org/browse/JBDS-1234?page=com.atlassian.jira.plugin.... ]
Jiri Peterka commented on JBDS-1234:
------------------------------------
Yes, request related to unsupported OS is obsolete now.A warning message saying a user is installing package with 32bit JVM on 64bit system might be useful hint for a user. But it's not an important issue I agree.
> Installer could check OS architecture
> -------------------------------------
>
> Key: JBDS-1234
> URL: https://issues.jboss.org/browse/JBDS-1234
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Feature Request
> Security Level: Public(Everyone can see)
> Components: installer
> Affects Versions: 3.0.1.GA
> Reporter: Jiri Peterka
> Assignee: Denis Golovin
> Fix For: LATER
>
>
> Installer could check OS architecture, for example if installing 32-bit package on 64 bit OS there should be a warning and non-compatible package should be forced to exit installation.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
12 years, 10 months