January 2017 - jbosstools-issues - Jboss List Archives

[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: -------------------------------- Sprint: devex #126 January 2017 > 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, 2 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 #126 January 2017 > 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.3.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 (v7.2.3#72005)

9 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBDS-4016) Add Readme.txt(.md) in the root of devsuite installation with references to all included projects

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBDS-4016?page=com.atlassian.jira.plugin.... ] Denis Golovin updated JBDS-4016: -------------------------------- Description: This file should be generated during build based on info in platform specific requirements*.json > Add Readme.txt(.md) in the root of devsuite installation with references to all included projects > ------------------------------------------------------------------------------------------------- > > Key: JBDS-4016 > URL: https://issues.jboss.org/browse/JBDS-4016 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Task > Components: platform-installer > Affects Versions: 10.1.0.GA > Reporter: Denis Golovin > Assignee: Denis Golovin > Fix For: 10.3.0.AM2 > > > This file should be generated during build based on info in platform specific requirements*.json -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBDS-4248) Uninstaller script asks to press any key to exit, but accepts only Enter

by Denis Golovin (JIRA)

Denis Golovin created JBDS-4248: ----------------------------------- Summary: Uninstaller script asks to press any key to exit, but accepts only Enter Key: JBDS-4248 URL: https://issues.jboss.org/browse/JBDS-4248 Project: Red Hat JBoss Developer Studio (devstudio) Issue Type: Task Components: platform-installer Affects Versions: 10.3.0.AM2 Environment: Windows Reporter: Denis Golovin Assignee: Denis Golovin Uninstaller PS script asks to press any key to exit {code}PS C:\Users\eskimo> powershell -ExecutionPolicy bypass -file C:\DevelopmentSuite1\uninstaller\uninstall.ps1 Uninstalling Red Hat Development Suite Removing installation folder DONE Removing path entries DONE Press any key to exit {code} But it exits only when Enter pressed. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23637) AERI report: NPE in CDKRuntimeDetector.exists

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23637?page=com.atlassian.jira.plugi... ] Rob Stryker resolved JBIDE-23637. --------------------------------- Resolution: Done pushed to master > AERI report: NPE in CDKRuntimeDetector.exists > --------------------------------------------- > > Key: JBIDE-23637 > URL: https://issues.jboss.org/browse/JBIDE-23637 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: cdk > Affects Versions: 4.5.0.AM1 > Reporter: Dmitrii Bocharov > Assignee: Rob Stryker > Fix For: 4.4.3.AM2 > > > https://aer.ctrlflow.com/redhat/reporters#!/problems/584af47be4b0c53b1227... > {noformat} > at org.jboss.tools.openshift.cdk.server.core.internal.detection.CDKRuntimeDetector.exists(CDKRuntimeDetector.java:106) >  > at org.jboss.tools.openshift.cdk.server.core.internal.detection.CDKRuntimeDetector.initializeRuntime(CDKRuntimeDetector.java:55) >  > at org.jboss.tools.runtime.core.internal.RuntimeDetector.initializeRuntime(RuntimeDetector.java:149) >  > at org.jboss.tools.runtime.core.util.RuntimeInitializerUtil.initializeRuntimes(RuntimeInitializerUtil.java:56) >  > at org.jboss.tools.runtime.core.util.RuntimeInitializerUtil.initializeRuntimesFromFolder(RuntimeInitializerUtil.java:36) >  > at org.jboss.tools.runtime.ui.internal.startup.JBossRuntimeStartup.initializeCDKRuntimes(JBossRuntimeStartup.java:78) >  > at org.jboss.tools.runtime.ui.internal.startup.JBossRuntimeStartup.initializeRuntimes(JBossRuntimeStartup.java:53) >  > at org.jboss.tools.runtime.ui.internal.startup.RuntimeScanner$1.run(RuntimeScanner.java:79) > {noformat} -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23637) AERI report: NPE in CDKRuntimeDetector.exists

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23637?page=com.atlassian.jira.plugi... ] Rob Stryker updated JBIDE-23637: -------------------------------- Fix Version/s: 4.4.3.AM2 > AERI report: NPE in CDKRuntimeDetector.exists > --------------------------------------------- > > Key: JBIDE-23637 > URL: https://issues.jboss.org/browse/JBIDE-23637 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: cdk > Affects Versions: 4.5.0.AM1 > Reporter: Dmitrii Bocharov > Fix For: 4.4.3.AM2 > > > https://aer.ctrlflow.com/redhat/reporters#!/problems/584af47be4b0c53b1227... > {noformat} > at org.jboss.tools.openshift.cdk.server.core.internal.detection.CDKRuntimeDetector.exists(CDKRuntimeDetector.java:106) >  > at org.jboss.tools.openshift.cdk.server.core.internal.detection.CDKRuntimeDetector.initializeRuntime(CDKRuntimeDetector.java:55) >  > at org.jboss.tools.runtime.core.internal.RuntimeDetector.initializeRuntime(RuntimeDetector.java:149) >  > at org.jboss.tools.runtime.core.util.RuntimeInitializerUtil.initializeRuntimes(RuntimeInitializerUtil.java:56) >  > at org.jboss.tools.runtime.core.util.RuntimeInitializerUtil.initializeRuntimesFromFolder(RuntimeInitializerUtil.java:36) >  > at org.jboss.tools.runtime.ui.internal.startup.JBossRuntimeStartup.initializeCDKRuntimes(JBossRuntimeStartup.java:78) >  > at org.jboss.tools.runtime.ui.internal.startup.JBossRuntimeStartup.initializeRuntimes(JBossRuntimeStartup.java:53) >  > at org.jboss.tools.runtime.ui.internal.startup.RuntimeScanner$1.run(RuntimeScanner.java:79) > {noformat} -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23637) AERI report: NPE in CDKRuntimeDetector.exists

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23637?page=com.atlassian.jira.plugi... ] Rob Stryker reassigned JBIDE-23637: ----------------------------------- Assignee: Rob Stryker > AERI report: NPE in CDKRuntimeDetector.exists > --------------------------------------------- > > Key: JBIDE-23637 > URL: https://issues.jboss.org/browse/JBIDE-23637 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: cdk > Affects Versions: 4.5.0.AM1 > Reporter: Dmitrii Bocharov > Assignee: Rob Stryker > Fix For: 4.4.3.AM2 > > > https://aer.ctrlflow.com/redhat/reporters#!/problems/584af47be4b0c53b1227... > {noformat} > at org.jboss.tools.openshift.cdk.server.core.internal.detection.CDKRuntimeDetector.exists(CDKRuntimeDetector.java:106) >  > at org.jboss.tools.openshift.cdk.server.core.internal.detection.CDKRuntimeDetector.initializeRuntime(CDKRuntimeDetector.java:55) >  > at org.jboss.tools.runtime.core.internal.RuntimeDetector.initializeRuntime(RuntimeDetector.java:149) >  > at org.jboss.tools.runtime.core.util.RuntimeInitializerUtil.initializeRuntimes(RuntimeInitializerUtil.java:56) >  > at org.jboss.tools.runtime.core.util.RuntimeInitializerUtil.initializeRuntimesFromFolder(RuntimeInitializerUtil.java:36) >  > at org.jboss.tools.runtime.ui.internal.startup.JBossRuntimeStartup.initializeCDKRuntimes(JBossRuntimeStartup.java:78) >  > at org.jboss.tools.runtime.ui.internal.startup.JBossRuntimeStartup.initializeRuntimes(JBossRuntimeStartup.java:53) >  > at org.jboss.tools.runtime.ui.internal.startup.RuntimeScanner$1.run(RuntimeScanner.java:79) > {noformat} -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-23701) Server New and Noteworthy for 4.4.3.AM1

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-23701?page=com.atlassian.jira.plugi... ] Rob Stryker closed JBIDE-23701. ------------------------------- Fix Version/s: 4.4.3.AM1 Resolution: Done No significant changes here > Server New and Noteworthy for 4.4.3.AM1 > --------------------------------------------------- > > Key: JBIDE-23701 > URL: https://issues.jboss.org/browse/JBIDE-23701 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: archives, jmx, server > Reporter: Jeff MAURY > Assignee: Rob Stryker > Priority: Critical > Fix For: 4.4.3.AM1 > > > Search for your component's New and Noteworthy issues: > Queries: > * [Completed Server JIRAs marked N&N|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and+...] > * [All Completed JIRAs marked N&N|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and+...] > * [N&N Task JIRAs for this milestone|https://issues.jboss.org/issues/?jql=summary+%7E+%22New+and+Not...] > * [All N&N Task JIRAs|https://issues.jboss.org/issues/?jql=summary+%7E+%22New+and+Notewor...] > If no N&N issues are found for Server, check if there are issues that SHOULD have been labelled with *Labels =* _new_and_noteworthy_, and add them. > Document the ones relevant for Server by submitting a pull request against: > * https://github.com/jbosstools/jbosstools-website/tree/master/documentatio... > If your PR's commit comment is of the form 'JBIDE-56789 #comment Create N&N for Server4.4.3.AM1 #close', and your github user's email address is the same as your JIRA one, then this JIRA should be closed automatically when the PR is applied. > If there is nothing new or noteworthy for Server for this milestone, please *reject* and *close* this issue. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBTIS-1015) Latest JBDSIS Target Platform cannot be used locally

by Paul Leacu (JIRA)

[ https://issues.jboss.org/browse/JBTIS-1015?page=com.atlassian.jira.plugin... ] Paul Leacu edited comment on JBTIS-1015 at 1/12/17 3:03 PM: ------------------------------------------------------------ Just so we don't lose it - here's the javax.crypto bug: https://bugs.eclipse.org/bugs/show_bug.cgi?id=284465 https://bugs.eclipse.org/bugs/show_bug.cgi?id=434959 was (Author: pleacu): Just so we don't lose it - here's the javax.crypto bug: https://bugs.eclipse.org/bugs/show_bug.cgi?id=284465 > Latest JBDSIS Target Platform cannot be used locally > ---------------------------------------------------- > > Key: JBTIS-1015 > URL: https://issues.jboss.org/browse/JBTIS-1015 > Project: JBoss Tools Integration Stack > Issue Type: Bug > Components: target-platform > Affects Versions: 4.4.1.CR2-TP > Reporter: Aurélien Pupier > Assignee: Paul Leacu > Attachments: a1.png, a2.png, a3.png, a4.png, a5.png, b1.png, b2.png, commons.io available in folder.png, commons.io not visible in update site.png > > > Current state of understanding: > There are 2 different bugs: > * when using local "Directory": the jars which should be exploded in folder stay in jars > ** wondering if org.jboss.tools.tycho-plugins:target-platform-utils should be responsible to explode them or if it should be the task for P2 itself? > ** the implication is that we can't start a CDK server with such a TP > * when using local "Software site": the JVM packages are not recognized (javax.crypto for instance) > ** looks like a p2 bugs > ** the implication is that the TP doesn't resolve at all > If one of these two bugs can be fixed, we will have a way to consume a local Target Platform. > see [JBTIS-1008] for original discussions -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 2 months

1
0
0 / 0

[JBoss JIRA] (JBDS-4247) Replace 7Zip self extracting executable

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBDS-4247?page=com.atlassian.jira.plugin.... ] Denis Golovin reassigned JBDS-4247: ----------------------------------- Assignee: Denis Golovin > Replace 7Zip self extracting executable > --------------------------------------- > > Key: JBDS-4247 > URL: https://issues.jboss.org/browse/JBDS-4247 > Project: Red Hat JBoss Developer Studio (devstudio) > Issue Type: Task > Components: platform-installer > Affects Versions: 10.3.0.AM2 > Environment: Windows > Reporter: Denis Golovin > Assignee: Denis Golovin > > Implement simple installer based on [go-bindata:https://github.com/jteeuwen/go-bindata]. > It would do simple thing similar to other self-extracting installers, unpack specific Asset from executable and run it. > In case of windows installer it would speedup installation. because instead of extracting everything for bundle installer as 7Zip does, it would pull only installer first and run it. Then every specific installer selected for installation would first pull data out of installer executable with go-bindata. > This approach would fix several opened issues that should be addressed upstream in 7Zip selexecuatble. -- This message was sent by Atlassian JIRA (v7.2.3#72005)

9 years, 2 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 January 2017