February 2018 - jbosstools-issues

[JBoss JIRA] (ERT-532) Overall repo merge issue [EBZ#525342]

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/ERT-532?page=com.atlassian.jira.plugin.sy... ] Nick Boldt updated ERT-532: --------------------------- Fix Version/s: Photon (4.8) M5 (was: Photon (4.8) M4) > Overall repo merge issue [EBZ#525342] > ------------------------------------- > > Key: ERT-532 > URL: https://issues.jboss.org/browse/ERT-532 > Project: Eclipse Release Train > Issue Type: Task > Components: WTP Releng > Reporter: Friendly Jira Robot > Assignee: Nick Boldt > Labels: bzira, releng > Fix For: Photon (4.8) M5 > > > Intent of this issue is to track the work needed to merge the 21 WTP projects [1] down to 8: > * common > * servertools > * sourceediting > * jsdt > * javaee-ejb > * webservices > * jsf > * dali > [1] https://wiki.eclipse.org/WTP_Gerrit_Access#Clone_a_repository_for_develop... > First pass at merging requires these two merge scripts to be run for servertools [2] and sourceediting [3]. > [2] https://bugs.eclipse.org/bugs/show_bug.cgi?id=519780 -> https://gist.github.com/robstryker/e79310e3ca09de45bf62c9264ac506e7 > [3] https://bugs.eclipse.org/bugs/show_bug.cgi?id=520044 -> https://gist.github.com/robstryker/054b9f2315a9bddd0ca76acebbd44610 > Later, once we have consensus on what to do about javaee & ejb, I'll link to that merge script and the downstream ones for ws and jsf. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years

1
0
0 / 0

[JBoss JIRA] (ERT-539) terminal produced by "Execute Shell" times out after 30 seconds of inactivity. This is extremely annoying [EBZ#525915]

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/ERT-539?page=com.atlassian.jira.plugin.sy... ] Nick Boldt updated ERT-539: --------------------------- Fix Version/s: Oxygen.3 (4.7) (was: Oxygen.2 (4.7)) > terminal produced by "Execute Shell" times out after 30 seconds of inactivity. This is extremely annoying [EBZ#525915] > ---------------------------------------------------------------------------------------------------------------------- > > Key: ERT-539 > URL: https://issues.jboss.org/browse/ERT-539 > Project: Eclipse Release Train > Issue Type: Task > Components: Linux Tools > Reporter: Friendly Jira Robot > Labels: 6.2.0, Docker, bzira > Fix For: Oxygen.3 (4.7) > > > The terminal produced by the "Execute Shell" command times out after 30 seconds of inactivity. This is extremely annoying. Can it be set to something a lot longer or at least be configurable? -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years

1
0
0 / 0

[JBoss JIRA] (ERT-476) User can install software from market without acceptation license agreements [EBZ#509500]

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/ERT-476?page=com.atlassian.jira.plugin.sy... ] Nick Boldt updated ERT-476: --------------------------- Fix Version/s: Oxygen.3 (4.7) (was: Neon.3 (4.6)) > User can install software from market without acceptation license agreements [EBZ#509500] > ----------------------------------------------------------------------------------------- > > Key: ERT-476 > URL: https://issues.jboss.org/browse/ERT-476 > Project: Eclipse Release Train > Issue Type: Task > Components: MPC > Reporter: Friendly Jira Robot > Labels: Marketplace, bzira > Fix For: Oxygen.3 (4.7) > > > Created attachment 265962 > The "Review Licenses" window where the "Finish" button is available though the licence is not accepted. > User can install Red Hat JBoss Developer Studio from Eclipse Marketplace without acceptation terms of the licence agreements. > Step to reproduce: > 1) Download, unpack and start Eclipse Neon 1 > http://www.eclipse.org/downloads/download.php?file=/technology/epp/downlo... > 2) Help -> Eclipse Marketplace -> Search for "Red Hat JBoss Developer Studio 10.2.0.GA" -> Install > 3) The window "Review Licenses" looks like on the attached screenshot > 4) Notice that "I do not accept..." is selected but Finish button is enabled and user is able to install Developer Studio. > When I click "I accept..." radio button and then switch back to "I do not accept..." it starts work correctly. So, the availability of the 'Finish' button is evaluated badly only in initial state. > I tried to remove ~/.eclipse directory and start Eclipse with new workspace but it didn't solve my problem. > This problem doesn't occur when installing JBoss Tools. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years

1
0
0 / 0

[JBoss JIRA] (ERT-165) Refactor the Connection Wizard [EBZ#492420]

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/ERT-165?page=com.atlassian.jira.plugin.sy... ] Nick Boldt updated ERT-165: --------------------------- Fix Version/s: Oxygen.3 (4.7) (was: Oxygen (4.7)) > Refactor the Connection Wizard [EBZ#492420] > ------------------------------------------- > > Key: ERT-165 > URL: https://issues.jboss.org/browse/ERT-165 > Project: Eclipse Release Train > Issue Type: Task > Components: Linux Tools > Reporter: Friendly Jira Robot > Assignee: Xavier Coulon > Labels: 5.0.0, Docker, bzira > Fix For: Oxygen.3 (4.7) > > > Refactor the connection wizard to provide: > - a table with all existing Docker instances (native, Docker for Mac/Windows and Docker Machine) > - a simplified form to specify custom settings, more directly based on the env variables that are used by the Docker CLI client (DOCKER_HOST, DOCKER_TLS_VERIFY and DOCKER_CERT_PATH) -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years

1
0
0 / 0

[JBoss JIRA] (ERT-164) Improve connection detection in connection wizard [EBZ#475892]

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/ERT-164?page=com.atlassian.jira.plugin.sy... ] Nick Boldt updated ERT-164: --------------------------- Fix Version/s: Oxygen.3 (4.7) (was: Oxygen (4.7)) > Improve connection detection in connection wizard [EBZ#475892] > -------------------------------------------------------------- > > Key: ERT-164 > URL: https://issues.jboss.org/browse/ERT-164 > 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) > > > The wizard should not block the UI when opening (especially when connection settings are found but no Docker daemon is available) > Also, in case of connection test failure, an error dialog with the root cause would be interesting. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years

1
0
0 / 0

[JBoss JIRA] (ERT-33) [JFace] MessageDialog should use Link instead of Text [EBZ#484347]

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/ERT-33?page=com.atlassian.jira.plugin.sys... ] Nick Boldt updated ERT-33: -------------------------- Fix Version/s: Oxygen.3 (4.7) (was: Oxygen (4.7)) > [JFace] MessageDialog should use Link instead of Text [EBZ#484347] > ------------------------------------------------------------------ > > Key: ERT-33 > URL: https://issues.jboss.org/browse/ERT-33 > Project: Eclipse Release Train > Issue Type: Task > Components: Platform > Reporter: Max Rydahl Andersen > Priority: Trivial > Labels: 4.6_M6, UI, bzira > Fix For: Oxygen.3 (4.7) > > > In Eclipse IDE, I see many message dialogs giving instruction about opening a wizard or the preference page. Giving such instructions to user is nice, but in many cases, it would be even better to allow user to perform such operations in one click. For example a message dialog with "configure proxy" would have a link to immediately open the proxy settings page. > Those message dialog should also allow selectionListeners for those links. > If MessageDialog provide links by default, it will encourage consumers to take advantage of them, and to be more helpful to their users. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years

1
0
0 / 0

[JBoss JIRA] (ERT-327) Pull new version of an image [EBZ#497010]

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/ERT-327?page=com.atlassian.jira.plugin.sy... ] Nick Boldt updated ERT-327: --------------------------- Fix Version/s: Oxygen.3 (4.7) (was: Oxygen (4.7) M7) > Pull new version of an image [EBZ#497010] > ----------------------------------------- > > Key: ERT-327 > URL: https://issues.jboss.org/browse/ERT-327 > 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: Oxygen.3 (4.7) > > > The Docker tooling should allow for pull the new version of a selected image. For example, the image tagged 'latest' might have changed. > In the UI, the "Tag selection" page on the Search wizard should provide with a state indicating that an image with the tag was already pulled but is out-dated > Also, in the context menu, a command handle to pull an updated version could be added. -- This message was sent by Atlassian JIRA (v7.5.0#75005)

8 years

1
0
0 / 0

[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

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

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

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