December 2016 - jbosstools-issues

[JBoss JIRA] (JBDS-4130) Environment variables are duplicated after several installations

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBDS-4130?page=com.atlassian.jira.plugin.... ] Denis Golovin updated JBDS-4130: -------------------------------- Description: Installer does not perform any checks at the moment before setting PATH environment variable. This issue affects only windows installer. > Environment variables are duplicated after several installations > ---------------------------------------------------------------- > > Key: JBDS-4130 > URL: https://issues.jboss.org/browse/JBDS-4130 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Bug > Components: platform-installer > Affects Versions: 10.1.0.GA > Environment: Windows > Reporter: Aurélien Pupier > Assignee: Denis Golovin > Fix For: 10.3.0.AM1 > > Attachments: screenshot-1.png > > > Installer does not perform any checks at the moment before setting PATH environment variable. This issue affects only windows installer. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBDS-4130) Environment variables are duplicated after several installations

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBDS-4130?page=com.atlassian.jira.plugin.... ] Denis Golovin updated JBDS-4130: -------------------------------- Environment: Windows > Environment variables are duplicated after several installations > ---------------------------------------------------------------- > > Key: JBDS-4130 > URL: https://issues.jboss.org/browse/JBDS-4130 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Bug > Components: platform-installer > Affects Versions: 10.1.0.GA > Environment: Windows > Reporter: Aurélien Pupier > Assignee: Denis Golovin > Fix For: 10.3.0.AM1 > > Attachments: screenshot-1.png > > -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18743) write tests for download.jboss.org & devstudio.redhat.com xmlunit test cases; validate composite*.xml; *.properties validation -- check if all properties are defined (avoid boss.* vs. jboss.*)

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18743?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-18743: ------------------------------- Sprint: devex #125 December 2017 > write tests for download.jboss.org & devstudio.redhat.com xmlunit test cases; validate composite*.xml; *.properties validation -- check if all properties are defined (avoid boss.* vs. jboss.*) > ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ > > Key: JBIDE-18743 > URL: https://issues.jboss.org/browse/JBIDE-18743 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: build > Affects Versions: 4.2.0.Final > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 4.4.3.AM2 > > > We need to write tests for download.jboss.org & devstudio.redhat.com: > * xmlunit test cases > ** validate composite*.xml > ** unit testing for discovery plugin.xml, update site category.xml (avoid bad URLs like 8.0-staging in a milestone release) > * other test cases > ** \*.properties validation -- check if all properties are defined (avoid boss.* vs. jboss.*) -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18743) write tests for download.jboss.org & devstudio.redhat.com xmlunit test cases; validate composite*.xml; *.properties validation -- check if all properties are defined (avoid boss.* vs. jboss.*)

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18743?page=com.atlassian.jira.plugi... ] Nick Boldt reassigned JBIDE-18743: ---------------------------------- Assignee: Nick Boldt > write tests for download.jboss.org & devstudio.redhat.com xmlunit test cases; validate composite*.xml; *.properties validation -- check if all properties are defined (avoid boss.* vs. jboss.*) > ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ > > Key: JBIDE-18743 > URL: https://issues.jboss.org/browse/JBIDE-18743 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: build > Affects Versions: 4.2.0.Final > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 4.4.3.AM2 > > > We need to write tests for download.jboss.org & devstudio.redhat.com: > * xmlunit test cases > ** validate composite*.xml > ** unit testing for discovery plugin.xml, update site category.xml (avoid bad URLs like 8.0-staging in a milestone release) > * other test cases > ** \*.properties validation -- check if all properties are defined (avoid boss.* vs. jboss.*) -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18743) write tests for download.jboss.org & devstudio.redhat.com xmlunit test cases; validate composite*.xml; *.properties validation -- check if all properties are defined (avoid boss.* vs. jboss.*)

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18743?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-18743: ------------------------------- Fix Version/s: 4.4.3.AM2 (was: 4.4.x) > write tests for download.jboss.org & devstudio.redhat.com xmlunit test cases; validate composite*.xml; *.properties validation -- check if all properties are defined (avoid boss.* vs. jboss.*) > ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------ > > Key: JBIDE-18743 > URL: https://issues.jboss.org/browse/JBIDE-18743 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: build > Affects Versions: 4.2.0.Final > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 4.4.3.AM2 > > > We need to write tests for download.jboss.org & devstudio.redhat.com: > * xmlunit test cases > ** validate composite*.xml > ** unit testing for discovery plugin.xml, update site category.xml (avoid bad URLs like 8.0-staging in a milestone release) > * other test cases > ** \*.properties validation -- check if all properties are defined (avoid boss.* vs. jboss.*) -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18848) setup tests for ide-config.properties

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18848?page=com.atlassian.jira.plugi... ] Nick Boldt commented on JBIDE-18848: ------------------------------------ Three verification tests added to the generator that creates ide-config.properties: * check for duplicate entries so we don't get people downloading from staging or snapshots when we mean dev or stable * check that there are exactly 8 keys defined for a given version - no more, no less. * check that if we're doing a stable release, all entries with .Final or .GA are commented out, as stable releases use shorter keys (eg., 4.4 or 10, rather than 4.4.2.Final or 10.2.0.GA) https://github.com/jbosstools/jbosstools-download.jboss.org/commits/master > setup tests for ide-config.properties > ------------------------------------- > > Key: JBIDE-18848 > URL: https://issues.jboss.org/browse/JBIDE-18848 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: build, common > Reporter: Max Rydahl Andersen > Assignee: Nick Boldt > Labels: releasework > Fix For: 4.4.2.Final > > > JBIDE-18837 and other jiras showed that ide-config.properties risk having errors introduced into it. > we should have a test that runs every day to check if it is still consistent. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBDS-4112) create verification test to ensure that we never point a GA release at snapshot or staging URLs in ide-config.properties

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBDS-4112?page=com.atlassian.jira.plugin.... ] Nick Boldt commented on JBDS-4112: ---------------------------------- Test added to generator for ide-config.properties so that an error is thrown if we're doing a stable release and any uncommented lines are found with .Final or .GA (since a stable release should use 4.4 or 10, not 4.4.2.Final or 10.2.0.GA). https://github.com/jbosstools/jbosstools-download.jboss.org/commit/cd4a2b... > create verification test to ensure that we never point a GA release at snapshot or staging URLs in ide-config.properties > ------------------------------------------------------------------------------------------------------------------------ > > Key: JBDS-4112 > URL: https://issues.jboss.org/browse/JBDS-4112 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Bug > Components: build > Affects Versions: 10.1.0.GA, 10.2.0.AM1 > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 10.2.0.GA > > > As reported in https://developer.jboss.org/message/964029#964029 it seems there may have been a situation where a user installed devstudio 10.1.0.GA from the installer jar, but then using Central got the staging/snapshot URLs into their Available Update Sites, which then caused them to be prompted to update to 10.2. > Mixing an AM1 staging build into a .GA stable build should not happen. > We need a better test/check to ensure that if GA is live, its ide-config.properties content NEVER points to the future snapshot/staging content. > This testing could be part of the staging/release guide, but could also be run as a Jenkins job to check at intervals: > * ide-config.properties: URLs exist, are valid, don't 404, don't mismatch content > * foundation plugin / devstudio version plugin have correct version (eg., can't still be GA after GA is live) - see https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevS... job -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBDS-4159) On Windows, the installer need to choose the correct CDK version depending if Hyper-V is activated or not

by Aileen Cunningham (JIRA)

[ https://issues.jboss.org/browse/JBDS-4159?page=com.atlassian.jira.plugin.... ] Aileen Cunningham commented on JBDS-4159: ----------------------------------------- [~dgolovin] This has been highlighted as a usability issue for Fuse Integration Services as when users do hit this issues it takes time to figure out what went wrong. Is this something you can look at for next release of the Installer? > On Windows, the installer need to choose the correct CDK version depending if Hyper-V is activated or not > --------------------------------------------------------------------------------------------------------- > > Key: JBDS-4159 > URL: https://issues.jboss.org/browse/JBDS-4159 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Feature Request > Components: platform-installer > Affects Versions: 1.1.0.GA > Reporter: Aurélien Pupier > Assignee: Denis Golovin > Priority: Blocker > > On windows, the latest version of Docker is using Hyper-V and no more VirtualBox. The current embedded CDK is expecting Docker in a Virtualbox. The installer should handle both cases. > here is the error: > {noformat} > Bringing machine 'default' up with 'virtualbox' provider... > ==> default: Importing base box 'cdkv2'... > ==> default: Matching MAC address for NAT networking... > ==> default: Setting the name of the VM: rhel-ose_default_1478167717348_52569 > ==> default: Clearing any previously set network interfaces... > ==> default: Preparing network interfaces based on configuration... > default: Adapter 1: nat > default: Adapter 2: hostonly > ==> default: Forwarding ports... > default: 22 (guest) => 2222 (host) (adapter 1) > ==> default: Running 'pre-boot' VM customizations... > ==> default: Booting VM... > There was an error while executing `VBoxManage`, a CLI used by Vagrant > for controlling VirtualBox. The command and stderr is shown below. > Command: ["startvm", "27ab7252-7971-4276-abec-1aba54965c62", "--type", "headless"] > Stderr: VBoxManage.exe: error: VT-x is not available (VERR_VMX_NO_VMX) > VBoxManage.exe: error: Details: code E_FAIL (0x80004005), component ConsoleWrap, interface IConsole > {noformat} -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBTIS-1002) Progress bar still indicates that the installation is in progress even if it is done

by Paul Leacu (JIRA)

[ https://issues.jboss.org/browse/JBTIS-1002?page=com.atlassian.jira.plugin... ] Paul Leacu commented on JBTIS-1002: ----------------------------------- [~apodhrad] - please download http://download.jboss.org/jbosstools/neon/staging/updates/integration-sta... and retest - see !inst-proc2.png|thumbnail! - I'm not seeing the next button enabled prematurely. > Progress bar still indicates that the installation is in progress even if it is done > ------------------------------------------------------------------------------------ > > Key: JBTIS-1002 > URL: https://issues.jboss.org/browse/JBTIS-1002 > Project: JBoss Tools Integration Stack > Issue Type: Bug > Components: distribution > Environment: devstudio-is-fuse-runtime-installer-10.1.1-SNAPSHOT.jar > Reporter: Andrej Podhradsky > Assignee: Paul Leacu > Attachments: inst-proc2.png, installer_progress.png > > > Progress bar still indicates that the installation is in progress even if it is done. Please see the attached screenshot and notice that the button 'Next' is enabled (the installation is done). -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBTIS-1002) Progress bar still indicates that the installation is in progress even if it is done

by Paul Leacu (JIRA)

[ https://issues.jboss.org/browse/JBTIS-1002?page=com.atlassian.jira.plugin... ] Paul Leacu updated JBTIS-1002: ------------------------------ Attachment: inst-proc2.png > Progress bar still indicates that the installation is in progress even if it is done > ------------------------------------------------------------------------------------ > > Key: JBTIS-1002 > URL: https://issues.jboss.org/browse/JBTIS-1002 > Project: JBoss Tools Integration Stack > Issue Type: Bug > Components: distribution > Environment: devstudio-is-fuse-runtime-installer-10.1.1-SNAPSHOT.jar > Reporter: Andrej Podhradsky > Assignee: Paul Leacu > Attachments: inst-proc2.png, installer_progress.png > > > Progress bar still indicates that the installation is in progress even if it is done. Please see the attached screenshot and notice that the button 'Next' is enabled (the installation is done). -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 4 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 December 2016