September 2014 - jbosstools-issues

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

by Jiri Peterka (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18036?page=com.atlassian.jira.plugi... ] Jiri Peterka commented on JBIDE-18036: -------------------------------------- No Max, this one is just about wrong syntax highlight around comment. Not critical for GA IMO. I'm quite fine when it's fixed in 4.2.1. > 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: Peter Palaga > Fix For: 4.2.1.Final > > 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.1#6329)

11 years

1
0
0 / 0

[JBoss JIRA] (JBDS-2919) Initial/basic support for Java EE 7 should be present. Should not "blow up". Allow to create Java, compile and deploy EE 7 projects on WildFly 8

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBDS-2919?page=com.atlassian.jira.plugin.... ] Max Rydahl Andersen resolved JBDS-2919. --------------------------------------- Resolution: Done all dev work on tools is done - remaining is xsd issues in wildlfy or bugs ine clipse. open separate issues for follow up. > Initial/basic support for Java EE 7 should be present. Should not "blow up". Allow to create Java, compile and deploy EE 7 projects on WildFly 8 > ------------------------------------------------------------------------------------------------------------------------------------------------ > > Key: JBDS-2919 > URL: https://issues.jboss.org/browse/JBDS-2919 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Epic > Components: server > Reporter: Max Rydahl Andersen > Assignee: Xavier Coulon > Fix For: 8.0.0.CR2 > > > Moving to 8.0.0.CR1 (as agreed with [~maxandersen]) -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years

1
0
0 / 0

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

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18355?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen updated JBIDE-18355: ---------------------------------------- Fix Version/s: 4.2.1.Final 4.3.0.Alpha1 (was: 4.2.0.CR2) > 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 > > > Strange characters occurs when editing ftl file (check the screencast) -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years

1
0
0 / 0

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

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18036?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen commented on JBIDE-18036: --------------------------------------------- @jpeterka any updates? > 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: Peter Palaga > Fix For: 4.2.1.Final > > 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.1#6329)

11 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-15474) "Further Configuration" for JAX-RS Facet should be optional

by Xavier Coulon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15474?page=com.atlassian.jira.plugi... ] Xavier Coulon resolved JBIDE-15474. ----------------------------------- Resolution: Done Marking this issue as resolved since the patch was committed (see comment from Sept. 11th) and Luna SR1 was released. > "Further Configuration" for JAX-RS Facet should be optional > ----------------------------------------------------------- > > Key: JBIDE-15474 > URL: https://issues.jboss.org/browse/JBIDE-15474 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: upstream, webservices > Affects Versions: 4.1.0.Final > Reporter: Xavier Coulon > Assignee: Xavier Coulon > Fix For: 4.2.0.CR2 > > > - library configuration should be optional, since users may work with Maven > - web.xml configuration (servlet mapping) should be optional as well, since it has not been required since JavaEE6. > Opened https://bugs.eclipse.org/bugs/show_bug.cgi?id=431081 to track this request at the Eclipse WTP level. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-18117) Unable to remove the JAX-RS facet on a Dynamic Web Project version 3.1

by Xavier Coulon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18117?page=com.atlassian.jira.plugi... ] Xavier Coulon edited comment on JBIDE-18117 at 9/30/14 9:33 AM: ---------------------------------------------------------------- Marking this issue as resolved since the patch was committed (see comment from Sept. 2nd) and Luna SR1 was released. was (Author: xcoulon): Marking this issue as resolved since the patch was committed (see comment from Sept. 11th) and Luna SR1 was released. > Unable to remove the JAX-RS facet on a Dynamic Web Project version 3.1 > ---------------------------------------------------------------------- > > Key: JBIDE-18117 > URL: https://issues.jboss.org/browse/JBIDE-18117 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: upstream, webservices > Affects Versions: 4.2.0.Beta3 > Reporter: Xavier Coulon > Assignee: Xavier Coulon > Fix For: 4.2.0.CR2 > > > A bug in Eclipse WTP causes the following exception: > {code} > java.lang.ClassCastException: org.eclipse.jst.javaee.web.internal.impl.WebAppImpl cannot be cast to org.eclipse.jst.j2ee.webapplication.WebApp > at org.eclipse.jst.ws.jaxrs.core.internal.project.facet.JAXRSFacetUninstallDelegate.uninstallJAXRSReferencesFromWebApp(JAXRSFacetUninstallDelegate.java:116) > at org.eclipse.jst.ws.jaxrs.core.internal.project.facet.JAXRSFacetUninstallDelegate.execute(JAXRSFacetUninstallDelegate.java:85) > at org.eclipse.wst.common.project.facet.core.internal.FacetedProject.callDelegate(FacetedProject.java:1477) > at org.eclipse.wst.common.project.facet.core.internal.FacetedProject.modifyInternal(FacetedProject.java:441) > at org.eclipse.wst.common.project.facet.core.internal.FacetedProject.mergeChangesInternal(FacetedProject.java:1181) > at org.eclipse.wst.common.project.facet.core.internal.FacetedProject.access$2(FacetedProject.java:1117) > at org.eclipse.wst.common.project.facet.core.internal.FacetedProject$5.run(FacetedProject.java:1099) > at org.eclipse.core.internal.resources.Workspace.run(Workspace.java:2313) > at org.eclipse.wst.common.project.facet.core.internal.FacetedProject.mergeChanges(FacetedProject.java:1109) > at org.eclipse.wst.common.project.facet.core.internal.FacetedProjectWorkingCopy.commitChanges(FacetedProjectWorkingCopy.java:2020) > at org.eclipse.wst.common.project.facet.ui.internal.FacetsPropertyPage$4.run(FacetsPropertyPage.java:232) > at org.eclipse.core.internal.resources.Workspace.run(Workspace.java:2313) > at org.eclipse.wst.common.project.facet.ui.internal.FacetsPropertyPage$5.run(FacetsPropertyPage.java:246) > at org.eclipse.jface.operation.ModalContext$ModalContextThread.run(ModalContext.java:122) > {code} > the problem comes from an evaluation that checks for dynamic project facet version 2.5 or 3.0 but not higher, in {{JAXRSJEEUtils#isWebApp25or40(Object)}} -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years

1
0
0 / 0

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

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18036?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen updated JBIDE-18036: ---------------------------------------- Fix Version/s: 4.2.1.Final (was: 4.2.0.CR2) > 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: Peter Palaga > Fix For: 4.2.1.Final > > 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.1#6329)

11 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-18395) Improve layout / Show CAT

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18395?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen updated JBIDE-18395: ---------------------------------------- Fix Version/s: 4.2.0.Final (was: 4.2.0.CR2) > Improve layout / Show CAT > ------------------------- > > Key: JBIDE-18395 > URL: https://issues.jboss.org/browse/JBIDE-18395 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: website > Affects Versions: 4.2.0.CR1 > Reporter: Xavier Coulon > Assignee: Xavier Coulon > Fix For: 4.2.0.Final > > > Show the CAT on the main page > See how 'intermediate' pages can be skipped to improve the navigation (and UX accross the site) -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-18117) Unable to remove the JAX-RS facet on a Dynamic Web Project version 3.1

by Xavier Coulon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18117?page=com.atlassian.jira.plugi... ] Xavier Coulon resolved JBIDE-18117. ----------------------------------- Resolution: Done Marking this issue as resolved since the patch was committed (see comment from Sept. 11th) and Luna SR1 was released. > Unable to remove the JAX-RS facet on a Dynamic Web Project version 3.1 > ---------------------------------------------------------------------- > > Key: JBIDE-18117 > URL: https://issues.jboss.org/browse/JBIDE-18117 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: upstream, webservices > Affects Versions: 4.2.0.Beta3 > Reporter: Xavier Coulon > Assignee: Xavier Coulon > Fix For: 4.2.0.CR2 > > > A bug in Eclipse WTP causes the following exception: > {code} > java.lang.ClassCastException: org.eclipse.jst.javaee.web.internal.impl.WebAppImpl cannot be cast to org.eclipse.jst.j2ee.webapplication.WebApp > at org.eclipse.jst.ws.jaxrs.core.internal.project.facet.JAXRSFacetUninstallDelegate.uninstallJAXRSReferencesFromWebApp(JAXRSFacetUninstallDelegate.java:116) > at org.eclipse.jst.ws.jaxrs.core.internal.project.facet.JAXRSFacetUninstallDelegate.execute(JAXRSFacetUninstallDelegate.java:85) > at org.eclipse.wst.common.project.facet.core.internal.FacetedProject.callDelegate(FacetedProject.java:1477) > at org.eclipse.wst.common.project.facet.core.internal.FacetedProject.modifyInternal(FacetedProject.java:441) > at org.eclipse.wst.common.project.facet.core.internal.FacetedProject.mergeChangesInternal(FacetedProject.java:1181) > at org.eclipse.wst.common.project.facet.core.internal.FacetedProject.access$2(FacetedProject.java:1117) > at org.eclipse.wst.common.project.facet.core.internal.FacetedProject$5.run(FacetedProject.java:1099) > at org.eclipse.core.internal.resources.Workspace.run(Workspace.java:2313) > at org.eclipse.wst.common.project.facet.core.internal.FacetedProject.mergeChanges(FacetedProject.java:1109) > at org.eclipse.wst.common.project.facet.core.internal.FacetedProjectWorkingCopy.commitChanges(FacetedProjectWorkingCopy.java:2020) > at org.eclipse.wst.common.project.facet.ui.internal.FacetsPropertyPage$4.run(FacetsPropertyPage.java:232) > at org.eclipse.core.internal.resources.Workspace.run(Workspace.java:2313) > at org.eclipse.wst.common.project.facet.ui.internal.FacetsPropertyPage$5.run(FacetsPropertyPage.java:246) > at org.eclipse.jface.operation.ModalContext$ModalContextThread.run(ModalContext.java:122) > {code} > the problem comes from an evaluation that checks for dynamic project facet version 2.5 or 3.0 but not higher, in {{JAXRSJEEUtils#isWebApp25or40(Object)}} -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-18383) forge command rely on english description label to lookup commands - fragile!

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18383?page=com.atlassian.jira.plugi... ] Fred Bricon commented on JBIDE-18383: ------------------------------------- +1 for using command ids. This will need a rebuild of the cheatsheet accordingly > forge command rely on english description label to lookup commands - fragile! > ----------------------------------------------------------------------------- > > Key: JBIDE-18383 > URL: https://issues.jboss.org/browse/JBIDE-18383 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: forge > Reporter: Max Rydahl Andersen > Assignee: Koen Aers > Priority: Critical > Fix For: 4.2.0.CR2 > > > it seems this is the way forge commands are looked up: > org.jboss.tools.forge.ui.runForgeCommand(org.jboss.tools.forge.ui.runForgeCommand.commandName=REST: Generate Endpoints From Entities)" > meaning if description changes the cheatsheet breaks. > should this not us a unique id or at least the cli command name so we have *one* API to obey to ? -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years

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 September 2014