April 2016 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBDS-3749) With existing virtual box 5.0.16 already installed, bundled installer refuses to see it and let me proceed to install

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBDS-3749?page=com.atlassian.jira.plugin.... ] Nick Boldt updated JBDS-3749: ----------------------------- Attachment: vbox5016-installed-detected-cant-selected-i-want-to-use-existing-vb.png Looks like my fix was incomplete... VB 5.0.16 is now detected and the path is shown, but the "i want to use existing" can't be selected. !vbox5016-installed-detected-cant-selected-i-want-to-use-existing-vb.png! > With existing virtual box 5.0.16 already installed, bundled installer refuses to see it and let me proceed to install > --------------------------------------------------------------------------------------------------------------------- > > Key: JBDS-3749 > URL: https://issues.jboss.org/browse/JBDS-3749 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Components: installer > Affects Versions: 9.1.0.CR1 > Reporter: Nick Boldt > Priority: Blocker > Fix For: 9.1.0.GA > > Attachments: vb-not-detected-can-not-proceed.png, vbox5016-installed-detected-cant-selected-i-want-to-use-existing-vb.png, win10-details.png > > > Downloaded Setup-bundled-0.0.2-20160331-23.exe > Logged in using my RHD credentials > On the Confirmation step of the installer, I see an unchecked box for ORACLE VIRTUALBOX v5 and an unchecked box for "I want to use the existing VirtualBox". > I can't check either of them (when I cursor over them I see a red NOT circle) so as a result the "Download & Install" button is greyed out - it too has a red NOT circle when I cursor over it. > I have VB installed here: > C:\Program Files\Oracle\VirtualBox\VirtualBox.exe > Version 5.0.16 r105871 -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (JBDS-3775) Missing maven.repository.redhat.com

by Burr Sutter (JIRA)

Burr Sutter created JBDS-3775: --------------------------------- Summary: Missing maven.repository.redhat.com Key: JBDS-3775 URL: https://issues.jboss.org/browse/JBDS-3775 Project: Developer Studio (JBoss Developer Studio) Issue Type: Bug Components: installer Reporter: Burr Sutter Priority: Critical After using the Installer, I select Red Hat Central, OpenShift Application, eap64-basic-sti which then imports the kitchensink project into my workspace, it immediately has compile errors http://screencast.com/t/y1NFnvaMcJD -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (JBDS-3774) Failed due to 2 attempts at installing CDK's vagrant box

by Burr Sutter (JIRA)

[ https://issues.jboss.org/browse/JBDS-3774?page=com.atlassian.jira.plugin.... ] Burr Sutter updated JBDS-3774: ------------------------------ Attachment: install.log vbox.log vagrant.log > Failed due to 2 attempts at installing CDK's vagrant box > -------------------------------------------------------- > > Key: JBDS-3774 > URL: https://issues.jboss.org/browse/JBDS-3774 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Components: installer > Environment: Windows 10 Pro > Reporter: Burr Sutter > Attachments: install.log, vagrant.log, vbox.log > > > Wed, 06 Apr 2016 01:01:51 GMT-ERROR: cdk - Error: Command failed: > C:\WINDOWS\system32\cmd.exe /s /c "vagrant box remove cdkv2 -f" > 'vagrant' is not recognized as an internal or external command, > operable program or batch file. > ... > Wed, 06 Apr 2016 01:02:15 GMT-ERROR: cdk - Error: Command failed: > C:\WINDOWS\system32\cmd.exe /s /c "vagrant box add --name cdkv2 > c:\DeveloperPlatform\cdk\boxes\rhel-vagrant-virtualbox.box" > The box you're attempting to add already exists. Remove it before > adding it again or add it with the `--force` flag. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (JBDS-3774) Failed due to 2 attempts at installing CDK's vagrant box

by Burr Sutter (JIRA)

[ https://issues.jboss.org/browse/JBDS-3774?page=com.atlassian.jira.plugin.... ] Burr Sutter updated JBDS-3774: ------------------------------ Description: Wed, 06 Apr 2016 01:01:51 GMT-ERROR: cdk - Error: Command failed: C:\WINDOWS\system32\cmd.exe /s /c "vagrant box remove cdkv2 -f" 'vagrant' is not recognized as an internal or external command, operable program or batch file. ... Wed, 06 Apr 2016 01:02:15 GMT-ERROR: cdk - Error: Command failed: C:\WINDOWS\system32\cmd.exe /s /c "vagrant box add --name cdkv2 c:\DeveloperPlatform\cdk\boxes\rhel-vagrant-virtualbox.box" The box you're attempting to add already exists. Remove it before adding it again or add it with the `--force` flag. > Failed due to 2 attempts at installing CDK's vagrant box > -------------------------------------------------------- > > Key: JBDS-3774 > URL: https://issues.jboss.org/browse/JBDS-3774 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Components: installer > Environment: Windows 10 Pro > Reporter: Burr Sutter > Attachments: install.log, vagrant.log, vbox.log > > > Wed, 06 Apr 2016 01:01:51 GMT-ERROR: cdk - Error: Command failed: > C:\WINDOWS\system32\cmd.exe /s /c "vagrant box remove cdkv2 -f" > 'vagrant' is not recognized as an internal or external command, > operable program or batch file. > ... > Wed, 06 Apr 2016 01:02:15 GMT-ERROR: cdk - Error: Command failed: > C:\WINDOWS\system32\cmd.exe /s /c "vagrant box add --name cdkv2 > c:\DeveloperPlatform\cdk\boxes\rhel-vagrant-virtualbox.box" > The box you're attempting to add already exists. Remove it before > adding it again or add it with the `--force` flag. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (JBDS-3774) Failed due to 2 attempts at installing CDK's vagrant box

by Burr Sutter (JIRA)

Burr Sutter created JBDS-3774: --------------------------------- Summary: Failed due to 2 attempts at installing CDK's vagrant box Key: JBDS-3774 URL: https://issues.jboss.org/browse/JBDS-3774 Project: Developer Studio (JBoss Developer Studio) Issue Type: Bug Components: installer Environment: Windows 10 Pro Reporter: Burr Sutter -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-22032) Set common default width to buttons in dialogs that are more narrow than OK or Finish button

by Viacheslav Kabanovich (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22032?page=com.atlassian.jira.plugi... ] Viacheslav Kabanovich commented on JBIDE-22032: ----------------------------------------------- Description lists pages of wizards in which after this fix widths of buttons in input editors should be no less than the width of Back/Next/Cancel/Finish buttons, in most cases - equal to it. You can also search through all other wizards and dialogs to check if some button's width does not look good. > Set common default width to buttons in dialogs that are more narrow than OK or Finish button > -------------------------------------------------------------------------------------------- > > Key: JBIDE-22032 > URL: https://issues.jboss.org/browse/JBIDE-22032 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.3.1.CR1 > Reporter: Viacheslav Kabanovich > Assignee: Viacheslav Kabanovich > Fix For: 4.3.1.CR1, 4.4.0.Alpha1 > > > OpenShift Projects (ManageProjectsWizardPage) > Resource Labels (ResourceLabelsPage) > Services & Routing Settings (ServicesAndRoutingPage) > SSL certificates (SSLCertificatesPreferencePage) > Select template (TemplateListPage, SelectProjectComponentBuilder) > Template Parameters (TemplateParametersPage) -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-18362) Dependency installation during platform build

by Pavol Srna (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18362?page=com.atlassian.jira.plugi... ] Pavol Srna closed JBIDE-18362. ------------------------------ > Dependency installation during platform build > --------------------------------------------- > > Key: JBIDE-18362 > URL: https://issues.jboss.org/browse/JBIDE-18362 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: aerogear-hybrid > Affects Versions: 4.2.0.CR1 > Reporter: Gorkem Ercan > Assignee: Gorkem Ercan > Fix For: 4.3.1.CR1 > > > Check and install plugin dependencies and missing config.xml entries when building the projects for a platform -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (JBTIS-640) Cannot install JBDS-IS EA in offline mode

by Andrej Podhradsky (JIRA)

[ https://issues.jboss.org/browse/JBTIS-640?page=com.atlassian.jira.plugin.... ] Andrej Podhradsky commented on JBTIS-640: ----------------------------------------- And the following error when installeing from master ea zip file {code} Cannot complete the install because one or more required items could not be found. Software being installed: SwitchYard BPEL Support 2.1.0.Beta3-v20160226-2057-B645 (org.switchyard.tools.bpel.feature.feature.group 2.1.0.Beta3-v20160226-2057-B645) Missing requirement: SwitchYard BPEL Support 2.1.0.Beta3-v20160226-2057-B645 (org.switchyard.tools.bpel.feature.feature.group 2.1.0.Beta3-v20160226-2057-B645) requires 'org.eclipse.bpel.feature.feature.group [1.0.2,2.0.0)' but it could not be found {code} This can be again solved by adding the GA zip file. > Cannot install JBDS-IS EA in offline mode > ----------------------------------------- > > Key: JBTIS-640 > URL: https://issues.jboss.org/browse/JBTIS-640 > Project: JBoss Tools Integration Stack > Issue Type: Bug > Components: distribution > Affects Versions: 9.0.0.CR1 > Reporter: Andrej Podhradsky > Priority: Blocker > > When installing JBDS-IS 9.0.0.CR1 EA from the zip file I'm getting the following > {code} > Cannot complete the install because one or more required items could not be found. > Software being installed: JBoss Fuse Tooling Core Bundles 8.0.0.Beta2-v20160401-1305-B821 (org.fusesource.ide.core.feature.feature.group 8.0.0.Beta2-v20160401-1305-B821) > Missing requirement: JBoss Fuse Tooling Core Bundles 8.0.0.Beta2-v20160401-1305-B821 (org.fusesource.ide.core.feature.feature.group 8.0.0.Beta2-v20160401-1305-B821) requires 'org.eclipse.zest.core 1.5.100' but it could not be found > {code} > EDIT: this can be resolved by adding JBDS-IS 9.0.0.CR1 zip file (the GA one) -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (JBTIS-640) Cannot install JBDS-IS EA in offline mode

by Andrej Podhradsky (JIRA)

[ https://issues.jboss.org/browse/JBTIS-640?page=com.atlassian.jira.plugin.... ] Andrej Podhradsky updated JBTIS-640: ------------------------------------ Description: When installing JBDS-IS 9.0.0.CR1 EA from the zip file I'm getting the following {code} Cannot complete the install because one or more required items could not be found. Software being installed: JBoss Fuse Tooling Core Bundles 8.0.0.Beta2-v20160401-1305-B821 (org.fusesource.ide.core.feature.feature.group 8.0.0.Beta2-v20160401-1305-B821) Missing requirement: JBoss Fuse Tooling Core Bundles 8.0.0.Beta2-v20160401-1305-B821 (org.fusesource.ide.core.feature.feature.group 8.0.0.Beta2-v20160401-1305-B821) requires 'org.eclipse.zest.core 1.5.100' but it could not be found {code} EDIT: this can be resolved by adding JBDS-IS 9.0.0.CR1 zip file (the GA one) was: When installing JBDS-IS 9.0.0.CR1 EA from the zip file I'm getting the following {code} Cannot complete the install because one or more required items could not be found. Software being installed: JBoss Fuse Tooling Core Bundles 8.0.0.Beta2-v20160401-1305-B821 (org.fusesource.ide.core.feature.feature.group 8.0.0.Beta2-v20160401-1305-B821) Missing requirement: JBoss Fuse Tooling Core Bundles 8.0.0.Beta2-v20160401-1305-B821 (org.fusesource.ide.core.feature.feature.group 8.0.0.Beta2-v20160401-1305-B821) requires 'org.eclipse.zest.core 1.5.100' but it could not be found {code} > Cannot install JBDS-IS EA in offline mode > ----------------------------------------- > > Key: JBTIS-640 > URL: https://issues.jboss.org/browse/JBTIS-640 > Project: JBoss Tools Integration Stack > Issue Type: Bug > Components: distribution > Affects Versions: 9.0.0.CR1 > Reporter: Andrej Podhradsky > Priority: Blocker > > When installing JBDS-IS 9.0.0.CR1 EA from the zip file I'm getting the following > {code} > Cannot complete the install because one or more required items could not be found. > Software being installed: JBoss Fuse Tooling Core Bundles 8.0.0.Beta2-v20160401-1305-B821 (org.fusesource.ide.core.feature.feature.group 8.0.0.Beta2-v20160401-1305-B821) > Missing requirement: JBoss Fuse Tooling Core Bundles 8.0.0.Beta2-v20160401-1305-B821 (org.fusesource.ide.core.feature.feature.group 8.0.0.Beta2-v20160401-1305-B821) requires 'org.eclipse.zest.core 1.5.100' but it could not be found > {code} > EDIT: this can be resolved by adding JBDS-IS 9.0.0.CR1 zip file (the GA one) -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (JBTIS-640) Cannot install JBDS-IS EA in offline mode

by Andrej Podhradsky (JIRA)

Andrej Podhradsky created JBTIS-640: --------------------------------------- Summary: Cannot install JBDS-IS EA in offline mode Key: JBTIS-640 URL: https://issues.jboss.org/browse/JBTIS-640 Project: JBoss Tools Integration Stack Issue Type: Bug Components: distribution Affects Versions: 9.0.0.CR1 Reporter: Andrej Podhradsky Priority: Blocker When installing JBDS-IS 9.0.0.CR1 EA from the zip file I'm getting the following {code} Cannot complete the install because one or more required items could not be found. Software being installed: JBoss Fuse Tooling Core Bundles 8.0.0.Beta2-v20160401-1305-B821 (org.fusesource.ide.core.feature.feature.group 8.0.0.Beta2-v20160401-1305-B821) Missing requirement: JBoss Fuse Tooling Core Bundles 8.0.0.Beta2-v20160401-1305-B821 (org.fusesource.ide.core.feature.feature.group 8.0.0.Beta2-v20160401-1305-B821) requires 'org.eclipse.zest.core 1.5.100' but it could not be found {code} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

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 April 2016