[JBoss JIRA] (JBIDE-22616) Red Hat Central crashes when SWT_WEBKIT2=1
by Alexey Kazakov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-22616?page=com.atlassian.jira.plugi... ]
Alexey Kazakov updated JBIDE-22616:
-----------------------------------
Description:
This is a follow-up on JBDS-3953
SWT_WEBKIT2=1 works around the problem of crashing Eclipse/devstudio on Fedora
But this prevent Central view from loading browser:
!https://issues.jboss.org/secure/attachment/12406478/12406478_Selection_003.png!
was:
This is a follow-up of JBDS-3953
SWT_WEBKIT2=1 works around the problem of crashing Eclipse/devstudio on Fedora
But this prevent Central view from loading browser:
!https://issues.jboss.org/secure/attachment/12406478/12406478_Selection_003.png!
> Red Hat Central crashes when SWT_WEBKIT2=1
> ------------------------------------------
>
> Key: JBIDE-22616
> URL: https://issues.jboss.org/browse/JBIDE-22616
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: central
> Affects Versions: 4.4.0.Final
> Reporter: Alexey Kazakov
>
> This is a follow-up on JBDS-3953
> SWT_WEBKIT2=1 works around the problem of crashing Eclipse/devstudio on Fedora
> But this prevent Central view from loading browser:
> !https://issues.jboss.org/secure/attachment/12406478/12406478_Selection_003.png!
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 9 months
[JBoss JIRA] (JBIDE-22616) Red Hat Central crashes when SWT_WEBKIT2=1
by Alexey Kazakov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-22616?page=com.atlassian.jira.plugi... ]
Alexey Kazakov updated JBIDE-22616:
-----------------------------------
Description:
This is a follow-up of JBDS-3953
SWT_WEBKIT2=1 works around the problem of crashing Eclipse/devstudio on Fedora
But this prevent Central view from loading browser:
!https://issues.jboss.org/secure/attachment/12406478/12406478_Selection_003.png!
> Red Hat Central crashes when SWT_WEBKIT2=1
> ------------------------------------------
>
> Key: JBIDE-22616
> URL: https://issues.jboss.org/browse/JBIDE-22616
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: central
> Affects Versions: 4.4.0.Final
> Reporter: Alexey Kazakov
>
> This is a follow-up of JBDS-3953
> SWT_WEBKIT2=1 works around the problem of crashing Eclipse/devstudio on Fedora
> But this prevent Central view from loading browser:
> !https://issues.jboss.org/secure/attachment/12406478/12406478_Selection_003.png!
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 9 months
[JBoss JIRA] (JBIDE-20491) "incompatibleImprovements" setting should be set
by Denis Golovin (JIRA)
[ https://issues.jboss.org/browse/JBIDE-20491?page=com.atlassian.jira.plugi... ]
Denis Golovin updated JBIDE-20491:
----------------------------------
Fix Version/s: 4.4.1.S116
(was: 4.4.0.Alpha1)
> "incompatibleImprovements" setting should be set
> ------------------------------------------------
>
> Key: JBIDE-20491
> URL: https://issues.jboss.org/browse/JBIDE-20491
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: freemarker
> Reporter: Daniel Dekany
> Assignee: Denis Golovin
> Fix For: 4.4.1.S116
>
>
> Where the {{freemarker.template.Configuration}} is created, the {{incompatibleImprovements}} setting shouldn't be left on its default, 2.3.0. It should be set to {{Configuration.getVersion()}} (like {{new Configuration(Configuration.getVersion())}}, or with {{config.setIncompatibleImprovements(Configuration.getVersion())}}).
> Why: The plugin doesn't execute the templates, just parses them. As of 2.3.24, all the "incompatible" fixes that affect the parser (not the execution) just makes it stricter by eliminating legacy parser glitches that let through things that are pretty much always just user oversights. Also when 2.3.24 is out, the new {{ftlh}} and {{ftlx}} file extensions, which affect parsing, will only have effect with {{incompatibleImprovements}} 2.3.24.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 9 months
[JBoss JIRA] (JBTIS-790) Fuse: Extend Server Requirement
by Andrej Podhradsky (JIRA)
[ https://issues.jboss.org/browse/JBTIS-790?page=com.atlassian.jira.plugin.... ]
Andrej Podhradsky closed JBTIS-790.
-----------------------------------
I've slightly change the xsd ('camel-version' -> 'camelVersion') so that it follows our convention ;-)
pushed to master
> Fuse: Extend Server Requirement
> -------------------------------
>
> Key: JBTIS-790
> URL: https://issues.jboss.org/browse/JBTIS-790
> Project: JBoss Tools Integration Stack
> Issue Type: Sub-task
> Components: Fuse IDE, QE
> Affects Versions: 4.3.0.Final
> Reporter: Tomáš Sedmík
> Assignee: Tomáš Sedmík
> Priority: Blocker
> Fix For: 4.3.1.Final
>
>
> We need to know a version of Camel inside JBoss Fuse runtime -> add new element for Camel Version
> + also add support for JBoss Fuse 6.3 server adapter
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 9 months
[JBoss JIRA] (JBIDE-22612) Explorer: OpenShift connections are missing from the explorer on startup
by Viacheslav Kabanovich (JIRA)
[ https://issues.jboss.org/browse/JBIDE-22612?page=com.atlassian.jira.plugi... ]
Viacheslav Kabanovich commented on JBIDE-22612:
-----------------------------------------------
[~adietish], global New menu has option for creating OpenShift application. It can be accessed before view is opened. Then it also trigger loading OpenShift plugins. If not now, in the future more features may be needed that activate OpenShift, from menues, toolbars, etc.
> Explorer: OpenShift connections are missing from the explorer on startup
> ------------------------------------------------------------------------
>
> Key: JBIDE-22612
> URL: https://issues.jboss.org/browse/JBIDE-22612
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.4.1.Alpha1-devex116
> Reporter: Fred Bricon
> Assignee: Andre Dietisheim
> Labels: explorer, openshift_v2, openshift_v3
> Fix For: 4.4.1.Alpha1-devex116
>
>
> After applying the fix for JBIDE-21828, it appears that, on workspace restart, the OpenShift 3 connections are missing from the OpenShift Explorer.
> This is caused by the OpenShift 3 core plugin not being started when the OpenShiftExplorerContentProvider is called. As a consequence, no connections are loaded.
> Before JBIDE-21828, [getExplorerElements|https://github.com/jbosstools/jbosstools-openshift/co...] would return all the OpenShift3 connections. With the new code, the UI Model is expected to be already loaded
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 9 months