February 2017 - jbosstools-issues

[JBoss JIRA] (JBDS-3869) DevSuite Installer should check/warn if Hyper-V is already enabled

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBDS-3869?page=com.atlassian.jira.plugin.... ] Denis Golovin updated JBDS-3869: -------------------------------- Sprint: (was: devex #127 February 2017) > DevSuite Installer should check/warn if Hyper-V is already enabled > ------------------------------------------------------------------ > > Key: JBDS-3869 > URL: https://issues.jboss.org/browse/JBDS-3869 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Bug > Components: platform-installer > Affects Versions: 9.1.0.Beta1 > Environment: Windows 10 Pro, 64 bit. > Reporter: Robert Terzi > Assignee: Denis Golovin > Labels: ui > Fix For: 10.4.0.AM1 > > > The platform installer should check and warn if Hyper-V is already enabled on Windows systems. > Hyper-V takes over the virtualization assist hardware, which will keep VirtualBox from being able to start the CDK box which depends on VT-x/AMD-V. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBDS-4253) Show warning for virtualbox component if virtualization is not enabled or cannot be detected

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBDS-4253?page=com.atlassian.jira.plugin.... ] Denis Golovin updated JBDS-4253: -------------------------------- Sprint: (was: devex #127 February 2017) > Show warning for virtualbox component if virtualization is not enabled or cannot be detected > -------------------------------------------------------------------------------------------- > > Key: JBDS-4253 > URL: https://issues.jboss.org/browse/JBDS-4253 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Feature Request > Components: platform-installer > Affects Versions: 10.3.0.AM2 > Reporter: Denis Golovin > Assignee: Denis Golovin > Fix For: 10.3.0.GA > > > Current implementation shows errors and warning under item selected for installation. > See confirmation page error message for virtualbox Installer [here|https://github.com/redhat-developer-tooling/developer-platform-insta...]. > Confirmation page controller should run Virtualization detection along with installed components detection and show warning under virtualbox item if it is detected or selected for install. > If Virtualization firmware status cannot be detected (windows 7) message should say: > * Make sure hardware virtualization is enabled on your platform if supported to improve performance. > if Hardware Virtualization is Disabled: > * Please enable hardware virtualization for your platform to improve performance > If Hardware Virtualization is Enabled, no message is required. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBTIS-1046) JBT 4.5.0 Oxygen JBTIS TP

by Paul Leacu (JIRA)

Paul Leacu created JBTIS-1046: --------------------------------- Summary: JBT 4.5.0 Oxygen JBTIS TP Key: JBTIS-1046 URL: https://issues.jboss.org/browse/JBTIS-1046 Project: JBoss Tools Integration Stack Issue Type: Task Components: target-platform Affects Versions: 4.5.0.AM1-TP Reporter: Paul Leacu Assignee: Paul Leacu *Reason:* Sync with Eclipse Oxygen AM JBT core and JBT TP *Project page/sources: * *Version:* 4.5.0.AM1 *License and owner:* EPL *Original p2 repo:* *JBoss mirror: * *Include Sources:* Yes *Affected JBoss Tools components: *.DevstudioIS *Include in JBDS:* Yes (IS) *Type of dependency:* distribution *List of bundles added/removed:* -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (ERT-480) JSDT stops breakpoints from working in C/C++ editors when CDT is installed [EBZ#511114]

by Victor Rubezhny (JIRA)

[ https://issues.jboss.org/browse/ERT-480?page=com.atlassian.jira.plugin.sy... ] Victor Rubezhny resolved ERT-480. --------------------------------- Fix Version/s: Neon.3 (4.6) Resolution: Done > JSDT stops breakpoints from working in C/C++ editors when CDT is installed [EBZ#511114] > --------------------------------------------------------------------------------------- > > Key: ERT-480 > URL: https://issues.jboss.org/browse/ERT-480 > Project: Eclipse Release Train > Issue Type: Task > Components: JSDT > Reporter: Friendly Jira Robot > Assignee: Victor Rubezhny > Labels: Debug, bzira > Fix For: Neon.3 (4.6) > > > If you install CDT into an Eclipse containing Webtools or vice-versa then breakpoints stop working out-of-the-box in C/C++ code editors. > Reproduction steps: > 1. Download JEE distribution: eclipse-jee-neon-2-linux-gtk-x86_64.tar.gz > 2. Add the Neon CDT update site: http://download.eclipse.org/tools/cdt/releases/9.2 and install all "Main" and "Optional" features > 3. Create a new C project --> "Hello World ANSI C Project" > 4. Try to add breakpoint anywhere in the C file editor: (CTRL+SHIFT+B or from the main menu) > 5. Notice you can't add a C breakpoint > Workaround: > 1. Instead you have to switch breakpoint types by going to "Run" menu --> "Breakpoint Types" --> "C/C++ Breakpoints" > 2. Breakpoints can now be added as normal and as expected > I don't expect the default breakpoint type to be incorrect for C/C++ editors when I have JSDT installed. This only fails when CDT and JSDT are installed at the same time. > Quick brain dump of my understanding of the problem so far: > 1. There is a kind of JavaScript breakpoint adaptor factory registered by webtools JSDT that is too unrestricted in the kinds of editors to which it applies. It applies itself to all text editors, regardless of content and then at a later point checks the extension of the file open in the editor (this is at odds other implementations I've looked at, which register themselves for specific editor types.) > 2. The Eclipse debugging framework may be a bit sloppy checking whether a breakpoint adaptor exists for a given adaptable -- from reading the code, the adaptor manager method that is used seems to only go as far as checking to see if there is an adaptor factory available instead actually attempting to get an adaptor from the factory. This is problematic because the factory available for all editors, but it only returns an adaptor conditionally on the extension of the open file. This may be misleading the "toggle breakpoint" action into thinking it can apply a JavaScript breakpoint when it actually can't. > I will attach a patch that that restricts the problematic breakpoint adaptor factory to javascript editors. This fixes the problem for my use-case above. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-23636) Update supported configuration docs / test plans / platforms for jbosstools 4.4.3 / devstudio 10.3

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23636?page=com.atlassian.jira.plugi... ] Nick Boldt commented on JBIDE-23636: ------------------------------------ Current status: more things have been fixed in Neon.3 and Oxygen.0.M5, so we might be in a better place for devstudio 10.4 and 11.0. I don't have all the details here as I'm not actively working with F25 or using Wayland. You want Leo Ufimtsev <lufimtse(a)redhat.com> or [~akurtako] for that. Current workaround for using F25: https://issues.jboss.org/browse/JBDS-4204 > Update supported configuration docs / test plans / platforms for jbosstools 4.4.3 / devstudio 10.3 > -------------------------------------------------------------------------------------------------- > > Key: JBIDE-23636 > URL: https://issues.jboss.org/browse/JBIDE-23636 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build > Affects Versions: 4.4.2.Final > Reporter: Nick Boldt > Assignee: Josef Kopriva > Labels: releasework > Fix For: 4.4.3.Final > > > It's time to review the available platforms on which we test devstudio / jbt. > Ubuntu: > We will probably want 16.04.1 LTS and 16.10, but should check https://wiki.ubuntu.com/Releases > Fedora: > We will want to support Fedora 24 and 25, but 25 currently has some issues with Wayland - JBDS-4204 among others. > Here's the support matrix document: > https://access.redhat.com/documentation/en/red-hat-jboss-developer-studio... -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-23965) externalize variable for filemgmt.jboss.org so it can be swapped for IP (performance improvement)

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23965?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-23965: ------------------------------- Fix Version/s: 4.4.3.Final > externalize variable for filemgmt.jboss.org so it can be swapped for IP (performance improvement) > ------------------------------------------------------------------------------------------------- > > Key: JBIDE-23965 > URL: https://issues.jboss.org/browse/JBIDE-23965 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build > Affects Versions: 4.4.3.Final > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 4.4.3.Final, 4.4.4.AM1, 4.5.0.AM1 > > > Recently, filemgmt moved IP addresses and any hardcoded refs to the old place are taking FOREVER to write files. So we need to parameterize this... or go back to using the domain name. But either way, this shouldn't be hardcoded in places like this: > https://github.com/jbosstools/jbosstools-build-sites/blob/master/aggregat... > So the variable ought to be moved into the parent pom for global and local override options. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-23965) externalize variable for filemgmt.jboss.org so it can be swapped for IP (performance improvement)

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23965?page=com.atlassian.jira.plugi... ] Nick Boldt commented on JBIDE-23965: ------------------------------------ new variable added to parent pom in 4.4.3.x, 4.4.x, master branches. https://github.com/jbosstools/jbosstools-build/commit/1715a7b3330a89b623d... https://github.com/jbosstools/jbosstools-build/commit/17c1d1fd3f06785d540... https://github.com/jbosstools/jbosstools-build/commit/b0a7081a21846c29dc0... https://github.com/jbosstools/jbosstools-build-sites/commit/2f961b074b7da... https://github.com/jbosstools/jbosstools-build-sites/commit/a2c010a8cb00e... https://github.com/jbosstools/jbosstools-build-sites/commit/a18246ec97cc2... https://github.com/jbdevstudio/jbdevstudio-product/commit/db978bcacbf961d... https://github.com/jbdevstudio/jbdevstudio-product/commit/a5b982d88551f4c... https://github.com/jbdevstudio/jbdevstudio-product/commit/c29b26a680c05b1... > externalize variable for filemgmt.jboss.org so it can be swapped for IP (performance improvement) > ------------------------------------------------------------------------------------------------- > > Key: JBIDE-23965 > URL: https://issues.jboss.org/browse/JBIDE-23965 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build > Affects Versions: 4.4.3.Final > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 4.4.4.AM1, 4.5.0.AM1 > > > Recently, filemgmt moved IP addresses and any hardcoded refs to the old place are taking FOREVER to write files. So we need to parameterize this... or go back to using the domain name. But either way, this shouldn't be hardcoded in places like this: > https://github.com/jbosstools/jbosstools-build-sites/blob/master/aggregat... > So the variable ought to be moved into the parent pom for global and local override options. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-23731) Integration tests: move hibernate integration tests to jbosstools/jbosstools-hibernate repo

by Dmitrii Bocharov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23731?page=com.atlassian.jira.plugi... ] Dmitrii Bocharov updated JBIDE-23731: ------------------------------------- Sprint: devex #128 February 2018 (was: devex #127 February 2017) > Integration tests: move hibernate integration tests to jbosstools/jbosstools-hibernate repo > ------------------------------------------------------------------------------------------- > > Key: JBIDE-23731 > URL: https://issues.jboss.org/browse/JBIDE-23731 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: central, integration-tests > Affects Versions: 4.4.2.Final > Reporter: Dmitrii Bocharov > Assignee: Dmitrii Bocharov > Fix For: 4.4.4.AM1 > > -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-23136) Deploy Docker Wizard: Pushing image to CDK registry results in an image with no tag

by Dmitrii Bocharov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23136?page=com.atlassian.jira.plugi... ] Dmitrii Bocharov updated JBIDE-23136: ------------------------------------- Sprint: devex #123 November 2016, devex #128 February 2018 (was: devex #123 November 2016, devex #127 February 2017) > Deploy Docker Wizard: Pushing image to CDK registry results in an image with no tag > ----------------------------------------------------------------------------------- > > Key: JBIDE-23136 > URL: https://issues.jboss.org/browse/JBIDE-23136 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.4.1.Final > Reporter: Marián Labuda > Assignee: Dmitrii Bocharov > Labels: deploy_docker_wizard, openshift_v3 > Fix For: 4.4.3.Final > > Attachments: FedoraImageStream.png, ImagesWithDigest.png, eap64-basic-s2i-new-app-from-cli-1.png, eap64-basic-s2i-new-app-from-jbosstools-1.png, local-docker-images-after-pull-1.png > > > I have a docker connection to local docker daemon and a CDK docker connection. I am pushing an image from a docker connection to CDK registry via Deploy Image to OpenShift wizard. Push of an image pass, but it results into an image with no tag, see: > 172.30.192.49:5000/msa/msa <none> 238200ae067d 4 months ago 1.05 GB > Such images are not shown in docker explorer under a docker connection because of upstream bug ERT-411 > Steps to reproduce: > - have a project with a file named {{Dockerfile}} with the following content (1 line): > {code} > FROM fedora:latest > {code} > - Select the file in the project explorer, then {{Run As > Docker Image Build}}. Use the CDK connection and give it a name (eg: {{username/fedora}}) > - Select the image in the Docker Explorer view, then {{Deploy to OpenShift}}. > - In the wizard, select the option to push the image to the registry (add a dummy port if needed) > - once the operation completed, there's an unexpected image named like {{172.30.164.33:5000/<project>/fedora}} in the output of the {{docker images}} command (in CLI) -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-23494) Tests: Should provide unit-tests for WatchManager

by Dmitrii Bocharov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23494?page=com.atlassian.jira.plugi... ] Dmitrii Bocharov updated JBIDE-23494: ------------------------------------- Sprint: devex #128 February 2018 > Tests: Should provide unit-tests for WatchManager > ------------------------------------------------- > > Key: JBIDE-23494 > URL: https://issues.jboss.org/browse/JBIDE-23494 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.4.2.AM3 > Reporter: Andre Dietisheim > Assignee: Dmitrii Bocharov > Priority: Critical > Fix For: 4.5.0.AM1 > > > WatchManager proved to be a complex and sensitive component and thus it is highly required to have unit-tests for it. I'll jira -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 1 month

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 2017