December 2016 - jbosstools-issues

[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: ----------------------------------------- Will the next release be CDK 3.0 based on minishift? > 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 > Fix For: 10.3.0.GA > > > 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, 3 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23587) Integration tests global refactoring: org.jboss.tools.maven.ui.bot.test

by Josef Kopriva (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23587?page=com.atlassian.jira.plugi... ] Josef Kopriva commented on JBIDE-23587: --------------------------------------- PRs are merged and verified. Can be closed [~dbocharov]? > Integration tests global refactoring: org.jboss.tools.maven.ui.bot.test > ----------------------------------------------------------------------- > > Key: JBIDE-23587 > URL: https://issues.jboss.org/browse/JBIDE-23587 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: maven > Affects Versions: 4.4.2.Final > Reporter: Jeff MAURY > Assignee: Dmitrii Bocharov > Labels: integration, integration_tests, maven > Fix For: 4.4.3.AM1 > > > Maven command from CLI: > {code} > mvn clean verify -Dtest.module=org.jboss.tools.maven.ui.bot.test -DskipTests=false > {code} > Launching in Eclipse needs the following parameters: > {code} > -Dusage_reporting_enabled=false -Drd.config=resources/servers -Djbosstools.test.seam.2.1.0.home=/home/dbocharo/jboss-seam/jboss-seam-2.1.2 -Djbosstools.test.seam.2.3.0.home=/home/dbocharo/jboss-seam/jboss-seam-2.3.0.CR1 -Djbosstools.test.seam.2.2.0.home=/home/dbocharo/jboss-seam/jboss-seam-2.2.0.GA -Djbosstools.test.wildfly8.home=/home/dbocharo/wildfly-8.2.1.Final -Dmaven.settings.path=/home/dbocharo/dev/openshift/jbosstools-integration-tests/tests/org.jboss.tools.maven.ui.bot.test/target/classes/usersettings/settings.xml > {code} > Corresponding directories must contain Seam and Wildfly -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22774) Create integration tests PR check job for aerogar-hybrid

by Pavol Srna (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22774?page=com.atlassian.jira.plugi... ] Pavol Srna updated JBIDE-22774: ------------------------------- Fix Version/s: 4.4.3.AM1 (was: 4.4.x) > Create integration tests PR check job for aerogar-hybrid > -------------------------------------------------------- > > Key: JBIDE-22774 > URL: https://issues.jboss.org/browse/JBIDE-22774 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: aerogear-hybrid, build, qa > Reporter: Rastislav Wagner > Assignee: Pavol Srna > Fix For: 4.4.3.AM1 > > -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBDS-4224) Include OpenJDK 1.8.0.111-3.b15 release into installer

by Denis Golovin (JIRA)

Denis Golovin created JBDS-4224: ----------------------------------- Summary: Include OpenJDK 1.8.0.111-3.b15 release into installer Key: JBDS-4224 URL: https://issues.jboss.org/browse/JBDS-4224 Project: Red Hat JBoss Developer Studio (devstudio) Issue Type: Task Components: platform-installer Affects Versions: 10.3.0.AM1 Reporter: Denis Golovin Assignee: Denis Golovin Fix For: 10.3.0.AM2 >From [~akashche]: Public download: https://developers.redhat.com/download-manager/file/java-1.8.0-openjdk-1.... sha256: d4fa67a45cef119325e9ef775ea53dee0e2754b2df511618f91abf5acda6ddf0 Notable changes that can affect DevSuite are: 1) MSI installer now includes Update Notifier utility. This utility is not installed by default. In installer UI form with installation directory chooser is changed, but should behave the same (jdk installed into default directory, notifier not installed) on default "Next" action. For silent install MSI now contains two named "installation features": "jdk" and "update_notifier". msiexec invocation without specifying features: msiexec /quiet /i jdk.msi should behave the same way if only jdk feature will be specified: msiexec /quiet /i jdk.msi ADDLOCAL=jdk INSTALLDIR variable also should continue to work. To install both jdk and update_notifier (that is probably not needed for DevSuite) the following can be used: msiexec /quiet /i jdk.msi ADDLOCAL=jdk,update_notifier 2) MSI installer size grew up to 103MB, that is mostly caused not by update_notifier (that is less than 5MB) but by inclusion of additional Java sources into src.zip bundle that is installed into jdk directory. Now debugging of all jdk-internal Java packages (sun.*, com.sun.*) should work in Eclipse. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 3 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 Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBDS-4159?page=com.atlassian.jira.plugin.... ] Denis Golovin commented on JBDS-4159: ------------------------------------- [~aileenc] this should be fixed with next CDK release, approximately within next 6 weeks. For Windows 10 Pro Hyper-V would be selected by default if enabled for other windows platforms virtualbox will stay as a requirement. VM image is going to be the same for virtualbox and Hyper-V setup and bundled installer is not going to be roughly the same size as it is right now. > 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 > Fix For: 10.3.0.GA > > > 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, 3 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 Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBDS-4159?page=com.atlassian.jira.plugin.... ] Denis Golovin updated JBDS-4159: -------------------------------- Fix Version/s: 10.3.0.GA > 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 > Fix For: 10.3.0.GA > > > 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, 3 months

1
0
0 / 0

[JBoss JIRA] (JBDS-4219) minor text fix: bundled installer should say "Install" instead of "Download and Install"

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBDS-4219?page=com.atlassian.jira.plugin.... ] Denis Golovin closed JBDS-4219. ------------------------------- Resolution: Done > minor text fix: bundled installer should say "Install" instead of "Download and Install" > ---------------------------------------------------------------------------------------- > > Key: JBDS-4219 > URL: https://issues.jboss.org/browse/JBDS-4219 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Bug > Components: platform-installer > Reporter: Misha Ali > Priority: Minor > > The bundled and online installer both have a button when selecting components that says "Download & Install" and the next screen shows the current step in the process at the top of the installer screen as "Download & Install" as well. This is correct for the online installer but not for the bundled installer and should be changed to something like just "Install". -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBDS-4219) minor text fix: bundled installer should say "Install" instead of "Download and Install"

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBDS-4219?page=com.atlassian.jira.plugin.... ] Denis Golovin commented on JBDS-4219: ------------------------------------- it is bundled with our products, but Virtualbox and Vagrant are still downloaded. Button text should probably always be 'Install' and components in list should indicate in some way that they are going to be downloaded. Linking original issue and closing as duplicate. > minor text fix: bundled installer should say "Install" instead of "Download and Install" > ---------------------------------------------------------------------------------------- > > Key: JBDS-4219 > URL: https://issues.jboss.org/browse/JBDS-4219 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Bug > Components: platform-installer > Reporter: Misha Ali > Priority: Minor > > The bundled and online installer both have a button when selecting components that says "Download & Install" and the next screen shows the current step in the process at the top of the installer screen as "Download & Install" as well. This is correct for the online installer but not for the bundled installer and should be changed to something like just "Install". -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBTIS-948) Runtime is not detected if the Devstudio was installed using the InstallConfigRecord.xml

by Paul Leacu (JIRA)

[ https://issues.jboss.org/browse/JBTIS-948?page=com.atlassian.jira.plugin.... ] Paul Leacu reassigned JBTIS-948: -------------------------------- Assignee: Paul Leacu (was: Rob Stryker) > Runtime is not detected if the Devstudio was installed using the InstallConfigRecord.xml > ---------------------------------------------------------------------------------------- > > Key: JBTIS-948 > URL: https://issues.jboss.org/browse/JBTIS-948 > Project: JBoss Tools Integration Stack > Issue Type: Bug > Components: distribution > Affects Versions: 10.0.0.CR1 > Environment: devstudio-integration-stack-rt-10.0.0.CR1-standalone-installer.jar > Reporter: Andrej Podhradsky > Assignee: Paul Leacu > Attachments: ds-10.2-pref-cmd-install.png, ds-10.2-pref-gui-install.png > > > Runtime is not detected if the Devstudio was installed using the InstallConfigRecord.xml. It seems that the folder for runtime detection is set to {{<user>/jboss-runtimes}}. > The above folder can be found at Preferences > JBoss Tools > JBoss Runtime Detection -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 3 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23651) Incremental publish to remote server throws exception

by Rastislav Wagner (JIRA)

Rastislav Wagner created JBIDE-23651: ---------------------------------------- Summary: Incremental publish to remote server throws exception Key: JBIDE-23651 URL: https://issues.jboss.org/browse/JBIDE-23651 Project: Tools (JBoss Tools) Issue Type: Bug Components: server Affects Versions: 4.4.2.Final Reporter: Rastislav Wagner Fix For: 4.4.3.AM1 {code} failed to create folder /opt/wildfly/standalone/deployments/jboss-as-kitchensink-html5-mobile.war on host jawa32g2.mw.lab.eng.brq.redhat.com {code} {code} org.eclipse.rse.services.files.RemoteFileIOException: Operation failed. File system input or output error at org.eclipse.rse.internal.services.ssh.files.SftpFileService.makeSystemMessageException(SftpFileService.java:596) at org.eclipse.rse.internal.services.ssh.files.SftpFileService.createFolder(SftpFileService.java:1103) at org.jboss.ide.eclipse.as.rse.core.subsystems.RSEFilesystemController$3.run(RSEFilesystemController.java:107) at org.jboss.tools.foundation.core.jobs.BarrierProgressWaitJob.run(BarrierProgressWaitJob.java:85) at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55) {code} Incremetal publish successfully completes (file is updated) but exception is logged in error because RSEFilesystemController is trying to create a folder on remote server which already exists (was created during full publish) -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 3 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