December 2014 - jbosstools-issues

[JBoss JIRA] (JBIDE-18979) Unable to run CordovaSim with Fedora 21 KDE

by Ilya Buziuk (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18979?page=com.atlassian.jira.plugi... ] Ilya Buziuk commented on JBIDE-18979: ------------------------------------- [~vpakan] here is what I have sorted out by now: Fedora 21 KDE / GNOME 1. Can't use SWT.WEBKIT web engine against GTK 2 - getting the error message on start up. Eventhought I have installed *libwebkitgt-1.0.so.0*: !webkit.png|thumbnail! 2. Both BrowserSim and CordovaSim works fine against GTK 2 using JavaFx web engine against Oracle JDK 7 / 8 3. Both BrowserSim and CordovaSim works fine against GTK 3 with SWT.WEBKIT web engine On balance, everything seems to be fine except (1). Also I do belive that trere were no such problem (1) on Fedora 20 > Unable to run CordovaSim with Fedora 21 KDE > ------------------------------------------- > > Key: JBIDE-18979 > URL: https://issues.jboss.org/browse/JBIDE-18979 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: cordovasim > Affects Versions: 4.2.1.Final > Environment: JBDS 8.0.1.CR1-v20141207-0100-B352, Java Oracle 1.8 > Fedora 21 KDE 64 bit > Reporter: Vlado Pakan > Assignee: Ilya Buziuk > Priority: Critical > Attachments: webkit.png > > > 1. Run default Hybrid Mobile app with CordovaSim > {noformat} > No bp log location saved, using default. > [000:000] Cpu: 6.42.7, x4, 3500Mhz, 7867MB > [000:000] Computer model: Not available > [000:000] Browser XEmbed support present: 1 > [000:000] Browser toolkit is Gtk2. > [000:003] Using Gtk2 toolkit > No bp log location saved, using default. > [000:000] Cpu: 6.42.7, x4, 3500Mhz, 7867MB > [000:001] Computer model: Not available > [000:497] Warning(optionsfile.cc:30): Load: Could not open file, err=2 > [000:497] No bp log location saved, using default. > [000:497] Cpu: 6.42.7, x4, 3500Mhz, 7867MB > [000:497] Computer model: Not available > [000:498] Browser XEmbed support present: 1 > [000:498] Browser toolkit is Gtk2. > [000:498] Using Gtk2 toolkit > [000:003] Warning(optionsfile.cc:30): Load: Could not open file, err=2 > [000:003] No bp log location saved, using default. > [000:004] Cpu: 6.42.7, x4, 3500Mhz, 7867MB > [000:004] Computer model: Not available > (SWT:13580): GLib-GObject-CRITICAL **: g_closure_unref: assertion 'closure->ref_count > 0' failed > (SWT:13580): GLib-GObject-CRITICAL **: g_closure_unref: assertion 'closure->ref_count > 0' failed > (SWT:13580): GLib-GObject-CRITICAL **: g_closure_unref: assertion 'closure->ref_count > 0' failed > (SWT:13580): GLib-GObject-CRITICAL **: g_closure_unref: assertion 'closure->ref_count > 0' failed > (SWT:13580): GLib-GObject-CRITICAL **: g_closure_unref: assertion 'closure->ref_count > 0' failed > (SWT:13580): GLib-GObject-CRITICAL **: g_closure_unref: assertion 'closure->ref_count > 0' failed > (SWT:13580): GLib-GObject-CRITICAL **: g_closure_unref: assertion 'closure->ref_count > 0' failed > (SWT:13580): GLib-GObject-CRITICAL **: g_closure_unref: assertion 'closure->ref_count > 0' failed > # > # A fatal error has been detected by the Java Runtime Environment: > # > # SIGSEGV (0xb) at pc=0x000000370a80c42b, pid=13580, tid=140558422947584 > # > # JRE version: Java(TM) SE Runtime Environment (8.0-b132) (build 1.8.0-b132) > # Java VM: Java HotSpot(TM) 64-Bit Server VM (25.0-b70 mixed mode linux-amd64 compressed oops) > # Problematic frame: > # C [ld-linux-x86-64.so.2+0xc42b] > # > # Failed to write core dump. Core dumps have been disabled. To enable core dumping, try "ulimit -c unlimited" before starting Java again > # > # An error report file with more information is saved as: > # /home/vpakan/hs_err_pid13580.log > # > # If you would like to submit a bug report, please visit: > # http://bugreport.sun.com/bugreport/crash.jsp > # The crash happened outside the Java Virtual Machine in native code. > # See problematic frame for where to report the bug. > # > {noformat} -- This message was sent by Atlassian JIRA (v6.3.11#6341)

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18979) Unable to run CordovaSim with Fedora 21 KDE

by Ilya Buziuk (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18979?page=com.atlassian.jira.plugi... ] Ilya Buziuk updated JBIDE-18979: -------------------------------- Attachment: webkit.png > Unable to run CordovaSim with Fedora 21 KDE > ------------------------------------------- > > Key: JBIDE-18979 > URL: https://issues.jboss.org/browse/JBIDE-18979 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: cordovasim > Affects Versions: 4.2.1.Final > Environment: JBDS 8.0.1.CR1-v20141207-0100-B352, Java Oracle 1.8 > Fedora 21 KDE 64 bit > Reporter: Vlado Pakan > Assignee: Ilya Buziuk > Priority: Critical > Attachments: webkit.png > > > 1. Run default Hybrid Mobile app with CordovaSim > {noformat} > No bp log location saved, using default. > [000:000] Cpu: 6.42.7, x4, 3500Mhz, 7867MB > [000:000] Computer model: Not available > [000:000] Browser XEmbed support present: 1 > [000:000] Browser toolkit is Gtk2. > [000:003] Using Gtk2 toolkit > No bp log location saved, using default. > [000:000] Cpu: 6.42.7, x4, 3500Mhz, 7867MB > [000:001] Computer model: Not available > [000:497] Warning(optionsfile.cc:30): Load: Could not open file, err=2 > [000:497] No bp log location saved, using default. > [000:497] Cpu: 6.42.7, x4, 3500Mhz, 7867MB > [000:497] Computer model: Not available > [000:498] Browser XEmbed support present: 1 > [000:498] Browser toolkit is Gtk2. > [000:498] Using Gtk2 toolkit > [000:003] Warning(optionsfile.cc:30): Load: Could not open file, err=2 > [000:003] No bp log location saved, using default. > [000:004] Cpu: 6.42.7, x4, 3500Mhz, 7867MB > [000:004] Computer model: Not available > (SWT:13580): GLib-GObject-CRITICAL **: g_closure_unref: assertion 'closure->ref_count > 0' failed > (SWT:13580): GLib-GObject-CRITICAL **: g_closure_unref: assertion 'closure->ref_count > 0' failed > (SWT:13580): GLib-GObject-CRITICAL **: g_closure_unref: assertion 'closure->ref_count > 0' failed > (SWT:13580): GLib-GObject-CRITICAL **: g_closure_unref: assertion 'closure->ref_count > 0' failed > (SWT:13580): GLib-GObject-CRITICAL **: g_closure_unref: assertion 'closure->ref_count > 0' failed > (SWT:13580): GLib-GObject-CRITICAL **: g_closure_unref: assertion 'closure->ref_count > 0' failed > (SWT:13580): GLib-GObject-CRITICAL **: g_closure_unref: assertion 'closure->ref_count > 0' failed > (SWT:13580): GLib-GObject-CRITICAL **: g_closure_unref: assertion 'closure->ref_count > 0' failed > # > # A fatal error has been detected by the Java Runtime Environment: > # > # SIGSEGV (0xb) at pc=0x000000370a80c42b, pid=13580, tid=140558422947584 > # > # JRE version: Java(TM) SE Runtime Environment (8.0-b132) (build 1.8.0-b132) > # Java VM: Java HotSpot(TM) 64-Bit Server VM (25.0-b70 mixed mode linux-amd64 compressed oops) > # Problematic frame: > # C [ld-linux-x86-64.so.2+0xc42b] > # > # Failed to write core dump. Core dumps have been disabled. To enable core dumping, try "ulimit -c unlimited" before starting Java again > # > # An error report file with more information is saved as: > # /home/vpakan/hs_err_pid13580.log > # > # If you would like to submit a bug report, please visit: > # http://bugreport.sun.com/bugreport/crash.jsp > # The crash happened outside the Java Virtual Machine in native code. > # See problematic frame for where to report the bug. > # > {noformat} -- This message was sent by Atlassian JIRA (v6.3.11#6341)

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18768) Document use cases where JST Tern integration is taking place

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18768?page=com.atlassian.jira.plugi... ] Denis Golovin updated JBIDE-18768: ---------------------------------- Fix Version/s: 4.2.2.Final (was: 4.2.x) > Document use cases where JST Tern integration is taking place > ------------------------------------------------------------- > > Key: JBIDE-18768 > URL: https://issues.jboss.org/browse/JBIDE-18768 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: jsp/jsf/xml/html source editing > Affects Versions: 4.2.0.Final > Reporter: Denis Golovin > Assignee: Denis Golovin > Fix For: 4.2.2.Final > > > We need to keep list of use cases where jst tern integration bundle is doing tern/angularjs configuration behind the scene. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3262) Deprecate Visual JSF Preview & Editing

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBDS-3262?page=com.atlassian.jira.plugin.... ] Denis Golovin commented on JBDS-3262: ------------------------------------- It should be easy enough for deprecation: 1. The xulrunner feature should be marked as deprecated and org.jboss.tools.vpe.xulrunner requirements to xulrunner platform specific bundles should be marked as optional none greedy. It would mean no JSF Preview Editing by default available until xulrunner feature is manually installed. 2. There should be user friendly message in case of opening jsf pages in vpe about deprecation and xulrunner manual installation. > Deprecate Visual JSF Preview & Editing > -------------------------------------- > > Key: JBDS-3262 > URL: https://issues.jboss.org/browse/JBDS-3262 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Feature Request > Components: requirements, visual-page-editor-core > Reporter: Burr Sutter > Assignee: Konstantin Marmalyukov > Fix For: 8.1.0.GA, 9.0.0.Alpha1 > > > Note: JSF will remain supported as part of JBDS for EAP5, 6 , 7 and beyond as it is part of the Java EE specification. This deprecation notice specifically for the visual/source and preview editors. It does not currently work for 64-bit JVMs and a fair number of our end-users are moving to 64-bit JVMs. > This is the "deprecation notice" - actual removal of the visual/source and preview tabs is JBDS-3263 > http://screencast.com/t/zur1sCXmZ > http://screencast.com/t/wettTf6s6cU -- This message was sent by Atlassian JIRA (v6.3.11#6341)

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18669) HTML5 Palette: Custom palette group

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18669?page=com.atlassian.jira.plugi... ] Alexey Kazakov updated JBIDE-18669: ----------------------------------- Fix Version/s: 4.3.0.Alpha1 (was: 4.3.x) > HTML5 Palette: Custom palette group > ----------------------------------- > > Key: JBIDE-18669 > URL: https://issues.jboss.org/browse/JBIDE-18669 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: jsp/jsf/xml/html source editing > Reporter: Daniel Azarov > Assignee: Daniel Azarov > Labels: new_and_noteworthy > Fix For: 4.3.0.Alpha1 > > > It would be nice to have custom HTML5 Palette group. > It should be possible for users to select which items to show in that group: > 1. Last used items > 2. The most popular items > It should be possible to limit number of items. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18669) HTML5 Palette: Custom palette group

by Daniel Azarov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18669?page=com.atlassian.jira.plugi... ] Daniel Azarov updated JBIDE-18669: ---------------------------------- Description: It would be nice to have custom HTML5 Palette group. It should be possible for users to select which items to show in that group: 1. Last used items 2. The most popular items It should be possible to limit number of items. was: It would be nice to have custom HTML5 Palette group. It should be possible for users to select which items to show in that group: 1. Last used items 2. The most popular items It should be possible to limit number of items and edit set of items > HTML5 Palette: Custom palette group > ----------------------------------- > > Key: JBIDE-18669 > URL: https://issues.jboss.org/browse/JBIDE-18669 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: jsp/jsf/xml/html source editing > Reporter: Daniel Azarov > Assignee: Daniel Azarov > Labels: new_and_noteworthy > Fix For: 4.3.x > > > It would be nice to have custom HTML5 Palette group. > It should be possible for users to select which items to show in that group: > 1. Last used items > 2. The most popular items > It should be possible to limit number of items. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18980) New Table wizard for HTML5 palette

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18980?page=com.atlassian.jira.plugi... ] Alexey Kazakov updated JBIDE-18980: ----------------------------------- Description: !table.png! > New Table wizard for HTML5 palette > ---------------------------------- > > Key: JBIDE-18980 > URL: https://issues.jboss.org/browse/JBIDE-18980 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: jsp/jsf/xml/html source editing > Affects Versions: 4.3.0.Alpha1 > Reporter: Viacheslav Kabanovich > Assignee: Viacheslav Kabanovich > Labels: new_and_noteworthy > Fix For: 4.3.0.Alpha1 > > Attachments: table.png > > > !table.png! -- This message was sent by Atlassian JIRA (v6.3.11#6341)

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18980) New Table wizard for HTML5 palette

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18980?page=com.atlassian.jira.plugi... ] Alexey Kazakov updated JBIDE-18980: ----------------------------------- Attachment: table.png > New Table wizard for HTML5 palette > ---------------------------------- > > Key: JBIDE-18980 > URL: https://issues.jboss.org/browse/JBIDE-18980 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: jsp/jsf/xml/html source editing > Affects Versions: 4.3.0.Alpha1 > Reporter: Viacheslav Kabanovich > Assignee: Viacheslav Kabanovich > Labels: new_and_noteworthy > Fix For: 4.3.0.Alpha1 > > Attachments: table.png > > -- This message was sent by Atlassian JIRA (v6.3.11#6341)

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3262) Deprecate Visual JSF Preview & Editing

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBDS-3262?page=com.atlassian.jira.plugin.... ] Denis Golovin commented on JBDS-3262: ------------------------------------- It should no be too difficult to remove it. It is basically standalone and noting depends on it except bundles with templates. Would be good if we do it for 9.0.0.Alpha1 and have chunk of binaries out of installer. > Deprecate Visual JSF Preview & Editing > -------------------------------------- > > Key: JBDS-3262 > URL: https://issues.jboss.org/browse/JBDS-3262 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Feature Request > Components: requirements, visual-page-editor-core > Reporter: Burr Sutter > Assignee: Konstantin Marmalyukov > Fix For: 8.1.0.GA, 9.0.0.Alpha1 > > > Note: JSF will remain supported as part of JBDS for EAP5, 6 , 7 and beyond as it is part of the Java EE specification. This deprecation notice specifically for the visual/source and preview editors. It does not currently work for 64-bit JVMs and a fair number of our end-users are moving to 64-bit JVMs. > This is the "deprecation notice" - actual removal of the visual/source and preview tabs is JBDS-3263 > http://screencast.com/t/zur1sCXmZ > http://screencast.com/t/wettTf6s6cU -- This message was sent by Atlassian JIRA (v6.3.11#6341)

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18914) Spring cleaning for /targetplatforms/ folder

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18914?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen commented on JBIDE-18914: --------------------------------------------- Same as Fred - i'm fine if we can outline/document how this wont break existing and past still installed releases. > Spring cleaning for /targetplatforms/ folder > -------------------------------------------- > > Key: JBIDE-18914 > URL: https://issues.jboss.org/browse/JBIDE-18914 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: target-platform, updatesite > Affects Versions: 4.2.1.Final > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 4.2.2.Final, 4.3.0.Alpha1 > > > Related to JBDS-3208, I'd like to purge all the unneeded old target platforms in [0]. > [0] http://download.jboss.org/jbosstools/targetplatforms/ > Specifically, this would involve moving and re-linking these into the equivalent folder under /static/ [1]: > {code} > [DIR] 3.62.0.Final-SNAPSHOT/ > [DIR] 3.72.0.Final-SNAPSHOT/ > [DIR] 4.20.5.Final-SNAPSHOT/ > [DIR] 4.20.6.Final-SNAPSHOT/ > [DIR] 4.21.3.Final-SNAPSHOT/ > [DIR] 4.21.4.Final-SNAPSHOT/ > [DIR] 4.22.0.Final-SNAPSHOT/ > [DIR] 4.22.1.Final-SNAPSHOT/ > [DIR] 4.22.2.Final-SNAPSHOT/ > {code} > Then we can purge all the 4.\{3?,4?}.\*.\*-SNAPSHOT folders for all the pre-Final builds; the rest should already be in /static/, but we can verify that and move any that are not already there. Really, we only need the handful of *.Final folders, and they should all be in /static/ [1]. > [1] http://download.jboss.org/jbosstools/static/targetplatforms/ > I believe we can also purge things like 4.40.0.Beta* from here [2]: > [2] http://download.jboss.org/jbosstools/static/targetplatforms/jbosstoolstar... > But for that one we need to verify that [~pleacu] doesn't still need them (ie., they're not used for an older JBTIS/JBDSIS Beta release build on Eclipse 4.4.0 / JBoss Tools 4.2.0. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

10 years, 10 months

1
0
0 / 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jbosstools-issues December 2014