[JBoss JIRA] (JBIDE-17404) CordovaSim cannot be launched on RHEL7
by Karel Piwko (JIRA)
[ https://issues.jboss.org/browse/JBIDE-17404?page=com.atlassian.jira.plugi... ]
Karel Piwko updated JBIDE-17404:
--------------------------------
Attachment: libwebkit2gtk.content
webkitgtk.content
webkitgtk3.content
I'm attaching the content of webkit related packages on RHEL.
You can see that needed library is in webkitgtk, which is not available by default.
{code}
yum provides '*/libwebkitgtk-1.0.so.0'
Loaded plugins: langpacks, product-id, subscription-manager
google-chrome/filelists | 1.4 kB 00:00:00
webkitgtk-2.2.4-1.el7.x86_64 : GTK+ Web content engine library
Repo : epel
Matched from:
Filename : /usr/lib64/libwebkitgtk-1.0.so.0
webkitgtk-2.2.4-1.el7.x86_64 : GTK+ Web content engine library
Repo : @epel
Matched from:
Filename : /usr/lib64/libwebkitgtk-1.0.so.0
{code}
If using EPEL depedency is fine, I believe that RPM distros should use yum provide yum install combo in instructions as this is the most flexible.
> CordovaSim cannot be launched on RHEL7
> --------------------------------------
>
> Key: JBIDE-17404
> URL: https://issues.jboss.org/browse/JBIDE-17404
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: aerogear-hybrid, browsersim
> Environment: RHEL7 latest, 64bit
> Installed webkitgtk3-devel 0:2.0.4-6-el7
> TicketMonster Cordava example from latest WFK
> JBDS 8.0.0.Beta1
> OpenJDK 7
> Reporter: Karel Piwko
> Assignee: Konstantin Marmalyukov
> Fix For: 4.2.0.CR1
>
> Attachments: CordovaSimFailure.png, libwebkit2gtk.content, snapshot1.png, webkitgtk.content, webkitgtk3.content
>
>
> Launching BrowserSim fails with NPE, adding information from workspace log
> Before webkitgtk3-devel is installed
> {code}
> !ENTRY No engine information on the config.json, this is OK if using an old project. Falling back to default engine. 2 0 2014-05-23 13:03:54.128
> !MESSAGE org.jboss.tools.aerogear.hybrid.core
> !ENTRY org.jboss.tools.vpe.browsersim 4 0 2014-05-23 13:03:56.162
> !MESSAGE BrowserSim is failed to start with the following error:
> "No more handles"
> Please note that WebKitGTK 1.2.0 or newer must be installed and available in the library load path.
> If not, use your package manager to install libwebkitgtk.
> Also see <a href="https://community.jboss.org/docs/DOC-18100">BrowserSim FAQ</a>.
> Stack trace:
> org.eclipse.swt.SWTError: No more handles
> at org.eclipse.swt.SWT.error(SWT.java:4467)
> at org.eclipse.swt.SWT.error(SWT.java:4356)
> at org.eclipse.swt.SWT.error(SWT.java:4327)
> at org.eclipse.swt.browser.Browser.<init>(Browser.java:103)
> at org.jboss.tools.vpe.browsersim.browser.BrowserSimBrowser.<init>(BrowserSimBrowser.java:36)
> at org.jboss.tools.vpe.browsersim.browser.AbstractWebKitBrowser.<init>(AbstractWebKitBrowser.java:25)
> at org.jboss.tools.vpe.browsersim.browser.internal.WebKitBrowser_gtk_linux_x86_64.<init>(WebKitBrowser_gtk_linux_x86_64.java:37)
> at org.jboss.tools.vpe.browsersim.browser.WebKitBrowserFactory.createBrowser(WebKitBrowserFactory.java:39)
> at org.jboss.tools.vpe.cordovasim.CordovaSimRunner.createCordovaSim(CordovaSimRunner.java:189)
> at org.jboss.tools.vpe.cordovasim.CordovaSimRunner.startCordovaSim(CordovaSimRunner.java:90)
> at org.jboss.tools.vpe.cordovasim.CordovaSimRunner.main(CordovaSimRunner.java:84)
> {code}
> After:
> {code}
> !ENTRY No engine information on the config.json, this is OK if using an old project. Falling back to default engine. 2 0 2014-05-23 14:03:57.380
> !MESSAGE org.jboss.tools.aerogear.hybrid.core
> !ENTRY No engine information on the config.json, this is OK if using an old project. Falling back to default engine. 2 0 2014-05-23 14:03:57.380
> !MESSAGE org.jboss.tools.aerogear.hybrid.core
> !ENTRY org.eclipse.core.jobs 4 2 2014-05-23 14:03:57.395
> !MESSAGE An internal error occurred during: "Launching TicketMonster-Cordova".
> !STACK 0
> java.lang.NullPointerException
> at org.jboss.tools.vpe.cordovasim.eclipse.launch.internal.CordovaSimLauncher.launchCordovaSim(CordovaSimLauncher.java:157)
> at org.jboss.tools.vpe.cordovasim.eclipse.launch.internal.CordovaSimLauncher.launchCordovaSim(CordovaSimLauncher.java:115)
> at org.jboss.tools.vpe.cordovasim.eclipse.launch.internal.CordovaSimLaunchConfigurationDelegate.launch(CordovaSimLaunchConfigurationDelegate.java:24)
> at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:884)
> at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:739)
> at org.eclipse.debug.internal.ui.DebugUIPlugin.buildAndLaunch(DebugUIPlugin.java:1039)
> at org.eclipse.debug.internal.ui.DebugUIPlugin$8.run(DebugUIPlugin.java:1256)
> at org.eclipse.core.internal.jobs.Worker.run(Worker.java:53)
> {code}
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)
11 years, 9 months
[JBoss JIRA] (JBIDE-17552) JBoss EWP isn't added into Servers by JBoss Tools Runtime Detection
by Martin Malina (JIRA)
[ https://issues.jboss.org/browse/JBIDE-17552?page=com.atlassian.jira.plugi... ]
Martin Malina commented on JBIDE-17552:
---------------------------------------
But I just checked in JBDS 8.0.0.Beta2 and Jirka is right, EWP can't be added. It is detected, but the server isn't really added.
Steps:
1. Go go Preferences -> JBoss Tools -> Runtime Detection
2. Click Add and add a directory with EWP 5.2
3. In the search results table, you can see that the EWP server was found - leave it checked and click OK to add it.
4. Check the server view - there will be no server - FAIL (the runtime is missing, too)
> JBoss EWP isn't added into Servers by JBoss Tools Runtime Detection
> -------------------------------------------------------------------
>
> Key: JBIDE-17552
> URL: https://issues.jboss.org/browse/JBIDE-17552
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: runtime-detection
> Affects Versions: 4.2.0.Beta2
> Environment: JBDS 8.0.0.Beta2a, GNU/Linux 64
> Reporter: Jiri Peterka
> Assignee: Rob Stryker
> Fix For: 4.2.0.CR1
>
>
> There is no EWP 5.2 added into Server View. EWP is detected by JBT Runtime Detection but no server added.
> I noticed that when trying on new workspace, that when EWP was selected it created another server but AS7 which was not selected for runtime detection. So I guess there si some bug there.
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)
11 years, 9 months
[JBoss JIRA] (JBIDE-17311) jvmmonitor agent project moved + renamed into jbt-server repo
by Rob Stryker (JIRA)
[ https://issues.jboss.org/browse/JBIDE-17311?page=com.atlassian.jira.plugi... ]
Rob Stryker commented on JBIDE-17311:
-------------------------------------
A check on the jmx repo (to verify that nobody specifically is polling these mbeans) shows that there's nobody is hard-coding these mbean names or packages.
{code}
[rob@localhost jmx]$ pwd
/home/rob/code/jbtools/github/jbosstools-server/jmx
[rob@localhost jmx]$ grep -R "com.fuse" *
Binary file plugins/org.jboss.tools.jmx.jvmmonitor.core/lib/jvmmonitor-agent.jar matches
{code}
This means it should be safe to rebuild the agent jar with different package names.
> jvmmonitor agent project moved + renamed into jbt-server repo
> -------------------------------------------------------------
>
> Key: JBIDE-17311
> URL: https://issues.jboss.org/browse/JBIDE-17311
> Project: Tools (JBoss Tools)
> Issue Type: Sub-task
> Components: jmx
> Affects Versions: 4.2.0.Beta2
> Reporter: Rob Stryker
>
> The file "jvmmonitor-agent.jar" is currently a built component separate from its project. This must be somehow unified with the other jvm-monitor code in terms of where it lives and how it gets built.
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)
11 years, 9 months