July 2016 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (ERT-344) JSON schema references are not being resolved [EBZ#489452]

by Friendly Jira Robot (JIRA)

[ https://issues.jboss.org/browse/ERT-344?page=com.atlassian.jira.plugin.sy... ] Friendly Jira Robot resolved ERT-344. ------------------------------------- Resolution: Done > JSON schema references are not being resolved [EBZ#489452] > ---------------------------------------------------------- > > Key: ERT-344 > URL: https://issues.jboss.org/browse/ERT-344 > Project: Eclipse Release Train > Issue Type: Task > Components: WTP Source Editing > Reporter: Friendly Jira Robot > Labels: 3.8.1, bzira, wst.json > Fix For: Neon.1 (4.6) > > > I hooked up the swagger schema (http://json.schemastore.org/swagger-2.0) to the schema extension and have been assessing content assist in the editor. At this point, only the top level properties are being returned as proposals, indicating this function is a probably a work in progress, which is fine. One problem I see is that JSON references are not being resolved: > Currently, there are JSONObjects with name/value pairs that look like this: > {"$ref":"#/definitions/info"} > {"$ref":"#/definitions/paths"} > ..etc > It'll be good if the model can contain the resolved references for content assist/validation purposes. I'd like to raise this as a requirement if it hasn't already been captured. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (ERT-345) Template "new package.json" should be available only for package.json file [EBZ#494185]

by Friendly Jira Robot (JIRA)

[ https://issues.jboss.org/browse/ERT-345?page=com.atlassian.jira.plugin.sy... ] Friendly Jira Robot resolved ERT-345. ------------------------------------- Resolution: Done > Template "new package.json" should be available only for package.json file [EBZ#494185] > --------------------------------------------------------------------------------------- > > Key: ERT-345 > URL: https://issues.jboss.org/browse/ERT-345 > Project: Eclipse Release Train > Issue Type: Task > Components: WTP Source Editing > Reporter: Friendly Jira Robot > Labels: 3.8.1, bzira, wst.json > Fix For: Neon.1 (4.6) > > > When you open completion for any JSON file, you have a template "new package.json". > I understand that it's a cool feature for package.json, but it's a little strange for other JSON file. > I think this template should be moved to org.eclipse.wst.json.npm.ui plugin > (not sure it's easy to do that). -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (ERT-345) Template "new package.json" should be available only for package.json file [EBZ#494185]

by Friendly Jira Robot (JIRA)

Friendly Jira Robot created ERT-345: --------------------------------------- Summary: Template "new package.json" should be available only for package.json file [EBZ#494185] Key: ERT-345 URL: https://issues.jboss.org/browse/ERT-345 Project: Eclipse Release Train Issue Type: Task Components: WTP Source Editing Reporter: Friendly Jira Robot Fix For: Neon.1 (4.6) When you open completion for any JSON file, you have a template "new package.json". I understand that it's a cool feature for package.json, but it's a little strange for other JSON file. I think this template should be moved to org.eclipse.wst.json.npm.ui plugin (not sure it's easy to do that). -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (ERT-343) Add labels support to ContainerLauncher class [EBZ#497777]

by Jeff Johnston (JIRA)

[ https://issues.jboss.org/browse/ERT-343?page=com.atlassian.jira.plugin.sy... ] Jeff Johnston resolved ERT-343. ------------------------------- Resolution: Done > Add labels support to ContainerLauncher class [EBZ#497777] > ---------------------------------------------------------- > > Key: ERT-343 > URL: https://issues.jboss.org/browse/ERT-343 > Project: Eclipse Release Train > Issue Type: Task > Components: Linux Tools > Reporter: Friendly Jira Robot > Assignee: Jeff Johnston > Labels: 5.1.0, Docker, bzira > Fix For: Neon.1 (4.6) > > > Now that Run Image supports labels, the ContainerLauncher class should accept them as input. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (ERT-343) Add labels support to ContainerLauncher class [EBZ#497777]

by Jeff Johnston (JIRA)

[ https://issues.jboss.org/browse/ERT-343?page=com.atlassian.jira.plugin.sy... ] Jeff Johnston reassigned ERT-343: --------------------------------- Assignee: Jeff Johnston > Add labels support to ContainerLauncher class [EBZ#497777] > ---------------------------------------------------------- > > Key: ERT-343 > URL: https://issues.jboss.org/browse/ERT-343 > Project: Eclipse Release Train > Issue Type: Task > Components: Linux Tools > Reporter: Friendly Jira Robot > Assignee: Jeff Johnston > Labels: 5.1.0, Docker, bzira > Fix For: Neon.1 (4.6) > > > Now that Run Image supports labels, the ContainerLauncher class should accept them as input. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (ERT-343) Add labels support to ContainerLauncher class [EBZ#497777]

by Jeff Johnston (JIRA)

[ https://issues.jboss.org/browse/ERT-343?page=com.atlassian.jira.plugin.sy... ] Jeff Johnston updated ERT-343: ------------------------------ Sprint: devex #117 July 2016 > Add labels support to ContainerLauncher class [EBZ#497777] > ---------------------------------------------------------- > > Key: ERT-343 > URL: https://issues.jboss.org/browse/ERT-343 > Project: Eclipse Release Train > Issue Type: Task > Components: Linux Tools > Reporter: Friendly Jira Robot > Assignee: Jeff Johnston > Labels: 5.1.0, Docker, bzira > Fix For: Neon.1 (4.6) > > > Now that Run Image supports labels, the ContainerLauncher class should accept them as input. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22726) Associate jbosstools & devstudio marketplace entries by fileextension to file types opened in Eclipse

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22726?page=com.atlassian.jira.plugi... ] Alexey Kazakov commented on JBIDE-22726: ---------------------------------------- OK, So we can add .html, .htm, for our HTML editor. Also .xhtml for JSF. > Associate jbosstools & devstudio marketplace entries by fileextension to file types opened in Eclipse > ----------------------------------------------------------------------------------------------------- > > Key: JBIDE-22726 > URL: https://issues.jboss.org/browse/JBIDE-22726 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: marketplace > Affects Versions: 4.4.0.Final > Reporter: Nick Boldt > Assignee: Alexey Kazakov > > I need a list of file extensions we want associated with JBT/devstudio. > Then I can add those to the list of tags on the marketplace entries: > https://marketplace.eclipse.org/content/jboss-tools > https://marketplace.eclipse.org/content/red-hat-jboss-developer-studio > eg., for freemarker, we want to add tag = *fileExtension_ftl* [1] > ref: https://www.eclipse.org/eclipse/news/4.6/platform.php#text-editor-selecti... > ref: https://www.eclipse.org/community/eclipse_newsletter/2016/june/article1.php (see #5) > [1] https://marketplace.eclipse.org/content/freemarker-ide-jboss-tools > related: https://bugs.eclipse.org/bugs/show_bug.cgi?id=480176 > related: https://bugs.eclipse.org/bugs/show_bug.cgi?id=494050 -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (ERT-343) Add labels support to ContainerLauncher class [EBZ#497777]

by Friendly Jira Robot (JIRA)

Friendly Jira Robot created ERT-343: --------------------------------------- Summary: Add labels support to ContainerLauncher class [EBZ#497777] Key: ERT-343 URL: https://issues.jboss.org/browse/ERT-343 Project: Eclipse Release Train Issue Type: Task Components: Linux Tools Reporter: Friendly Jira Robot Fix For: Neon.1 (4.6) Now that Run Image supports labels, the ContainerLauncher class should accept them as input. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22726) Associate jbosstools & devstudio marketplace entries by fileextension to file types opened in Eclipse

by Mickael Istria (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22726?page=com.atlassian.jira.plugi... ] Mickael Istria commented on JBIDE-22726: ---------------------------------------- As we have a nice HTML preview and advanced JSF, it could be worth adding also those file types. Currently, only association with extension (last segment) is supported. And yes, installing the marketplace entry associated to an extension will suggest to install the whole extension (like a regular MP installation), not only a subset. > Associate jbosstools & devstudio marketplace entries by fileextension to file types opened in Eclipse > ----------------------------------------------------------------------------------------------------- > > Key: JBIDE-22726 > URL: https://issues.jboss.org/browse/JBIDE-22726 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: marketplace > Affects Versions: 4.4.0.Final > Reporter: Nick Boldt > Assignee: Alexey Kazakov > > I need a list of file extensions we want associated with JBT/devstudio. > Then I can add those to the list of tags on the marketplace entries: > https://marketplace.eclipse.org/content/jboss-tools > https://marketplace.eclipse.org/content/red-hat-jboss-developer-studio > eg., for freemarker, we want to add tag = *fileExtension_ftl* [1] > ref: https://www.eclipse.org/eclipse/news/4.6/platform.php#text-editor-selecti... > ref: https://www.eclipse.org/community/eclipse_newsletter/2016/june/article1.php (see #5) > [1] https://marketplace.eclipse.org/content/freemarker-ide-jboss-tools > related: https://bugs.eclipse.org/bugs/show_bug.cgi?id=480176 > related: https://bugs.eclipse.org/bugs/show_bug.cgi?id=494050 -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 9 months

1
0
0 / 0

[JBoss JIRA] (ERT-342) Breakpoints doesn't hit if create Project from existing source. [EBZ#439778]

by Friendly Jira Robot (JIRA)

Friendly Jira Robot created ERT-342: --------------------------------------- Summary: Breakpoints doesn't hit if create Project from existing source. [EBZ#439778] Key: ERT-342 URL: https://issues.jboss.org/browse/ERT-342 Project: Eclipse Release Train Issue Type: Task Components: JSDT Reporter: Friendly Jira Robot I created JavaScript project (Name: Sample) using "Create Project from existing source" Let see in "C:\TestProject" which contains test.js script. Now i opened test.js and added some breakpoint in that script, now when I'm running the script breakpoint is Not Hitting. *****************Investigation******************** org.eclipse.wst.jsdt.debug.internal.core.model.ScriptResolutionManager there is a function guessScriptMatches(ScriptReference script, IPath path). JavaDoc of this function: "Guesses if the paths are considered equal by walking backward from the last segment of the paths and counting the matching segments. The paths are guessed to be equal iff any two or more segments match in order." So in My case because Project name and physical folder name are different. That why only file name is matching, but this function is checking for at least 2 segment to match, so it returns false and caller function will not add JavaScriptDebugTarget for this script. ******************** Solution Proposal********************* We can check if current script is inside root folder of project then if one segment matches we'll return true, for other case it will remain check for at least two segment to match -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 9 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