August 2015 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-20386) Autocompleation uses very outdated data

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20386?page=com.atlassian.jira.plugi... ] Denis Golovin updated JBIDE-20386: ---------------------------------- Fix Version/s: 4.3.x > Autocompleation uses very outdated data > --------------------------------------- > > Key: JBIDE-20386 > URL: https://issues.jboss.org/browse/JBIDE-20386 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: freemarker > Reporter: Daniel Dekany > Assignee: Denis Golovin > Fix For: 4.3.x > > > When you press Ctrl+Space after {{<#}} or in an expression after {{foo?}}, the list of directive names, and especially the list of built-in names shown is very outdated. Instead of maintaining these lists manually, the list of directive names could be get from {{freemarker.template.Configuration.getSupportedBuiltInDirectiveNames()}}, and the list of built-in names from {{Configuration.getSupportedBuiltInNames()}}. > Some complication since 2.3.23 is that the list of names should be filtered based on {{Template.getActualNamingConvention()}} (which either returns {{Configuration.LEGACY_NAMING_CONVENTION}} or {{Configuration.CAMEL_CASE_NAMING_CONVENTION}}). Though the algorithm for that is simple: If a name contains upper case letter then it's camel case. Otherwise, if it contains {{_}} then it belongs to the legacy naming convention. Otherwise if it's a directive name that equals to a lower-cased camel case directive name, then it's legacy naming convention (consider {{elseIf}} VS {{elseif}}). Otherwise the name belongs to both naming conventions. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20401) OpenShift tooling UI should include a link to user docs

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20401?page=com.atlassian.jira.plugi... ] Fred Bricon commented on JBIDE-20401: ------------------------------------- [~mhusnain]: will the new doc/video cover the Eclipse tooling? Because this is something that we want/need > OpenShift tooling UI should include a link to user docs > ------------------------------------------------------- > > Key: JBIDE-20401 > URL: https://issues.jboss.org/browse/JBIDE-20401 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: openshift > Reporter: Len DiMaggio > Assignee: Nick Boldt > Priority: Blocker > Labels: help_wanted > Fix For: 4.3.0.CR1 > > > Given the very different architecture of OpenShift v3 as compared to v2, we should provide users with a link to docs detailing the differences. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20210) For JBIDE 4.3.0.CR1: Migrate to using license feature in JBT 4.3 / JBDS 9 [Webservices]

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20210?page=com.atlassian.jira.plugi... ] Denis Golovin commented on JBIDE-20210: --------------------------------------- It was applied 10 days ago. Resolving. > For JBIDE 4.3.0.CR1: Migrate to using license feature in JBT 4.3 / JBDS 9 [Webservices] > --------------------------------------------------------------------------------------- > > Key: JBIDE-20210 > URL: https://issues.jboss.org/browse/JBIDE-20210 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: webservices > Reporter: Nick Boldt > Assignee: Denis Golovin > Priority: Blocker > Labels: task > Fix For: 4.3.0.CR1 > > > For JBIDE 4.3.0.CR1 [Webservices]: Please perform the following tasks: > 1. Ensure your component features/plugins have been [properly upversioned|http://wiki.eclipse.org/Version_Numbering#Overall_example], eg., from 1.0.0 to 1.1.0 or 1.0.100. > 2. Switch to using the new o.j.t.foundation.license.feature. Instructions here: > https://github.com/jbosstools/jbosstools-devdoc/blob/master/source/how_to... > 2. Resolve this JIRA when done. QE can then verify and close it later. > [Search for all task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...], or [Search for Webservices task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...] -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20210) For JBIDE 4.3.0.CR1: Migrate to using license feature in JBT 4.3 / JBDS 9 [Webservices]

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20210?page=com.atlassian.jira.plugi... ] Denis Golovin resolved JBIDE-20210. ----------------------------------- Resolution: Done Released to master. > For JBIDE 4.3.0.CR1: Migrate to using license feature in JBT 4.3 / JBDS 9 [Webservices] > --------------------------------------------------------------------------------------- > > Key: JBIDE-20210 > URL: https://issues.jboss.org/browse/JBIDE-20210 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: webservices > Reporter: Nick Boldt > Assignee: Denis Golovin > Priority: Blocker > Labels: task > Fix For: 4.3.0.CR1 > > > For JBIDE 4.3.0.CR1 [Webservices]: Please perform the following tasks: > 1. Ensure your component features/plugins have been [properly upversioned|http://wiki.eclipse.org/Version_Numbering#Overall_example], eg., from 1.0.0 to 1.1.0 or 1.0.100. > 2. Switch to using the new o.j.t.foundation.license.feature. Instructions here: > https://github.com/jbosstools/jbosstools-devdoc/blob/master/source/how_to... > 2. Resolve this JIRA when done. QE can then verify and close it later. > [Search for all task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...], or [Search for Webservices task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...] -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20475) Upgrade Forge Runtime to 2.19.0.Final

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20475?page=com.atlassian.jira.plugi... ] George Gastaldi resolved JBIDE-20475. ------------------------------------- Resolution: Done > Upgrade Forge Runtime to 2.19.0.Final > ------------------------------------- > > Key: JBIDE-20475 > URL: https://issues.jboss.org/browse/JBIDE-20475 > Project: Tools (JBoss Tools) > Issue Type: Component Upgrade > Components: forge > Affects Versions: 4.3.0.Beta2 > Reporter: George Gastaldi > Assignee: George Gastaldi > Labels: new_and_noteworthy > Fix For: 4.3.0.CR1 > > -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBTIS-486) FuseIDE - Migrate to use new license feature in JBTIS 4.3 / JBDS IS 9

by Lars Heinemann (JIRA)

[ https://issues.jboss.org/browse/JBTIS-486?page=com.atlassian.jira.plugin.... ] Lars Heinemann commented on JBTIS-486: -------------------------------------- merged PR > FuseIDE - Migrate to use new license feature in JBTIS 4.3 / JBDS IS 9 > --------------------------------------------------------------------- > > Key: JBTIS-486 > URL: https://issues.jboss.org/browse/JBTIS-486 > Project: JBoss Tools Integration Stack > Issue Type: Sub-task > Components: Fuse IDE > Affects Versions: 9.0.0.Alpha1 > Reporter: Paul Leacu > Assignee: Paul Leacu > Priority: Blocker > Fix For: 4.3.0.Beta1 > > Attachments: fuse-new-licenses1.png, fuse-new-licenses2.png, fuse-new-licenses3.png > > > Please make sure that Fuse Tooling is including the new license feature. See parent Jira description for details. > ref: https://github.com/jbosstools/jbosstools-devdoc/blob/master/source/how_to... -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20475) Upgrade Forge Runtime to 2.19.0.Final

by George Gastaldi (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20475?page=com.atlassian.jira.plugi... ] George Gastaldi updated JBIDE-20475: ------------------------------------ Summary: Upgrade Forge Runtime to 2.19.0.Final (was: Upgrade Forge Runtime to 2.18.1.Final) > Upgrade Forge Runtime to 2.19.0.Final > ------------------------------------- > > Key: JBIDE-20475 > URL: https://issues.jboss.org/browse/JBIDE-20475 > Project: Tools (JBoss Tools) > Issue Type: Component Upgrade > Components: forge > Affects Versions: 4.3.0.Beta2 > Reporter: George Gastaldi > Assignee: George Gastaldi > Labels: new_and_noteworthy > Fix For: 4.3.0.CR1 > > -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20529) Master JIRA for XML Validation Problems

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20529?page=com.atlassian.jira.plugi... ] Rob Stryker commented on JBIDE-20529: ------------------------------------- A scan of all wildfly quickstarts found that all examples have namespace / xsd urls that are accurate. Though some are in fact redirects, the redirects are accurate and none redirect to an html page. The upstream issue for following redirects is https://bugs.eclipse.org/bugs/show_bug.cgi?id=474741 There has been no upstream response to this issue yet. > Master JIRA for XML Validation Problems > --------------------------------------- > > Key: JBIDE-20529 > URL: https://issues.jboss.org/browse/JBIDE-20529 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: project-examples, server > Reporter: Rob Stryker > > This JIRA is meant to be a master container jira for all xml validation issues. These include identifying projects that are enganging in bad xml behavior, projects that point to namespaces or xsd locations that no longer exist, example projects using relative paths for linking to other xsd, and others. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20529) Master JIRA for XML Validation Problems

by Rob Stryker (JIRA)

Rob Stryker created JBIDE-20529: ----------------------------------- Summary: Master JIRA for XML Validation Problems Key: JBIDE-20529 URL: https://issues.jboss.org/browse/JBIDE-20529 Project: Tools (JBoss Tools) Issue Type: Feature Request Components: project-examples, server Reporter: Rob Stryker This JIRA is meant to be a master container jira for all xml validation issues. These include identifying projects that are enganging in bad xml behavior, projects that point to namespaces or xsd locations that no longer exist, example projects using relative paths for linking to other xsd, and others. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBTIS-487) SwitchYard - Migrate to use new license feature in JBTIS 4.3 / JBDS IS 9

by Brian Fitzpatrick (JIRA)

[ https://issues.jboss.org/browse/JBTIS-487?page=com.atlassian.jira.plugin.... ] Brian Fitzpatrick commented on JBTIS-487: ----------------------------------------- [~pleacu] or [~nickboldt] any ideas on what I am missing? I'm sure it's something obvious but I can't put my finger on it. > SwitchYard - Migrate to use new license feature in JBTIS 4.3 / JBDS IS 9 > ------------------------------------------------------------------------ > > Key: JBTIS-487 > URL: https://issues.jboss.org/browse/JBTIS-487 > Project: JBoss Tools Integration Stack > Issue Type: Sub-task > Components: switchyard > Affects Versions: 9.0.0.Alpha1 > Reporter: Paul Leacu > Assignee: Brian Fitzpatrick > Priority: Blocker > Fix For: 4.3.0.Beta1 > > > Please make sure that SwitchYard is including the new license feature. See parent Jira description for details. > ref: https://github.com/jbosstools/jbosstools-devdoc/blob/master/source/how_to... -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 2 months

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 August 2015