[JBoss JIRA] (JBIDE-24043) Upversion jbosstools-server in master and maintenance
by Martin Malina (JIRA)
[ https://issues.jboss.org/browse/JBIDE-24043?page=com.atlassian.jira.plugi... ]
Martin Malina closed JBIDE-24043.
---------------------------------
The commits seem alright and I checked the versions in the devstudio 10.4.0.AM1 build and they also seem correct.
> Upversion jbosstools-server in master and maintenance
> -----------------------------------------------------
>
> Key: JBIDE-24043
> URL: https://issues.jboss.org/browse/JBIDE-24043
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: server
> Affects Versions: 4.4.4.AM1, 4.5.0.AM1
> Reporter: Rob Stryker
> Assignee: Rob Stryker
> Fix For: 4.4.4.AM1, 4.5.0.AM1
>
>
> In maintenance:
> archives from 3.6.103 to 3.6.104
> jmx from 1.8.3 to 1.9.0 bc of API change
> wtp from 1.3.103 to 1.3.104
> AS from 3.2.3 to 3.2.4
> In Master
> archives from 3.6.103 to 3.6.110 to leave room in case of emergency
> jmx from 1.8.3 to 1.10.0 to leave room and also bc I expect further changes
> wtp from 1.3.103 to 1.3.110 to leave room in case of emergency
> AS from 3.2.3 to 3.3.0 because I expect API additions and new features
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
9 years
[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 resolved JBDS-4159.
---------------------------------
Resolution: Out of Date
CDK 2.4 is EOL and CDK 3 related work is here JBDS-4304.
> 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.4.0.AM1
>
>
> 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