July 2016 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-22656) Related tag background becomes misplaced when typing

by Ondrej Dockal (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22656?page=com.atlassian.jira.plugi... ] Ondrej Dockal closed JBIDE-22656. --------------------------------- Verified on devstudio: Version: 10.0.1.AM2 Build id: AM2-v20160720-1632-B5674 closing... > Related tag background becomes misplaced when typing > ---------------------------------------------------- > > Key: JBIDE-22656 > URL: https://issues.jboss.org/browse/JBIDE-22656 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: freemarker > Reporter: Daniel Dekany > Assignee: Alexey Kazakov > Fix For: 4.4.1.AM2 > > > When you put the cursor inside an FTL tag, like {{<#if ...>}}, the background color of related tags, like {{<#else>}} and {{</#if>}}, is changed. The problem is that if now you start typing into a such background-colored tag, the offsets of the colored sections after it will become outdated, and so they start to drift left from under the tag. This is because the up to date offsets only become available after the reconciling thread has finished, but the background coloring logic is called directly in the keydown handler. I'm not familiar with plugin development, but I suspect this is architecturally wrong. Perhaps the reconciler should send some kind of event when it's done, and if the editor content is still in the state for which the reconciling was ran, only then should the old background coloring be removed and the new one is added. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20491) "incompatibleImprovements" setting should be set

by Ondrej Dockal (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20491?page=com.atlassian.jira.plugi... ] Ondrej Dockal closed JBIDE-20491. --------------------------------- Verified on devstudio: Version: 10.0.1.AM2 Build id: AM2-v20160720-1632-B5674 Closing... > "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.AM2 > > > 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, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22574) Custom color of directives in eclipse plugin now working

by Ondrej Dockal (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22574?page=com.atlassian.jira.plugi... ] Ondrej Dockal closed JBIDE-22574. --------------------------------- Verified on devstudio: Version: 10.0.1.AM2 Build id: AM2-v20160720-1632-B5674 Closing. > Custom color of directives in eclipse plugin now working > -------------------------------------------------------- > > Key: JBIDE-22574 > URL: https://issues.jboss.org/browse/JBIDE-22574 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: freemarker > Environment: Eclipse Mars.2, FreeMarker IDE 1.5.100.Final-v20160603-0259-B419 > Reporter: Marcelo Marcelo > Assignee: Alexey Kazakov > Priority: Minor > Fix For: 4.4.1.AM2 > > Attachments: freemarker-ide.png > > > When using Freemarker IDE on eclipse, I would like to customize editor's colors, since I am using a dark theme and the editor is not readable with the default colors. However, changing the color for directives does not work as expected. It only change colors of closing tags. > Example: <#list> remains dark blue (default color) but </#list> changes to the new color. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3960) Rename platform installer artifacts to start with "devsuite" instead of "development-suite"

by Jan Richter (JIRA)

[ https://issues.jboss.org/browse/JBDS-3960?page=com.atlassian.jira.plugin.... ] Jan Richter resolved JBDS-3960. ------------------------------- Resolution: Done > Rename platform installer artifacts to start with "devsuite" instead of "development-suite" > ------------------------------------------------------------------------------------------- > > Key: JBDS-3960 > URL: https://issues.jboss.org/browse/JBDS-3960 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Bug > Components: platform-installer > Affects Versions: 10.0.0.GA > Reporter: Nick Boldt > Assignee: Jan Richter > Fix For: 10.1.0.AM2 > > > Max said: "I don't see dev studio in that download dialog - I see "Development-suite" ...which btw. is wrong, it should be devsuite here. Have you opened bug for this already ?" > So, I've opened a bug for this, already. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22636) Associate ftlh and fltx file extensions with the FreeMarker editor

by Ondrej Dockal (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22636?page=com.atlassian.jira.plugi... ] Ondrej Dockal closed JBIDE-22636. --------------------------------- Verified on devstudio: Version: 10.0.1.AM2 Build id: AM2-v20160720-1632-B5674 Closing. > Associate ftlh and fltx file extensions with the FreeMarker editor > ------------------------------------------------------------------ > > Key: JBIDE-22636 > URL: https://issues.jboss.org/browse/JBIDE-22636 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: freemarker > Reporter: Daniel Dekany > Assignee: Alexey Kazakov > Fix For: 4.4.1.AM2 > > > Currently only {{ftl}} is associated with it. 2.3.24 added support for using {{ftlh}} and {{ftlx}} extensions to indicate that the output will be HTML or XML respectively, and to enable auto-escaping for them. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3978) Getting started page shows guide for Devstudio 9.x

by Jan Richter (JIRA)

[ https://issues.jboss.org/browse/JBDS-3978?page=com.atlassian.jira.plugin.... ] Jan Richter updated JBDS-3978: ------------------------------ Priority: Minor (was: Major) > Getting started page shows guide for Devstudio 9.x > -------------------------------------------------- > > Key: JBDS-3978 > URL: https://issues.jboss.org/browse/JBDS-3978 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Bug > Components: platform-installer > Affects Versions: 10.1.0.AM2 > Reporter: Jan Richter > Priority: Minor > > The getting started link in devsuite leads to http://developers.redhat.com/devstudio-preview > The very fact that it is named > {noformat}Using JBoss Developer Studio 9.x's Container Development Kit Tooling {noformat} > looks suspicious. There might not be much difference to the current workflow, but it definitely is worth updating. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3978) Getting started page shows guide for Devstudio 9.x

by Jan Richter (JIRA)

Jan Richter created JBDS-3978: --------------------------------- Summary: Getting started page shows guide for Devstudio 9.x Key: JBDS-3978 URL: https://issues.jboss.org/browse/JBDS-3978 Project: Red Hat JBoss Developer Studio (devstudio) Issue Type: Bug Components: platform-installer Affects Versions: 10.1.0.AM2 Reporter: Jan Richter The getting started link in devsuite leads to http://developers.redhat.com/devstudio-preview The very fact that it is named {noformat}Using JBoss Developer Studio 9.x's Container Development Kit Tooling {noformat} looks suspicious. There might not be much difference to the current workflow, but it definitely is worth updating. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20180) > (and <) in expressions confuses the editor

by Ondrej Dockal (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20180?page=com.atlassian.jira.plugi... ] Ondrej Dockal closed JBIDE-20180. --------------------------------- Verified on devstudio: Version: 10.0.1.AM2 Build id: AM2-v20160720-1632-B5674 Build date: 20160720-1632 Closing. > > (and <) in expressions confuses the editor > -------------------------------------------- > > Key: JBIDE-20180 > URL: https://issues.jboss.org/browse/JBIDE-20180 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: freemarker > Affects Versions: 4.2.0.Beta2 > Reporter: Daniel Dekany > Assignee: Alexey Kazakov > Fix For: 4.4.1.AM2 > > > In the text editor, {{>}} closes the tag even if it's inside a string literal, or inside parentheses. Try: > * {{<#assign x = 'x>y'>}}: Notice how syntax coloring switches to black > * {{<#if (x > 0)></#if>}}: This one also breaks the outline view; no macros after this will appear in it. > More puzzling cases with {{<}}; these break outline view too: > * {{<#if x == '<'></#if><#macro m></#macro>}} > * {{<#if x < 1></#if><#macro m></#macro>}} > Note: There's an ongoing overhaul of the tokenizers (see in comments), which fixes these, and some more, like the handling of multi-line statements, of {{'}}-quoted stings, of FTL raw strings, of 2.3.22 identifier escapings, gives more detailed syntax highlighting, etc. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3977) Devstudio version string needs update

by Jan Richter (JIRA)

Jan Richter created JBDS-3977: --------------------------------- Summary: Devstudio version string needs update Key: JBDS-3977 URL: https://issues.jboss.org/browse/JBDS-3977 Project: Red Hat JBoss Developer Studio (devstudio) Issue Type: Bug Components: platform-installer Affects Versions: 10.1.0.AM2 Reporter: Jan Richter As per requirements.json, the static version field for devstudio is still set to 10.0.1.Alpha1. We need to update this and preferably find some way to do this effortlessly any time the version changes. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22673) Need better duplicate IU detection when validating target platforms

by Mickael Istria (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22673?page=com.atlassian.jira.plugi... ] Mickael Istria commented on JBIDE-22673: ---------------------------------------- Seems like we cannot easily mix 2 versions of Tycho. We have to wait for Tycho 0.26 to be released before adopting the new verification options. > Need better duplicate IU detection when validating target platforms > ------------------------------------------------------------------- > > Key: JBIDE-22673 > URL: https://issues.jboss.org/browse/JBIDE-22673 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: build, target-platform, upstream > Affects Versions: 4.4.0.Final > Reporter: Nick Boldt > Assignee: Mickael Istria > Fix For: 4.4.x > > Attachments: verify-log.txt > > > As discussed in JBIDE-22633, we have no way of knowing when the target platform SHOULD contain duplicate IUs, and when it should not. > {quote}Problem is there's no way to identify easily which dupes are OK and which are not. I suppose I could crack open all the jars and see which are singletons...? > Or add a whitelist?{quote} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 8 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 July 2016