October 2016 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-22773) Openshift server adapter can't start with eap64-basic-s2i template on Windows: can't copy MANIFEST.MF reported

by Jeff MAURY (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22773?page=com.atlassian.jira.plugi... ] Jeff MAURY commented on JBIDE-22773: ------------------------------------ Yes we should keep it open. My analysis is that error are caused when the workspace folder is not located under $HOME because permissions are not the same. We agreed a popup dialog warning of potential errors would be great. I just need to identify when it should popup > Openshift server adapter can't start with eap64-basic-s2i template on Windows: can't copy MANIFEST.MF reported > -------------------------------------------------------------------------------------------------------------- > > Key: JBIDE-22773 > URL: https://issues.jboss.org/browse/JBIDE-22773 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift, upstream > Affects Versions: 4.4.1.AM2 > Reporter: Jeff MAURY > Assignee: Jeff MAURY > Labels: server > Fix For: 4.4.2.AM2 > > Attachments: screenshot-1.png > > > When starting the Openshift server adapter created from the eap64-basic-s2i template, the rsync phase reports the following error: > [^screenshot-1.png] -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3633) Uninstaller does nothing

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBDS-3633?page=com.atlassian.jira.plugin.... ] Denis Golovin updated JBDS-3633: -------------------------------- Sprint: devex #122 October 2016 (was: devex #121 October 2016) > Uninstaller does nothing > ------------------------ > > Key: JBDS-3633 > URL: https://issues.jboss.org/browse/JBDS-3633 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Feature Request > Components: platform-installer > Reporter: Denis Golovin > Assignee: Denis Golovin > Labels: havoc > Fix For: 10.2.0.AM2 > > > Current implementation just removes record about installation from windows registry. > What it should do: > 1. Remove virtual box from vagrant: > {code}vagrant box remove cdkv2{code} > 2. Remove virtual machine from virtual box > {code}vboxmanage --unregister ${vmname}{code} > 3. Uninstall what was installed: > vargant > virtual box > developer studio > 4. Delete: > CDK > Open JDK 8 > 5. Cleanup PATH env variable -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3762) Add logging to configuration page for detection and configured items

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBDS-3762?page=com.atlassian.jira.plugin.... ] Denis Golovin updated JBDS-3762: -------------------------------- Sprint: devex #122 October 2016 (was: devex #121 October 2016) > Add logging to configuration page for detection and configured items > -------------------------------------------------------------------- > > Key: JBDS-3762 > URL: https://issues.jboss.org/browse/JBDS-3762 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Enhancement > Components: platform-installer > Affects Versions: 9.1.0.GA > Reporter: Denis Golovin > Assignee: Denis Golovin > Labels: Havoc > Fix For: 10.2.0.AM2 > > > Log what was detected and selected on configuration page. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3757) Add some logging to setup routines

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBDS-3757?page=com.atlassian.jira.plugin.... ] Denis Golovin updated JBDS-3757: -------------------------------- Sprint: devex #122 October 2016 (was: devex #121 October 2016) > Add some logging to setup routines > ---------------------------------- > > Key: JBDS-3757 > URL: https://issues.jboss.org/browse/JBDS-3757 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Enhancement > Components: platform-installer > Affects Versions: 9.1.0.CR1 > Reporter: Jan Richter > Assignee: Denis Golovin > Labels: havoc > Fix For: 10.2.0.AM2 > > > We should log events in setup the same way we now do in download and install phases. For example when the install -> setup transition happens, when setup is fired for an already existing item. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3822) Disable the annoying "This program might not have installed correctly" on cancelation

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBDS-3822?page=com.atlassian.jira.plugin.... ] Denis Golovin updated JBDS-3822: -------------------------------- Sprint: devex #122 October 2016 (was: devex #121 October 2016) > Disable the annoying "This program might not have installed correctly" on cancelation > ------------------------------------------------------------------------------------- > > Key: JBDS-3822 > URL: https://issues.jboss.org/browse/JBDS-3822 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Enhancement > Components: platform-installer > Affects Versions: 9.1.0.CR1 > Reporter: Jan Richter > Assignee: Denis Golovin > Labels: havoc > Fix For: 10.2.0.AM2 > > Attachments: devsuite.manifest > > > Upon closing/cancelling the installer before going through the entire installation process, Windows will open a dialog saying "This program might not have installed correctly" and the user has to somehow confirm it. > This should be avoided by providing an application manifest that indicates support for certain Windows versions. > Docs here: > https://msdn.microsoft.com/en-us/library/dd371711%28VS.85%29.aspx -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBDS-4058) Installer does not validate VAGRANT_HOME when used

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBDS-4058?page=com.atlassian.jira.plugin.... ] Denis Golovin updated JBDS-4058: -------------------------------- Sprint: devex #122 October 2016 (was: devex #121 October 2016) > Installer does not validate VAGRANT_HOME when used > -------------------------------------------------- > > Key: JBDS-4058 > URL: https://issues.jboss.org/browse/JBDS-4058 > 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 > Fix For: 10.2.0.AM2 > > > As per JBDS-3838, we require users with space in their name to use VAGRANT_HOME environment variable. The problem is, the installer will let you proceed without validating the variable contents. > Something like "x:\this definitely has no spaces\" will allow the user to proceed with installation, which inevitably fails. We need to validate if the path stored in the variable is valid, that the selected drive actually exists, and that there are no spaces. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3798) Repeated component detection keeps stale values

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBDS-3798?page=com.atlassian.jira.plugin.... ] Denis Golovin updated JBDS-3798: -------------------------------- Sprint: devex #122 October 2016 (was: devex #121 October 2016) > Repeated component detection keeps stale values > ----------------------------------------------- > > Key: JBDS-3798 > URL: https://issues.jboss.org/browse/JBDS-3798 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Bug > Components: platform-installer > Affects Versions: 9.1.0.CR1 > Environment: Setup-bundled-0.0.2-20160413-107 > Reporter: Jan Richter > Assignee: Denis Golovin > Labels: ui > Fix For: 10.2.0.AM2 > > Attachments: screenshot-1.png > > > Installer detects existing tools on confirmation page. If after that a change happens (like the user uninstalls VirtualBox) and then the user goes to the previous page and to confirm page again - the change is correctly detected, but instead of replacing the old option, there are now both options for 'install' and 'use existing'. Plus the count of detected components stays the same. > Using the existing (no longer existing in fact) installation fails, naturally. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3701) Add check for an existing Java to find if it is JRE or JDK

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBDS-3701?page=com.atlassian.jira.plugin.... ] Denis Golovin updated JBDS-3701: -------------------------------- Sprint: devex #122 October 2016 (was: devex #121 October 2016) > Add check for an existing Java to find if it is JRE or JDK > ---------------------------------------------------------- > > Key: JBDS-3701 > URL: https://issues.jboss.org/browse/JBDS-3701 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Enhancement > Components: platform-installer > Affects Versions: 9.1.0.CR1 > Reporter: Jan Richter > Assignee: Denis Golovin > Labels: ui > Fix For: 10.2.0.AM2 > > > JBDS will run on both, but in order to develop something the user needs a JDK. The detection/selection will allow using JRE distribution of Java without even a warning. We should find out what kind of Java the user has selected and at least display a warning if it is not JDK (or just not allow JRE). -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBDS-4073) Install page should show only components selected for installation

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBDS-4073?page=com.atlassian.jira.plugin.... ] Denis Golovin reassigned JBDS-4073: ----------------------------------- Assignee: Denis Golovin > Install page should show only components selected for installation > ------------------------------------------------------------------ > > Key: JBDS-4073 > URL: https://issues.jboss.org/browse/JBDS-4073 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Enhancement > Components: platform-installer > Affects Versions: 10.2.0.AM2 > Reporter: Denis Golovin > Assignee: Denis Golovin > Fix For: 10.2.0.AM2 > > > If component not selected for installation installer should not even run setup part of it. If for example virtualbox/vagrant detected and CDK is selected for installation it is CDK setup responsibility to add vagrant to PATH. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 5 months

1
0
0 / 0

[JBoss JIRA] (JBDS-4087) Mark as invalid Vagrant versions known to be not working

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBDS-4087?page=com.atlassian.jira.plugin.... ] Denis Golovin updated JBDS-4087: -------------------------------- Sprint: (was: devex #121 October 2016) > Mark as invalid Vagrant versions known to be not working > -------------------------------------------------------- > > Key: JBDS-4087 > URL: https://issues.jboss.org/browse/JBDS-4087 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Enhancement > Components: platform-installer > Affects Versions: 1.1.0.GA > Reporter: Aurélien Pupier > Assignee: Denis Golovin > Fix For: 10.2.0.AM2 > > > Vagrant version superior to 1.8.4 are known to be non-working, please mark them as invalid during installation of the components isntead of saying that there is a newer version. > For my part there was no clue on what was the issue, i was based on the latest at the moment 1.8.6. > When using JBDS, I had a timeout when trying to launch the Container in Server view and the console starting the server was displaying no errors -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 5 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 October 2016