September 2016 - jbosstools-issues

[JBoss JIRA] (JBDS-4047) Uninstaller does not clean up Path

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBDS-4047?page=com.atlassian.jira.plugin.... ] Denis Golovin updated JBDS-4047: -------------------------------- Story Points: 3 > Uninstaller does not clean up Path > ---------------------------------- > > Key: JBDS-4047 > URL: https://issues.jboss.org/browse/JBDS-4047 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Bug > Components: platform-installer > Affects Versions: 10.1.0.GA > Reporter: Jan Richter > Assignee: Denis Golovin > > After running the uninstall script all the PATH entries pointing to the devsuite install folder remain untouched. My guess is the actual folder these entries are compared to is not the root install folder, but the uninstall one. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBDS-4047) Uninstaller does not clean up Path

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBDS-4047?page=com.atlassian.jira.plugin.... ] Denis Golovin updated JBDS-4047: -------------------------------- Sprint: devex #120 September 2016 > Uninstaller does not clean up Path > ---------------------------------- > > Key: JBDS-4047 > URL: https://issues.jboss.org/browse/JBDS-4047 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Bug > Components: platform-installer > Affects Versions: 10.1.0.GA > Reporter: Jan Richter > Assignee: Denis Golovin > > After running the uninstall script all the PATH entries pointing to the devsuite install folder remain untouched. My guess is the actual folder these entries are compared to is not the root install folder, but the uninstall one. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBDS-4059) RPM errors: Installing rh-eclipse46-devstudio.10.1 into rh-eclipse46 beta.

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBDS-4059?page=com.atlassian.jira.plugin.... ] Nick Boldt commented on JBDS-4059: ---------------------------------- PR applied. Now the rpm causes a few extra dependencies to be installed when I `yum install` the latest RPM [1]: {code} Dependencies resolved. =========================================================================== Package Arch Version Repository Size =========================================================================== Installing: ORBit2 x86_64 2.14.19-15.fc24 fedora 179 k libIDL x86_64 0.8.14-11.fc24 fedora 89 k ... rh-eclipse46-devstudio x86_64 10.2-0.20160927.2139.el7 ... {code} [1] https://devstudio.jboss.com/10.0/snapshots/builds/devstudio.rpm_master/20... > RPM errors: Installing rh-eclipse46-devstudio.10.1 into rh-eclipse46 beta. > -------------------------------------------------------------------------- > > Key: JBDS-4059 > URL: https://issues.jboss.org/browse/JBDS-4059 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Bug > Components: build > Reporter: Pavol Srna > Assignee: Nick Boldt > > [~vkadlcik] has run some rpm sanity tests. The findings can be seen here: http://nest.test.redhat.com/mnt/qa/scratch/bkr-hv03-guest19/2016:24366/tp... > [~nickboldt] can you please investigate? Thanks! -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-17022) Show in Console does not work for remote servers

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-17022?page=com.atlassian.jira.plugi... ] Rob Stryker updated JBIDE-17022: -------------------------------- Sprint: devex #121 October 2016 > Show in Console does not work for remote servers > ------------------------------------------------ > > Key: JBIDE-17022 > URL: https://issues.jboss.org/browse/JBIDE-17022 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: server, upstream > Affects Versions: 4.2.0.Beta1 > Environment: JBDS 8.0.0.Beta1a B82 > Reporter: Martin Malina > Assignee: Rob Stryker > Fix For: 4.4.2.AM2 > > > When you have a remote server running and select Show In on the server, you can see the Console item is greyed out and cannot be clicked. > This is because of an upstream bug - unused items should be removed so we can add our working Console item. > So this JIRA is both to track the upstream bug and once that is fixed, we can fix this on our end. > Upstream bugzilla is here: https://bugs.eclipse.org/bugs/show_bug.cgi?id=431910 -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-17022) Show in Console does not work for remote servers

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-17022?page=com.atlassian.jira.plugi... ] Rob Stryker updated JBIDE-17022: -------------------------------- Fix Version/s: 4.4.2.AM2 (was: 4.2.x) > Show in Console does not work for remote servers > ------------------------------------------------ > > Key: JBIDE-17022 > URL: https://issues.jboss.org/browse/JBIDE-17022 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: server, upstream > Affects Versions: 4.2.0.Beta1 > Environment: JBDS 8.0.0.Beta1a B82 > Reporter: Martin Malina > Assignee: Rob Stryker > Fix For: 4.4.2.AM2 > > > When you have a remote server running and select Show In on the server, you can see the Console item is greyed out and cannot be clicked. > This is because of an upstream bug - unused items should be removed so we can add our working Console item. > So this JIRA is both to track the upstream bug and once that is fixed, we can fix this on our end. > Upstream bugzilla is here: https://bugs.eclipse.org/bugs/show_bug.cgi?id=431910 -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23157) rename component "common/jst/core" to "base" or "foundation" or add new components

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23157?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-23157: ------------------------------- Component/s: foundation jst (was: runtime-detection) > rename component "common/jst/core" to "base" or "foundation" or add new components > ---------------------------------------------------------------------------------- > > Key: JBIDE-23157 > URL: https://issues.jboss.org/browse/JBIDE-23157 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: common, foundation, jst > Affects Versions: 4.4.2.AM1 > Reporter: Nick Boldt > Assignee: Alexey Kazakov > Fix For: 4.4.2.AM2 > > > The closest thing to a "Base" component, or a "Foundation" component (eg., when reporting issues like JBIDE-23156) is "common/jst/core" which is nothing like "Base" or "Foundation". > We should either fix that component, or add new one(s). > This will impact *.py scripts in jbosstools-build-ci. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23157) rename component "common/jst/core" to "base" or "foundation" or add new components

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23157?page=com.atlassian.jira.plugi... ] Nick Boldt commented on JBIDE-23157: ------------------------------------ OK, I've... * created JBIDE > foundation (Rob as owner) * created JBDS > foundation (Rob as owner) * created JBIDE > jst (Alexey as owner) * created JBDS > jst (Alexey as owner) * renamed JBIDE > common/jst/core to common (and updated description: "Issues related to https://github.com/jbosstools/jbosstools-base/tree/master/common. For jst issues, see jst component. For core, see foundation component") (Alexey as owner) * created JBDS > common (with description: "Issues related to https://github.com/jbosstools/jbosstools-base/tree/master/common. For jst issues, see jst component. For core, see foundation component") (Alexey as owner) Next up, testing my PR and applying it. > rename component "common/jst/core" to "base" or "foundation" or add new components > ---------------------------------------------------------------------------------- > > Key: JBIDE-23157 > URL: https://issues.jboss.org/browse/JBIDE-23157 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: common, runtime-detection > Affects Versions: 4.4.2.AM1 > Reporter: Nick Boldt > Assignee: Alexey Kazakov > Fix For: 4.4.2.AM2 > > > The closest thing to a "Base" component, or a "Foundation" component (eg., when reporting issues like JBIDE-23156) is "common/jst/core" which is nothing like "Base" or "Foundation". > We should either fix that component, or add new one(s). > This will impact *.py scripts in jbosstools-build-ci. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBDS-4065) DevStudio 1.1 Installer unfriendly when 1.0 present

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBDS-4065?page=com.atlassian.jira.plugin.... ] Denis Golovin commented on JBDS-4065: ------------------------------------- [~rick_wagner] have you used the same eclipse workspace left after previous DevStudio? I guess you were using default one %USERPROFILE%\workspace. > DevStudio 1.1 Installer unfriendly when 1.0 present > --------------------------------------------------- > > Key: JBDS-4065 > URL: https://issues.jboss.org/browse/JBDS-4065 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Bug > Components: cdk, platform-installer > Affects Versions: 10.1.0.GA > Environment: Windows 10, DevSuite Installer 1.0 had been run > Reporter: Rick Wagner > Assignee: Rob Stryker > > When running the DevSuite 1.1 installer, DevStudio is not connected to the installed CDK. > Observations: > - All components removed before installation, does not help. (VirtualBox and Vagrant using Add/Remove programs, everything else directory-deleted, Environment variables cleaned). > - DevStudio says it can't start the Container Development Environment server. ('Failed to find Vagrant!' reads the error). If I open Launch Configuration, it lists the Main as "C:\HashiCorp\Vagrant\bin\vagrant.exe", which is not in the installation directory. > - It was noted that DevStudio marked itself 'completed' before Vagrant was installed. How does DevStudio know where Vagrant is? > - It's noted that DevStudio 'remembers' user settings (i.e. CDK registration user/password) from previous attempts. Where is this information kept? I must've missed something in cleanup. > - Tried full suite installation, then deleting DevStudio, then re-installing. (Hoping DevStudio would then find Vagrant in the right location, because it followed Vagrant's installation.) Result: No Container Development Environment server is present in 'server' view. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23269) Cannot use backspace when entering text in Terminal (e.g. during cdk launch) on Mac

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23269?page=com.atlassian.jira.plugi... ] Rob Stryker updated JBIDE-23269: -------------------------------- Component/s: upstream > Cannot use backspace when entering text in Terminal (e.g. during cdk launch) on Mac > ----------------------------------------------------------------------------------- > > Key: JBIDE-23269 > URL: https://issues.jboss.org/browse/JBIDE-23269 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: cdk, upstream > Affects Versions: 4.4.2.AM1 > Reporter: Martin Malina > Assignee: Rob Stryker > Attachments: tm-backspace.png > > > Today I tried to disable the SUB_USERNAME variable in cdk launch config so that I can check if entering input into Terminal view works correctly. > I made a typo and it turns out that pressing backspace prints out ^H. > !tm-backspace.png! > This happens on Mac. On Windows it works correctly. I haven't checked linux. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23269) Cannot use backspace when entering text in Terminal (e.g. during cdk launch) on Mac

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23269?page=com.atlassian.jira.plugi... ] Rob Stryker commented on JBIDE-23269: ------------------------------------- I spent an hour or two looking into this. It seems that even when opening a raw terminal (ie not one i make via API), backspace and stuff work fine when the terminal opens, and stop working once in vagrant. So... that's awesome. I also tried switching our opening from streamsConnector (let the view connect to some streams) to ProcessConnector, but that didn't result in anything good. It's possible we may need to do it in the future, but so far I've pinged Martin Oberhuber to see if he has any advice. > Cannot use backspace when entering text in Terminal (e.g. during cdk launch) on Mac > ----------------------------------------------------------------------------------- > > Key: JBIDE-23269 > URL: https://issues.jboss.org/browse/JBIDE-23269 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: cdk > Affects Versions: 4.4.2.AM1 > Reporter: Martin Malina > Assignee: Rob Stryker > Attachments: tm-backspace.png > > > Today I tried to disable the SUB_USERNAME variable in cdk launch config so that I can check if entering input into Terminal view works correctly. > I made a typo and it turns out that pressing backspace prints out ^H. > !tm-backspace.png! > This happens on Mac. On Windows it works correctly. I haven't checked linux. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 6 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 September 2016