October 2016 - jbosstools-issues - Jboss List Archives

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

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBDS-3757?page=com.atlassian.jira.plugin.... ] Nick Boldt updated JBDS-3757: ----------------------------- Fix Version/s: 10.2.0.AM3 (was: 10.2.0.AM2) > 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.AM3 > > > 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-3798) Repeated component detection keeps stale values

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBDS-3798?page=com.atlassian.jira.plugin.... ] Nick Boldt updated JBDS-3798: ----------------------------- Fix Version/s: 10.2.0.AM3 (was: 10.2.0.AM2) > 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.AM3 > > 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 Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBDS-3701?page=com.atlassian.jira.plugin.... ] Nick Boldt updated JBDS-3701: ----------------------------- Fix Version/s: 10.2.0.AM3 (was: 10.2.0.AM2) > 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.AM3 > > > 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-3762) Add logging to configuration page for detection and configured items

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBDS-3762?page=com.atlassian.jira.plugin.... ] Nick Boldt updated JBDS-3762: ----------------------------- Fix Version/s: 10.2.0.AM3 (was: 10.2.0.AM2) > 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.AM3 > > > 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-3754) Installer: redirect links for Vagrant and VirtualBox should use https

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBDS-3754?page=com.atlassian.jira.plugin.... ] Nick Boldt updated JBDS-3754: ----------------------------- Fix Version/s: 10.2.0.AM3 (was: 10.2.0.AM2) > Installer: redirect links for Vagrant and VirtualBox should use https > --------------------------------------------------------------------- > > Key: JBDS-3754 > URL: https://issues.jboss.org/browse/JBDS-3754 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Enhancement > Components: platform-installer > Affects Versions: 9.1.0.CR1 > Reporter: Pavol Pitonak > Assignee: Denis Golovin > Priority: Blocker > Labels: havoc > Fix For: 10.2.0.AM3 > > > Installer's requirements.json file \[1] declares location of Vagrant and VirtualBox installers like these: > {code} > http://developers.redhat.com/redirect/to/vagrant-1.7.4.download > http://developers.redhat.com/redirect/to/virtualbox-5.0.8.download > {code} > They should use *https* scheme. > \[1] https://github.com/redhat-developer-tooling/developer-platform-install/bl... -- 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 Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBDS-3633?page=com.atlassian.jira.plugin.... ] Nick Boldt updated JBDS-3633: ----------------------------- Fix Version/s: 10.2.0.AM3 (was: 10.2.0.AM2) > 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.AM3 > > > 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-4087) Mark as invalid Vagrant versions known to be not working

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBDS-4087?page=com.atlassian.jira.plugin.... ] Nick Boldt updated JBDS-4087: ----------------------------- Fix Version/s: 10.2.0.AM3 (was: 10.2.0.AM2) > 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.AM3 > > > 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

[JBoss JIRA] (JBDS-4089) Skip unit/ui tests not related to current platform/arch

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBDS-4089?page=com.atlassian.jira.plugin.... ] Nick Boldt updated JBDS-4089: ----------------------------- Fix Version/s: 10.2.0.AM3 (was: 10.2.0.AM2) > Skip unit/ui tests not related to current platform/arch > ------------------------------------------------------- > > Key: JBDS-4089 > URL: https://issues.jboss.org/browse/JBDS-4089 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Task > Components: platform-installer > Affects Versions: 10.1.0.AM2 > Reporter: Denis Golovin > Fix For: 10.2.0.AM3 > > > Current UI tests are specific for windows. When installer supports Mac OS X there will be failures when UI tests are running on Mac. For example verification for Drive in selected path is valid only on Windows. > this.skip() call does not work for protractor tests, because it still considered as a failure. Second option would be do not run tests that are not valid for current platform at all. That could be done ether by direct check in tests like > {code} > if(process.platform === 'win32') { > it('test desctription', function(){ > // test instructions > }); > } > {code} > or we can move platform specific tests in files with platform specific suffix and include them using process.platform and process.arch values at gulp execution time. -- 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 Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBDS-4058?page=com.atlassian.jira.plugin.... ] Nick Boldt updated JBDS-4058: ----------------------------- Fix Version/s: 10.2.0.AM3 (was: 10.2.0.AM2) > 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.AM3 > > > 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-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 updated JBDS-4059: ----------------------------- Fix Version/s: 10.2.0.AM3 (was: 10.2.0.AM2) > 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 > Fix For: 10.2.0.AM3 > > > [~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, 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