February 2018 - jbosstools-issues

[JBoss JIRA] (ERT-348) mouse hover over member variable does not show it value [EBZ#497965]

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/ERT-348?page=com.atlassian.jira.plugin.sy... ] Nick Boldt updated ERT-348: --------------------------- Fix Version/s: Oxygen.3 (4.7) (was: Neon.2 (4.6)) > mouse hover over member variable does not show it value [EBZ#497965] > -------------------------------------------------------------------- > > Key: ERT-348 > URL: https://issues.jboss.org/browse/ERT-348 > Project: Eclipse Release Train > Issue Type: Task > Components: JSDT > Reporter: Friendly Jira Robot > Assignee: Ilya Buziuk > Labels: Debug, bzira > Fix For: Oxygen.3 (4.7) > > > While debugging, if I hover with my mouse over “myVar” part of the expression “myVar.myProp.mySubProp.abc” in my JS editor, I see a tooltip with its current value. But if I hover over the last segment “abc” of the same expression nothing happens. If I want to see its value, I have to move the mouse to “myVar” and when the tooltip opens up I have to click to expand, scroll to “myProp”, click to expand, scroll to “mySubProp”, expand, etc. until I see “abc”. Would be a real time saver when I hover over “abc” to see its value. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 3 months

1
0
0 / 0

[JBoss JIRA] (ERT-346) If I add a breakpoint to a project called "node_modules" the program is not suspended [EBZ#497703]

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/ERT-346?page=com.atlassian.jira.plugin.sy... ] Nick Boldt updated ERT-346: --------------------------- Fix Version/s: Oxygen.3 (4.7) (was: Neon.2 (4.6)) > If I add a breakpoint to a project called "node_modules" the program is not suspended [EBZ#497703] > -------------------------------------------------------------------------------------------------- > > Key: ERT-346 > URL: https://issues.jboss.org/browse/ERT-346 > Project: Eclipse Release Train > Issue Type: Task > Components: JSDT > Reporter: Friendly Jira Robot > Assignee: Ilya Buziuk > Labels: Debug, bzira > Fix For: Oxygen.3 (4.7) > > > We use feature in node that we can put out modules in a “node_modules” in a parent folder and it will be properly found: https://nodejs.org/api/modules.html#modules_loading_from_node_modules_fol... > Node is working properly but if I add a breakpoint in a source file inside “node_modules” the breakpoint does not get hit. > To reproduce the issue: > 1. Create a JavaScript project “test”. > 2. Add a file “test.js” to the project with content: > var m1 = require("m1"); > console.log("m1.myFunc = " + m1.myFunc(3)); > 3. Create a JavaScript project called “node_modules”. > 4. Add a folder “m1” to the project “node_modules”. > 5. Add a file “index.js” to the folder “m1” with content: > module.exports.myFunc = function( i) { > return i*i; > } > 6. Debug “test.js” as Node – it works. Node is finding property “index.js”. 7. Add a breakpoint to “index.js”. > 8. Debug “test.js” as Node – it runs, but the breakpoint does not suspend the target. > Is there workaround for this issues? > Most of our projects are relying on the “node_modules” being found in the parent folder. That is making most of our code hard to debug. > I tested this on Ubuntu 14.04. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 3 months

1
0
0 / 0

[JBoss JIRA] (ERT-503) Deadlock DependencyGraphImpl and ComponentCore [backport/patch for Neon.3 / WTP 3.8.2] [EBZ#515270]

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/ERT-503?page=com.atlassian.jira.plugin.sy... ] Nick Boldt updated ERT-503: --------------------------- Fix Version/s: Oxygen.3 (4.7) (was: Neon.3 (4.6)) > Deadlock DependencyGraphImpl and ComponentCore [backport/patch for Neon.3 / WTP 3.8.2] [EBZ#515270] > --------------------------------------------------------------------------------------------------- > > Key: ERT-503 > URL: https://issues.jboss.org/browse/ERT-503 > Project: Eclipse Release Train > Issue Type: Task > Components: WTP Common Tools > Reporter: Friendly Jira Robot > Labels: 3.8.2, bzira, wst.common > Fix For: Oxygen.3 (4.7) > > > Request to backport https://bugs.eclipse.org/bugs/show_bug.cgi?id=511793 for Neon.3 / WTP 3.8.2 as a Maintenance update (to 3.8.3M) or a patchfix (to 3.8.3P). > See issue details in https://bugs.eclipse.org/bugs/show_bug.cgi?id=511793 > Downstream issues: > * Fedora/RHSCL: https://bugzilla.redhat.com/show_bug.cgi?id=1440205 > * JBoss Tools/Devstudio: https://issues.jboss.org/browse/JBIDE-24240 -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 3 months

1
0
0 / 0

[JBoss JIRA] (ERT-352) Implement checkbox to show/hide nightly builds of mobile engines [EBZ#498266]

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/ERT-352?page=com.atlassian.jira.plugin.sy... ] Nick Boldt updated ERT-352: --------------------------- Fix Version/s: Oxygen.3 (4.7) (was: Neon.1 (4.6)) > Implement checkbox to show/hide nightly builds of mobile engines [EBZ#498266] > ----------------------------------------------------------------------------- > > Key: ERT-352 > URL: https://issues.jboss.org/browse/ERT-352 > Project: Eclipse Release Train > Issue Type: Task > Components: Thym > Reporter: Friendly Jira Robot > Priority: Trivial > Labels: 2.1.0, General, bzira > Fix For: Oxygen.3 (4.7) > > > Download Hybrid Mobile Engine wizard shows nightly and stable builds of mobile engines in the same list. The list is pretty long. I think better is to have a checkbox for showing/hiding nightly builds. What do you think? -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 3 months

1
0
0 / 0

[JBoss JIRA] (ERT-351) Can not retrieve plugin catalog [EBZ#498254]

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/ERT-351?page=com.atlassian.jira.plugin.sy... ] Nick Boldt updated ERT-351: --------------------------- Fix Version/s: Oxygen.3 (4.7) (was: Neon.1 (4.6)) > Can not retrieve plugin catalog [EBZ#498254] > -------------------------------------------- > > Key: ERT-351 > URL: https://issues.jboss.org/browse/ERT-351 > Project: Eclipse Release Train > Issue Type: Task > Components: Thym > Reporter: Friendly Jira Robot > Labels: 2.1.0, General, bzira > Fix For: Oxygen.3 (4.7) > > > Created attachment 263226 > screenshot.png > 1) Open new thym project wizard > 2) the error will pop out (happens occasionally) > Stacktrace: > ------------ > com.google.gson.stream.MalformedJsonException: Use JsonReader.setLenient(true) to accept malformed JSON at line 2 column 1 > at com.google.gson.stream.JsonReader.syntaxError(JsonReader.java:1505) > at com.google.gson.stream.JsonReader.checkLenient(JsonReader.java:1386) > at com.google.gson.stream.JsonReader.doPeek(JsonReader.java:572) > at com.google.gson.stream.JsonReader.beginObject(JsonReader.java:368) > at org.eclipse.thym.core.plugin.registry.CordovaPluginRegistryManager.retrievePluginInfos(CordovaPluginRegistryManager.java:182) > at org.eclipse.thym.ui.plugins.internal.CordovaPluginSelectionPage$9.run(CordovaPluginSelectionPage.java:299) > at org.eclipse.jface.operation.ModalContext$ModalContextThread.run(ModalContext.java:119) -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 3 months

1
0
0 / 0

[JBoss JIRA] (ERT-202) Can't tune docker timeout [EBZ#494131]

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/ERT-202?page=com.atlassian.jira.plugin.sy... ] Nick Boldt updated ERT-202: --------------------------- Fix Version/s: Oxygen.3 (4.7) (was: Neon.1 (4.6)) > Can't tune docker timeout [EBZ#494131] > -------------------------------------- > > Key: ERT-202 > URL: https://issues.jboss.org/browse/ERT-202 > Project: Eclipse Release Train > Issue Type: Task > Components: Linux Tools > Reporter: Friendly Jira Robot > Labels: Docker, bzira > Fix For: Oxygen.3 (4.7) > > -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 3 months

1
0
0 / 0

[JBoss JIRA] (ERT-151) Data Volume Container do not need a container path [EBZ#483012]

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/ERT-151?page=com.atlassian.jira.plugin.sy... ] Nick Boldt updated ERT-151: --------------------------- Fix Version/s: Oxygen.3 (4.7) (was: Neon.1 (4.6)) > Data Volume Container do not need a container path [EBZ#483012] > --------------------------------------------------------------- > > Key: ERT-151 > URL: https://issues.jboss.org/browse/ERT-151 > Project: Eclipse Release Train > Issue Type: Task > Components: Linux Tools > Reporter: Friendly Jira Robot > Labels: 5.0.0, Docker, bzira > Fix For: Oxygen.3 (4.7) > > > The dialog to specify the volumes for a container to run is wrong, because data volume containers are not mounted on a user-given container path but instead, the selected container will mount its own defined volume. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 3 months

1
0
0 / 0

[JBoss JIRA] (ERT-148) Add support for custom Dockerfile name to build an image [EBZ#481093]

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/ERT-148?page=com.atlassian.jira.plugin.sy... ] Nick Boldt updated ERT-148: --------------------------- Fix Version/s: Oxygen.3 (4.7) (was: Neon.1 (4.6)) > Add support for custom Dockerfile name to build an image [EBZ#481093] > --------------------------------------------------------------------- > > Key: ERT-148 > URL: https://issues.jboss.org/browse/ERT-148 > Project: Eclipse Release Train > Issue Type: Task > Components: Linux Tools > Reporter: Friendly Jira Robot > Assignee: Xavier Coulon > Labels: Docker, bzira > Fix For: Oxygen.3 (4.7) > > > Docker supports custom Dockerfile names to build an image but this feature requires Docker Java client version 3.1.3 or higher (see https://github.com/spotify/docker-client/commit/b3b7371d7e6410e5c8b17cf7d...) > See bug 474196 for support for other options. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 3 months

1
0
0 / 0

[JBoss JIRA] (ERT-8) support docker ignore [EBZ#469819]

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/ERT-8?page=com.atlassian.jira.plugin.syst... ] Nick Boldt updated ERT-8: ------------------------- Fix Version/s: Oxygen.3 (4.7) (was: Neon.1 (4.6)) > support docker ignore [EBZ#469819] > ---------------------------------- > > Key: ERT-8 > URL: https://issues.jboss.org/browse/ERT-8 > Project: Eclipse Release Train > Issue Type: Task > Components: Linux Tools > Reporter: Max Rydahl Andersen > Priority: Trivial > Labels: Docker, bzira > Fix For: Oxygen.3 (4.7) > > > it does not look like docker build from eclipse honors .dockerignore > which makes its builds much slower for projects that contain source and other artifacts. > example with project using .dockerignore https://github.com/jbosstools/jbosstools-website -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 3 months

1
0
0 / 0

[JBoss JIRA] (ERT-422) tycho-extras:compare-version-with-baselines does not work for features [EBZ#502009]

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/ERT-422?page=com.atlassian.jira.plugin.sy... ] Nick Boldt updated ERT-422: --------------------------- Fix Version/s: Oxygen.3 (4.7) (was: Neon.2 (4.6)) > tycho-extras:compare-version-with-baselines does not work for features [EBZ#502009] > ----------------------------------------------------------------------------------- > > Key: ERT-422 > URL: https://issues.jboss.org/browse/ERT-422 > Project: Eclipse Release Train > Issue Type: Task > Components: Tycho > Reporter: Friendly Jira Robot > Assignee: Mickael Istria > Labels: Core, bzira > Fix For: Oxygen.3 (4.7) > > > When a feature is compared to baselines, if the source feature is generated during the build, the check fail for the source feature because the baseline artifact is compared to the wrong artifact (the binary one and not the source one) -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years, 3 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 February 2018