April 2015 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-19704) Visual part of Visual/Source tab is empty for HTML page when JSF support enabled

by Ilya Buziuk (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19704?page=com.atlassian.jira.plugi... ] Ilya Buziuk commented on JBIDE-19704: ------------------------------------- However, that simple html should be parsed without any problems even with obsolete xulrunner IMO > Visual part of Visual/Source tab is empty for HTML page when JSF support enabled > -------------------------------------------------------------------------------- > > Key: JBIDE-19704 > URL: https://issues.jboss.org/browse/JBIDE-19704 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: visual-page-editor-core > Affects Versions: 4.3.0.Alpha2 > Environment: Fedora 19 64bit, JBDS 9.0.0.Alpha2-v20150421-1151-B25, Oracle JDK 1.7 > Reporter: Vlado Pakan > Assignee: Ilya Buziuk > > 1. Set Visual Editor to use JSF support > 2. Create simple HTML page like this and open it in VPE editor > {code:html} > <!DOCTYPE html> > <html> > <body> > <h1>test heading</h1> > </body> > </html> > {code} > ERROR: Visual part of Visual/Source tab of VPE is empty. > Visual tab of VPE renders page properly. > When HTML support is enabled it works fine. > I'm not sure if this is issue or expected behavior so if it's not an issue just mark it as won't fix please. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19704) Visual part of Visual/Source tab is empty for HTML page when JSF support enabled

by Ilya Buziuk (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19704?page=com.atlassian.jira.plugi... ] Ilya Buziuk commented on JBIDE-19704: ------------------------------------- I believe this is expected behavior - http://tools.jboss.org/documentation/faq/visualeditor.html#platform-speci... > Visual part of Visual/Source tab is empty for HTML page when JSF support enabled > -------------------------------------------------------------------------------- > > Key: JBIDE-19704 > URL: https://issues.jboss.org/browse/JBIDE-19704 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: visual-page-editor-core > Affects Versions: 4.3.0.Alpha2 > Environment: Fedora 19 64bit, JBDS 9.0.0.Alpha2-v20150421-1151-B25, Oracle JDK 1.7 > Reporter: Vlado Pakan > Assignee: Ilya Buziuk > > 1. Set Visual Editor to use JSF support > 2. Create simple HTML page like this and open it in VPE editor > {code:html} > <!DOCTYPE html> > <html> > <body> > <h1>test heading</h1> > </body> > </html> > {code} > ERROR: Visual part of Visual/Source tab of VPE is empty. > Visual tab of VPE renders page properly. > When HTML support is enabled it works fine. > I'm not sure if this is issue or expected behavior so if it's not an issue just mark it as won't fix please. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19342) Update code to cope with generics added to org.eclipse.core.runtime package API

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19342?page=com.atlassian.jira.plugi... ] Denis Golovin commented on JBIDE-19342: --------------------------------------- freemarker is not affected. > Update code to cope with generics added to org.eclipse.core.runtime package API > -------------------------------------------------------------------------------- > > Key: JBIDE-19342 > URL: https://issues.jboss.org/browse/JBIDE-19342 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: aerogear-hybrid, archives, batch, bean-validation, birt, browsersim, cdi, cdi-extensions, central, common/jst/core, cordovasim, forge, hibernate, integration-platform, jmx, jsf, jsp/jsf/xml/html source editing > Affects Versions: 4.3.0.Alpha2 > Reporter: Fred Bricon > Priority: Minor > Fix For: 4.3.x > > > We need to detect and address any part of our code affected by generics added to the org.eclipse.core.runtime package API. > From https://dev.eclipse.org/mhonarc/lists/cross-project-issues-dev/msg11590.html : > {quote} > See https://bugs.eclipse.org/bugs/show_bug.cgi?id=442021 > Markus Keller wrote up an nice summary of what consumers should do to fix any warnings that may be caused by this change at https://bugs.eclipse.org/bugs/show_bug.cgi?id=442021#c25 > Here is a copy of the recommendations if you are going to compile against the latest version of org.eclipse.equinox.common: > 1. In MANIFEST.MF, update your Require-Bundle: org.eclipse.core.runtime;bundle-version="[3.11.0,4.0.0)", or org.eclipse.equinox.common;bundle-version="[3.7.0,4.0.0)", or update your Import-Package: org.eclipse.core.runtime; version="[3.5,4.0)" > 2. If your bundle re-exports one of these bundles, then you also have to make sure the minor version is incremented. > 3. Remove unnecessary casts (Clean Up, or Problems view > Quick Fix > Select All) > 4. Update implementations of IAdaptable#getAdapter(Class<T>), unless you override another implementation of that method that still uses the old signature. > Typical change: > Old: > {code} > public Object getAdapter(Class adapter) { > if (ICompilationUnit.class.equals(adapter)) > return getCompilationUnit(); > return null; > } > {code} > New: > {code} > public <T> T getAdapter(Class<T> adapter) { > if (ICompilationUnit.class.equals(adapter)) > return adapter.cast(getCompilationUnit()); > return null; > } > {code} > 5. Update implementations of IAdapterFactory > Hint for 4. & 5.: > - Open Type Hierarchy on IAdaptable, etc. > - In the view menu, select a working set that contains your projects > - In the methods list of the Type Hierarchy view, select the methods, and then click the first toolbar button (Lock View and Show Members in Hierarchy) > {quote} -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19342) Update code to cope with generics added to org.eclipse.core.runtime package API

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19342?page=com.atlassian.jira.plugi... ] Denis Golovin updated JBIDE-19342: ---------------------------------- Component/s: (was: freemarker) > Update code to cope with generics added to org.eclipse.core.runtime package API > -------------------------------------------------------------------------------- > > Key: JBIDE-19342 > URL: https://issues.jboss.org/browse/JBIDE-19342 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: aerogear-hybrid, archives, batch, bean-validation, birt, browsersim, cdi, cdi-extensions, central, common/jst/core, cordovasim, forge, hibernate, integration-platform, jmx, jsf, jsp/jsf/xml/html source editing > Affects Versions: 4.3.0.Alpha2 > Reporter: Fred Bricon > Priority: Minor > Fix For: 4.3.x > > > We need to detect and address any part of our code affected by generics added to the org.eclipse.core.runtime package API. > From https://dev.eclipse.org/mhonarc/lists/cross-project-issues-dev/msg11590.html : > {quote} > See https://bugs.eclipse.org/bugs/show_bug.cgi?id=442021 > Markus Keller wrote up an nice summary of what consumers should do to fix any warnings that may be caused by this change at https://bugs.eclipse.org/bugs/show_bug.cgi?id=442021#c25 > Here is a copy of the recommendations if you are going to compile against the latest version of org.eclipse.equinox.common: > 1. In MANIFEST.MF, update your Require-Bundle: org.eclipse.core.runtime;bundle-version="[3.11.0,4.0.0)", or org.eclipse.equinox.common;bundle-version="[3.7.0,4.0.0)", or update your Import-Package: org.eclipse.core.runtime; version="[3.5,4.0)" > 2. If your bundle re-exports one of these bundles, then you also have to make sure the minor version is incremented. > 3. Remove unnecessary casts (Clean Up, or Problems view > Quick Fix > Select All) > 4. Update implementations of IAdaptable#getAdapter(Class<T>), unless you override another implementation of that method that still uses the old signature. > Typical change: > Old: > {code} > public Object getAdapter(Class adapter) { > if (ICompilationUnit.class.equals(adapter)) > return getCompilationUnit(); > return null; > } > {code} > New: > {code} > public <T> T getAdapter(Class<T> adapter) { > if (ICompilationUnit.class.equals(adapter)) > return adapter.cast(getCompilationUnit()); > return null; > } > {code} > 5. Update implementations of IAdapterFactory > Hint for 4. & 5.: > - Open Type Hierarchy on IAdaptable, etc. > - In the view menu, select a working set that contains your projects > - In the methods list of the Type Hierarchy view, select the methods, and then click the first toolbar button (Lock View and Show Members in Hierarchy) > {quote} -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-8526) Freemarker content assist doesn't work when inside a tag or tag attribute

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBIDE-8526?page=com.atlassian.jira.plugin... ] Denis Golovin updated JBIDE-8526: --------------------------------- Fix Version/s: 4.3.0.Beta1 (was: 4.2.x) (was: 4.3.x) > Freemarker content assist doesn't work when inside a tag or tag attribute > ------------------------------------------------------------------------- > > Key: JBIDE-8526 > URL: https://issues.jboss.org/browse/JBIDE-8526 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: freemarker > Affects Versions: 3.3.x > Environment: Windows XP, > Reporter: Ehrann Mehdan > Assignee: Peter Palaga > Fix For: 4.3.0.Beta1 > > > In Freemarker 1.1.0.v20110303-1225-H55-Alpha1 > Eclipse platform version: 3.6.2.r362_v20110210-9gF78Gs1FrIGnHDHWkEcopoN8AmxeZflGDGKQi > Build id: M20110210-1200 > This code will not trigger content assist when pressing ctrl+space with a context named data that has property "someValue" > <tag attribute="${data.someValue}">... > This code will (removed opening tag bracket) > tag attribute="${data.someValue}">... -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-8526) Freemarker content assist doesn't work when inside a tag or tag attribute

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBIDE-8526?page=com.atlassian.jira.plugin... ] Denis Golovin updated JBIDE-8526: --------------------------------- Sprint: Sprint #3 May 2015 > Freemarker content assist doesn't work when inside a tag or tag attribute > ------------------------------------------------------------------------- > > Key: JBIDE-8526 > URL: https://issues.jboss.org/browse/JBIDE-8526 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: freemarker > Affects Versions: 3.3.x > Environment: Windows XP, > Reporter: Ehrann Mehdan > Assignee: Peter Palaga > Fix For: 4.3.0.Beta1 > > > In Freemarker 1.1.0.v20110303-1225-H55-Alpha1 > Eclipse platform version: 3.6.2.r362_v20110210-9gF78Gs1FrIGnHDHWkEcopoN8AmxeZflGDGKQi > Build id: M20110210-1200 > This code will not trigger content assist when pressing ctrl+space with a context named data that has property "someValue" > <tag attribute="${data.someValue}">... > This code will (removed opening tag bracket) > tag attribute="${data.someValue}">... -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18036) Decouple FTL target language syntax coloring

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18036?page=com.atlassian.jira.plugi... ] Denis Golovin updated JBIDE-18036: ---------------------------------- Sprint: Sprint #3 May 2015 > Decouple FTL target language syntax coloring > -------------------------------------------- > > Key: JBIDE-18036 > URL: https://issues.jboss.org/browse/JBIDE-18036 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: freemarker > Reporter: Peter Palaga > Assignee: Max Rydahl Andersen > Fix For: 4.3.0.Beta1 > > Attachments: coloring-issues.png > > > This issue covers the requirement formulated in point (1) of my earlier comment in [JBIDE-11287|https://issues.jboss.org/browse/JBIDE-11287?focusedCommentId=...]. > The present Freemarker plugin has a hard-coded XML/HTML syntax coloring. Although XML/HTML may well be the most common target language of an FTL template, it is clearly not the only possible target language. One can target virtually any language or even plaintext, where {{<}} and {{<!--}} may have completely different meanings or no meanigs at all. Hardcoding XML highlighting for every file opened by the FTL editor is thus simply incorrect. > Let's define the present task as follows: > (1) Decouple the syntax coloring of the target language of a FTL template by introducing an interface (call it {{TargetLanguageSupport}}) that will provide the general functionality needed for coloring of target languages. > (2) At least two implementations of {{TargetLanguageSupport}} should be added: > (2.1) XML/HTML and > (2.2) plain text. > (3) Some kind of target-language detection should be added, e.g. based on file extensions, making XML/HTML syntax coloring active for files ending with {{\*.xml.ftl}}, {{\*.xhtml.ftl}}, {{\*.html.ftl}} and {{\*.htm.ftl}}. > (3.1) There should be a workspace-wide preference that will say for which file extensions will e.g. XML/HTML syntax coloring be active. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18245) Freemarker syntax highlight issues

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18245?page=com.atlassian.jira.plugi... ] Denis Golovin updated JBIDE-18245: ---------------------------------- Sprint: Sprint #3 May 2015 > Freemarker syntax highlight issues > ---------------------------------- > > Key: JBIDE-18245 > URL: https://issues.jboss.org/browse/JBIDE-18245 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: freemarker > Affects Versions: 4.2.0.CR1 > Environment: JBDS 8.0.0.CR1 > Reporter: Jiri Peterka > Fix For: 4.3.0.Beta1 > > Attachments: syntax-highlight-issue.png > > > Create ftl file and paste: > {code} > <html> > <head> > <title>Welcome!</title> > </head> > <body> > <h1>Welcome ${user}!</h1> > <p>Our latest product: > <a href="${latestProduct.url}">${latestProduct.name}</a> > <#assign x = 1 />. > <#assign y = 1 /> > <#assign z = 1 /> > </body> > </html> > {code} > Syntax highlighting works very strange, see screenshot and make some atttempts, you will see it for your own. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18036) Decouple FTL target language syntax coloring

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18036?page=com.atlassian.jira.plugi... ] Denis Golovin updated JBIDE-18036: ---------------------------------- Fix Version/s: 4.3.0.Beta1 (was: 4.3.x) > Decouple FTL target language syntax coloring > -------------------------------------------- > > Key: JBIDE-18036 > URL: https://issues.jboss.org/browse/JBIDE-18036 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: freemarker > Reporter: Peter Palaga > Assignee: Max Rydahl Andersen > Fix For: 4.3.0.Beta1 > > Attachments: coloring-issues.png > > > This issue covers the requirement formulated in point (1) of my earlier comment in [JBIDE-11287|https://issues.jboss.org/browse/JBIDE-11287?focusedCommentId=...]. > The present Freemarker plugin has a hard-coded XML/HTML syntax coloring. Although XML/HTML may well be the most common target language of an FTL template, it is clearly not the only possible target language. One can target virtually any language or even plaintext, where {{<}} and {{<!--}} may have completely different meanings or no meanigs at all. Hardcoding XML highlighting for every file opened by the FTL editor is thus simply incorrect. > Let's define the present task as follows: > (1) Decouple the syntax coloring of the target language of a FTL template by introducing an interface (call it {{TargetLanguageSupport}}) that will provide the general functionality needed for coloring of target languages. > (2) At least two implementations of {{TargetLanguageSupport}} should be added: > (2.1) XML/HTML and > (2.2) plain text. > (3) Some kind of target-language detection should be added, e.g. based on file extensions, making XML/HTML syntax coloring active for files ending with {{\*.xml.ftl}}, {{\*.xhtml.ftl}}, {{\*.html.ftl}} and {{\*.htm.ftl}}. > (3.1) There should be a workspace-wide preference that will say for which file extensions will e.g. XML/HTML syntax coloring be active. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18243) Freemarker syntax highlight requires file reopening

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18243?page=com.atlassian.jira.plugi... ] Denis Golovin updated JBIDE-18243: ---------------------------------- Sprint: Sprint #3 May 2015 > Freemarker syntax highlight requires file reopening > --------------------------------------------------- > > Key: JBIDE-18243 > URL: https://issues.jboss.org/browse/JBIDE-18243 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: freemarker > Affects Versions: 4.2.0.CR1 > Environment: JBDS 8.0.0.CR1 > Reporter: Jiri Peterka > Fix For: 4.3.0.Beta1 > > > When pasting some code into ftl file, syntax highlight is not activated until file is saved closed and reopened. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 11 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 April 2015