October 2014 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-18355) Unexpected chars in freemarker editor

by Peter Palaga (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18355?page=com.atlassian.jira.plugi... ] Peter Palaga resolved JBIDE-18355. ---------------------------------- Release Notes Text: Gentlemen, I'd say that what we see here is Quick Diff, an old feature of the platform. It should disappear when you press {code}CTRL+SHIFT+Q{code} or if you disable it in the context menu of the left editor margin. Resolution: Rejected > Unexpected chars in freemarker editor > ------------------------------------- > > Key: JBIDE-18355 > URL: https://issues.jboss.org/browse/JBIDE-18355 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: freemarker > Affects Versions: 4.2.0.CR1 > Environment: JBDS 8.0.0.CR1b, L64 > Reporter: Jiri Peterka > Assignee: Peter Palaga > Fix For: 4.2.1.Final, 4.3.0.Alpha1 > > Attachments: freemarker-strange-char.ogv, html-template.ftl > > > Strange characters occurs when editing ftl file (check the screencast) -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18506) Usage plugin sometimes locks JBT/JBDS

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18506?page=com.atlassian.jira.plugi... ] Alexey Kazakov updated JBIDE-18506: ----------------------------------- Priority: Blocker (was: Major) > Usage plugin sometimes locks JBT/JBDS > ------------------------------------- > > Key: JBIDE-18506 > URL: https://issues.jboss.org/browse/JBIDE-18506 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: usage > Affects Versions: 4.2.0.CR1 > Reporter: Snjezana Peco > Assignee: Alexey Kazakov > Priority: Blocker > Fix For: 4.2.0.CR2 > > Attachments: usagestacktrace.out > > > JBossToolsUsageActivator initializes settings when starting and calls > AbstractEclipseEnvironment.initScreenSettings() > that uses the Display.syncExec method > which causes JBT/JBDS to freeze. The issue isn't always reproducible, but it often happens when starting JBDS/JBT in a new workspace. > While I was testing JBIDE-16379, I reproduced it each time when I started Eclipse 4.4.1/JBT 4.2.0.CR1 in a new workspace. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18506) Usage plugin sometimes locks JBT/JBDS

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18506?page=com.atlassian.jira.plugi... ] Alexey Kazakov commented on JBIDE-18506: ---------------------------------------- OK. It's clear now what causes this lock. When some plugin which register a usage event type in its startup method (it's a recommended way) it's invoking this syncExec() in Usage. If in the same time Eclipse UI invokes the usage tread (asyncExec()) from the earlyStartup method then we can get a deadlock in the synchronized JBossToolsUsageActivator.getDefault().getJBossToolsEclipseEnvironment() method. I still can't reproduce it but Snjezana's stacktrace is enough to see the problem. I modified the original Snjezana's PR to make sure the updated screen settings are available in all threads: https://github.com/jbosstools/jbosstools-base/pull/328 > Usage plugin sometimes locks JBT/JBDS > ------------------------------------- > > Key: JBIDE-18506 > URL: https://issues.jboss.org/browse/JBIDE-18506 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: usage > Affects Versions: 4.2.0.CR1 > Reporter: Snjezana Peco > Assignee: Alexey Kazakov > Fix For: 4.2.0.CR2 > > Attachments: usagestacktrace.out > > > JBossToolsUsageActivator initializes settings when starting and calls > AbstractEclipseEnvironment.initScreenSettings() > that uses the Display.syncExec method > which causes JBT/JBDS to freeze. The issue isn't always reproducible, but it often happens when starting JBDS/JBT in a new workspace. > While I was testing JBIDE-16379, I reproduced it each time when I started Eclipse 4.4.1/JBT 4.2.0.CR1 in a new workspace. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18506) Usage plugin sometimes locks JBT/JBDS

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18506?page=com.atlassian.jira.plugi... ] Alexey Kazakov updated JBIDE-18506: ----------------------------------- Git Pull Request: https://github.com/jbosstools/jbosstools-base/pull/328 (was: https://github.com/jbosstools/jbosstools-base/pull/326) > Usage plugin sometimes locks JBT/JBDS > ------------------------------------- > > Key: JBIDE-18506 > URL: https://issues.jboss.org/browse/JBIDE-18506 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: usage > Affects Versions: 4.2.0.CR1 > Reporter: Snjezana Peco > Assignee: Alexey Kazakov > Fix For: 4.2.0.CR2 > > Attachments: usagestacktrace.out > > > JBossToolsUsageActivator initializes settings when starting and calls > AbstractEclipseEnvironment.initScreenSettings() > that uses the Display.syncExec method > which causes JBT/JBDS to freeze. The issue isn't always reproducible, but it often happens when starting JBDS/JBT in a new workspace. > While I was testing JBIDE-16379, I reproduced it each time when I started Eclipse 4.4.1/JBT 4.2.0.CR1 in a new workspace. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18519) Cannot run Browsersim on RHEL6 with GTK3 - error instructs user to install package that is already installed

by Len DiMaggio (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18519?page=com.atlassian.jira.plugi... ] Len DiMaggio updated JBIDE-18519: --------------------------------- Fix Version/s: 4.2.0.Final Priority: Critical (was: Major) Assignee: Konstantin Marmalyukov > Cannot run Browsersim on RHEL6 with GTK3 - error instructs user to install package that is already installed > ------------------------------------------------------------------------------------------------------------ > > Key: JBIDE-18519 > URL: https://issues.jboss.org/browse/JBIDE-18519 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: browsersim > Affects Versions: 4.2.0.CR2 > Environment: RHEL 6.5 > Oracle 1.7, 1.8 > Reporter: Len DiMaggio > Assignee: Konstantin Marmalyukov > Priority: Critical > Fix For: 4.2.0.Final > > > In browsersim properties, GTK2 is the default - and if a RHEL6 user uses Java 1.7 JDK or Java 1.8 on RHEL6 - browsersim seems to function correctly. > But - is a user attempts to configure GTK3 (with either Oracle 1.7 or 1.8) - in the browsersim properties, browsersim fails to open with this error: > "To use BrowserSim please install webkitgtk 1.2.0 or higher or run BrowserSim with Oracle Java 7u7 and higher." > Also see <a href="http://tools.jboss.org/documentation/faq/browsersim.html">BrowserSim FAQ</a>. > Stack trace: > org.eclipse.swt.SWTError: To use BrowserSim please install webkitgtk 1.2.0 or higher or run BrowserSim with Oracle Java 7u7 and higher. > at org.jbos > The error is displayed even though this package is installed: > webkitgtk-1.2.6-5.el6.x86_64 -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18521) On RHEL7, Browsersim cannot use the SWT Browser (GTK) as the browser engine

by Len DiMaggio (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18521?page=com.atlassian.jira.plugi... ] Len DiMaggio updated JBIDE-18521: --------------------------------- Fix Version/s: 4.2.0.Final Priority: Critical (was: Major) Assignee: Konstantin Marmalyukov > On RHEL7, Browsersim cannot use the SWT Browser (GTK) as the browser engine > --------------------------------------------------------------------------- > > Key: JBIDE-18521 > URL: https://issues.jboss.org/browse/JBIDE-18521 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: browsersim > Affects Versions: 4.2.0.CR2 > Environment: RHEL7 > Java 1.7 > Java 1.8 > Reporter: Len DiMaggio > Assignee: Konstantin Marmalyukov > Priority: Critical > Fix For: 4.2.0.Final > > Attachments: screenshot_JBIDE-18521.png > > > Steps to reproduce: > * Configure Browsersim to use either Oracle 1.7 or 1.8 JDK on RHEL7 > * Open Browsersim > * Right-click to open the Browsersim context menu > * Observe the "please install webkitgtk to to use SWT.WebKit.engine" error > (See attached screenshot) > The webkitgtk package does not exist for RHEL7 - webkitgtk3 is installed in RHEL7 OOTB. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18518) If a RHEL user installs Oracle Java 1.7 through `yum install` and not from a direct download from Oracle, they cannot select JavaFx as the browser engine

by Len DiMaggio (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18518?page=com.atlassian.jira.plugi... ] Len DiMaggio updated JBIDE-18518: --------------------------------- Fix Version/s: 4.2.0.Final Priority: Critical (was: Major) > If a RHEL user installs Oracle Java 1.7 through `yum install` and not from a direct download from Oracle, they cannot select JavaFx as the browser engine > --------------------------------------------------------------------------------------------------------------------------------------------------------- > > Key: JBIDE-18518 > URL: https://issues.jboss.org/browse/JBIDE-18518 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: browsersim > Affects Versions: 4.2.0.CR2 > Reporter: Len DiMaggio > Assignee: Michelle Murray > Priority: Critical > Fix For: 4.2.0.Final > > > If a RHEL user installs Oracle Java 1.7 through `yum install` and not from a direct download from Oracle, they cannot select JavaFx as the browser engine > The issue is that if a RHEL user installs these packages: > java-1.7.0-oracle-1.7.0 > java-1.7.0-oracle-devel-1.7.0 > It may appear as though the full JDK has been installed as the "devel" package installs javac - however, the JavaFx libraries are not installed. As a result, the user cannot specify JavaFx as the browser engine in the BrowserSim preferences. (See attached screenshot.) -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18521) On RHEL7, Browsersim cannot use the SWT Browser (GTK) as the browser engine

by Len DiMaggio (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18521?page=com.atlassian.jira.plugi... ] Len DiMaggio updated JBIDE-18521: --------------------------------- Attachment: screenshot_JBIDE-18521.png > On RHEL7, Browsersim cannot use the SWT Browser (GTK) as the browser engine > --------------------------------------------------------------------------- > > Key: JBIDE-18521 > URL: https://issues.jboss.org/browse/JBIDE-18521 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: browsersim > Affects Versions: 4.2.0.CR2 > Environment: RHEL7 > Java 1.7 > Java 1.8 > Reporter: Len DiMaggio > Attachments: screenshot_JBIDE-18521.png > > > Steps to reproduce: > * Configure Browsersim to use either Oracle 1.7 or 1.8 JDK on RHEL7 > * Open Browsersim > * Right-click to open the Browsersim context menu > * Observe the "please install webkitgtk to to use SWT.WebKit.engine" error > (See attached screenshot) > The webkitgtk package does not exist for RHEL7 - webkitgtk3 is installed in RHEL7 OOTB. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18521) On RHEL7, Browsersim cannot use the SWT Browser (GTK) as the browser engine

by Len DiMaggio (JIRA)

Len DiMaggio created JBIDE-18521: ------------------------------------ Summary: On RHEL7, Browsersim cannot use the SWT Browser (GTK) as the browser engine Key: JBIDE-18521 URL: https://issues.jboss.org/browse/JBIDE-18521 Project: Tools (JBoss Tools) Issue Type: Bug Components: browsersim Affects Versions: 4.2.0.CR2 Environment: RHEL7 Java 1.7 Java 1.8 Reporter: Len DiMaggio Steps to reproduce: * Configure Browsersim to use either Oracle 1.7 or 1.8 JDK on RHEL7 * Open Browsersim * Right-click to open the Browsersim context menu * Observe the "please install webkitgtk to to use SWT.WebKit.engine" error (See attached screenshot) The webkitgtk package does not exist for RHEL7 - webkitgtk3 is installed in RHEL7 OOTB. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-17943) make it easy to add ionic libraries to cordova project

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBIDE-17943?page=com.atlassian.jira.plugi... ] Denis Golovin edited comment on JBIDE-17943 at 10/6/14 3:48 PM: ---------------------------------------------------------------- Should we do it as separate module or as part of aerogear-hybrid? As aerogear-hybrid/bower for example. was (Author: dgolovin): Should we do it as separate module or as part of aerogear-hybrid? As aerogear-hybrid/bower for example? > make it easy to add ionic libraries to cordova project > ------------------------------------------------------ > > Key: JBIDE-17943 > URL: https://issues.jboss.org/browse/JBIDE-17943 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: aerogear-hybrid > Reporter: Max Rydahl Andersen > Assignee: Gorkem Ercan > Fix For: 4.3.x > > > today enabling ionic on a cordova project requires manual setup - can we make it easier ? -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 6 months

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jbosstools-issues October 2014