[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:
-------------------------------------
That is correct.
> 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)
7 years, 6 months
[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 edited comment on JBDS-4159 at 12/20/16 12:06 AM:
----------------------------------------------------------------
[~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 going to be roughly the same size as it is right now.
was (Author: dgolovin):
[~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)
7 years, 6 months
[JBoss JIRA] (JBDS-4226) Migrate to gulp-angular-protractor 0.3.0
by Denis Golovin (JIRA)
Denis Golovin created JBDS-4226:
-----------------------------------
Summary: Migrate to gulp-angular-protractor 0.3.0
Key: JBDS-4226
URL: https://issues.jboss.org/browse/JBDS-4226
Project: Red Hat JBoss Developer Studio (devstudio)
Issue Type: Task
Components: platform-installer
Affects Versions: 10.3.0.AM2
Reporter: Denis Golovin
Assignee: Denis Golovin
Fix For: 10.3.0.AM2
Latest version for gulp-angular-protractor(a)0.3.0 does not work ui-test. There are several changes in package structure that requires changes in ui-test script and configuration
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
7 years, 6 months
[JBoss JIRA] (JBDS-4191) problem installing atlassian: depends on javax.servlet 3.1.0 -- remove atlassian from Central
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBDS-4191?page=com.atlassian.jira.plugin.... ]
Nick Boldt updated JBDS-4191:
-----------------------------
Git Pull Request: https://github.com/jbosstools/jbosstools-target-platforms/pull/251, https://github.com/jbosstools/jbosstools-discovery/pull/339, https://github.com/jbosstools/jbosstools-base/pull/546, https://github.com/jbosstools/jbosstools-base/pull/548 (was: https://github.com/jbosstools/jbosstools-target-platforms/pull/251, https://github.com/jbosstools/jbosstools-discovery/pull/339, https://github.com/jbosstools/jbosstools-base/pull/546)
> problem installing atlassian: depends on javax.servlet 3.1.0 -- remove atlassian from Central
> ---------------------------------------------------------------------------------------------
>
> Key: JBDS-4191
> URL: https://issues.jboss.org/browse/JBDS-4191
> Project: Red Hat JBoss Developer Studio (devstudio)
> Issue Type: Sub-task
> Components: central-update, rpm
> Affects Versions: 10.2.0.AM3
> Reporter: Nick Boldt
> Assignee: Nick Boldt
> Fix For: 10.3.0.AM1
>
>
> atlassian: depends on javax.servlet 3.1.0 (via req-bundle on javax.xml.rpc 1.1.0 from c.a.conn.eclipse.jira.core)
> : also depends on org.eclipse.core.runtime.compatibility.auth
> : also depends on mortbay, which breaks because of javax/servlet/Servlet
> {code}
> !MESSAGE Authorization infrastructure (org.eclipse.core.runtime.compatibility.auth) not installed.
> !STACK 0
> java.lang.ClassNotFoundException: org.eclipse.core.internal.runtime.auth.AuthorizationDatabase cannot be found by org.eclipse.core.runtime_3.12.0.v20160920-1429
> at org.eclipse.osgi.internal.loader.BundleLoader.findClassInternal(BundleLoader.java:461)
> at org.eclipse.osgi.internal.loader.BundleLoader.findClass(BundleLoader.java:372)
> at org.eclipse.osgi.internal.loader.BundleLoader.findClass(BundleLoader.java:364)
> at org.eclipse.osgi.internal.loader.ModuleClassLoader.loadClass(ModuleClassLoader.java:161)
> at java.lang.ClassLoader.loadClass(ClassLoader.java:357)
> at java.lang.Class.forName0(Native Method)
> at java.lang.Class.forName(Class.java:264)
> at org.eclipse.core.internal.runtime.AuthorizationHandler.getAuthClass(AuthorizationHandler.java:48)
> at org.eclipse.core.internal.runtime.AuthorizationHandler.loadKeyring(AuthorizationHandler.java:69)
> at org.eclipse.core.internal.runtime.AuthorizationHandler.flushAuthorizationInfo(AuthorizationHandler.java:231)
> at org.eclipse.core.runtime.Platform.flushAuthorizationInfo(Platform.java:590)
> at com.atlassian.connector.eclipse.internal.commons.ui.MigrateToSecureStorageJob.migrateToSecureStorage(MigrateToSecureStorageJob.java:89)
> at com.atlassian.connector.eclipse.internal.commons.ui.MigrateToSecureStorageJob.runInUIThread(MigrateToSecureStorageJob.java:60)
> !ENTRY org.eclipse.core.jobs 4 2 2016-11-17 21:09:30.244
> !MESSAGE An internal error occurred during: "Start Embedded Web Server".
> !STACK 0
> java.lang.LinkageError: loader constraint violation: when resolving method "org.mortbay.jetty.servlet.ServletHolder.<init>(Ljavax/servlet/Servlet;)V" the class loader (instance of org/eclipse/osgi/internal/loader/EquinoxClassLoader) of the current class, com/atlassian/connector/eclipse/internal/directclickthrough/ui/DirectClickThroughUiPlugin$2, and the class loader (instance of org/eclipse/osgi/internal/loader/EquinoxClassLoader) for the method's defining class, org/mortbay/jetty/servlet/ServletHolder, have different Class objects for the type javax/servlet/Servlet used in the signature
> at com.atlassian.connector.eclipse.internal.directclickthrough.ui.DirectClickThroughUiPlugin$2.runImpl(DirectClickThroughUiPlugin.java:88)
> at com.atlassian.connector.eclipse.internal.core.jobs.JobWithStatus.run(JobWithStatus.java:50)
> at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55)
> depends on and installs javax.servlet:
> * com.atlassian.connector.eclipse.bamboo.feature
> * com.atlassian.connector.eclipse.directclickthrough.feature
> * com.atlassian.connector.eclipse.jira.feature
> * com.atlassian.connector.commons.feature -> connector.commons -> javax.xml.rpc 1.1.0 -> javax.servlet 3.1.0
> {code}
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
7 years, 6 months
[JBoss JIRA] (JBDS-4191) problem installing atlassian: depends on javax.servlet 3.1.0 -- remove atlassian from Central
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBDS-4191?page=com.atlassian.jira.plugin.... ]
Nick Boldt edited comment on JBDS-4191 at 12/19/16 1:24 PM:
------------------------------------------------------------
Having removed the atlassian stuff from Central, I'm now getting a new error:
{code}
[ERROR] Cannot resolve project dependencies:
[ERROR] Software being installed: org.jboss.tools.site.core raw:4.4.3.'SNAPSHOT'/format(n[.n=0;[.n=0;[-S]]]):4.4.3-SNAPSHOT
[ERROR] Missing requirement: org.jboss.tools.common.mylyn.feature.feature.group 3.8.3.v20161213-1258 requires 'com.atlassian.connector.eclipse.jira.feature.group 3.2.2' but it could not be found
[ERROR] Cannot satisfy dependency: org.jboss.tools.site.core raw:4.4.3.'SNAPSHOT'/format(n[.n=0;[.n=0;[-S]]]):4.4.3-SNAPSHOT depends on: org.jboss.tools.common.mylyn.feature.feature.group 0.0.0{code}
So... we need to disconnect this feature, *org.jboss.tools.common.mylyn.feature*, from its dependency on *com.atlassian.connector.eclipse.jira*
PR: https://github.com/jbosstools/jbosstools-base/pull/546, https://github.com/jbosstools/jbosstools-base/pull/548
was (Author: nickboldt):
Having removed the atlassian stuff from Central, I'm now getting a new error:
{code}
[ERROR] Cannot resolve project dependencies:
[ERROR] Software being installed: org.jboss.tools.site.core raw:4.4.3.'SNAPSHOT'/format(n[.n=0;[.n=0;[-S]]]):4.4.3-SNAPSHOT
[ERROR] Missing requirement: org.jboss.tools.common.mylyn.feature.feature.group 3.8.3.v20161213-1258 requires 'com.atlassian.connector.eclipse.jira.feature.group 3.2.2' but it could not be found
[ERROR] Cannot satisfy dependency: org.jboss.tools.site.core raw:4.4.3.'SNAPSHOT'/format(n[.n=0;[.n=0;[-S]]]):4.4.3-SNAPSHOT depends on: org.jboss.tools.common.mylyn.feature.feature.group 0.0.0{code}
So... we need to disconnect this feature, *org.jboss.tools.common.mylyn.feature*, from its dependency on *com.atlassian.connector.eclipse.jira*
PR: https://github.com/jbosstools/jbosstools-base/pull/546
> problem installing atlassian: depends on javax.servlet 3.1.0 -- remove atlassian from Central
> ---------------------------------------------------------------------------------------------
>
> Key: JBDS-4191
> URL: https://issues.jboss.org/browse/JBDS-4191
> Project: Red Hat JBoss Developer Studio (devstudio)
> Issue Type: Sub-task
> Components: central-update, rpm
> Affects Versions: 10.2.0.AM3
> Reporter: Nick Boldt
> Assignee: Nick Boldt
> Fix For: 10.3.0.AM1
>
>
> atlassian: depends on javax.servlet 3.1.0 (via req-bundle on javax.xml.rpc 1.1.0 from c.a.conn.eclipse.jira.core)
> : also depends on org.eclipse.core.runtime.compatibility.auth
> : also depends on mortbay, which breaks because of javax/servlet/Servlet
> {code}
> !MESSAGE Authorization infrastructure (org.eclipse.core.runtime.compatibility.auth) not installed.
> !STACK 0
> java.lang.ClassNotFoundException: org.eclipse.core.internal.runtime.auth.AuthorizationDatabase cannot be found by org.eclipse.core.runtime_3.12.0.v20160920-1429
> at org.eclipse.osgi.internal.loader.BundleLoader.findClassInternal(BundleLoader.java:461)
> at org.eclipse.osgi.internal.loader.BundleLoader.findClass(BundleLoader.java:372)
> at org.eclipse.osgi.internal.loader.BundleLoader.findClass(BundleLoader.java:364)
> at org.eclipse.osgi.internal.loader.ModuleClassLoader.loadClass(ModuleClassLoader.java:161)
> at java.lang.ClassLoader.loadClass(ClassLoader.java:357)
> at java.lang.Class.forName0(Native Method)
> at java.lang.Class.forName(Class.java:264)
> at org.eclipse.core.internal.runtime.AuthorizationHandler.getAuthClass(AuthorizationHandler.java:48)
> at org.eclipse.core.internal.runtime.AuthorizationHandler.loadKeyring(AuthorizationHandler.java:69)
> at org.eclipse.core.internal.runtime.AuthorizationHandler.flushAuthorizationInfo(AuthorizationHandler.java:231)
> at org.eclipse.core.runtime.Platform.flushAuthorizationInfo(Platform.java:590)
> at com.atlassian.connector.eclipse.internal.commons.ui.MigrateToSecureStorageJob.migrateToSecureStorage(MigrateToSecureStorageJob.java:89)
> at com.atlassian.connector.eclipse.internal.commons.ui.MigrateToSecureStorageJob.runInUIThread(MigrateToSecureStorageJob.java:60)
> !ENTRY org.eclipse.core.jobs 4 2 2016-11-17 21:09:30.244
> !MESSAGE An internal error occurred during: "Start Embedded Web Server".
> !STACK 0
> java.lang.LinkageError: loader constraint violation: when resolving method "org.mortbay.jetty.servlet.ServletHolder.<init>(Ljavax/servlet/Servlet;)V" the class loader (instance of org/eclipse/osgi/internal/loader/EquinoxClassLoader) of the current class, com/atlassian/connector/eclipse/internal/directclickthrough/ui/DirectClickThroughUiPlugin$2, and the class loader (instance of org/eclipse/osgi/internal/loader/EquinoxClassLoader) for the method's defining class, org/mortbay/jetty/servlet/ServletHolder, have different Class objects for the type javax/servlet/Servlet used in the signature
> at com.atlassian.connector.eclipse.internal.directclickthrough.ui.DirectClickThroughUiPlugin$2.runImpl(DirectClickThroughUiPlugin.java:88)
> at com.atlassian.connector.eclipse.internal.core.jobs.JobWithStatus.run(JobWithStatus.java:50)
> at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55)
> depends on and installs javax.servlet:
> * com.atlassian.connector.eclipse.bamboo.feature
> * com.atlassian.connector.eclipse.directclickthrough.feature
> * com.atlassian.connector.eclipse.jira.feature
> * com.atlassian.connector.commons.feature -> connector.commons -> javax.xml.rpc 1.1.0 -> javax.servlet 3.1.0
> {code}
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
7 years, 6 months
[JBoss JIRA] (JBDS-4191) problem installing atlassian: depends on javax.servlet 3.1.0 -- remove atlassian from Central
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBDS-4191?page=com.atlassian.jira.plugin.... ]
Nick Boldt updated JBDS-4191:
-----------------------------
Git Pull Request: https://github.com/jbosstools/jbosstools-target-platforms/pull/251, https://github.com/jbosstools/jbosstools-discovery/pull/339, https://github.com/jbosstools/jbosstools-base/pull/546 (was: https://github.com/jbosstools/jbosstools-target-platforms/pull/251, https://github.com/jbosstools/jbosstools-discovery/pull/339)
> problem installing atlassian: depends on javax.servlet 3.1.0 -- remove atlassian from Central
> ---------------------------------------------------------------------------------------------
>
> Key: JBDS-4191
> URL: https://issues.jboss.org/browse/JBDS-4191
> Project: Red Hat JBoss Developer Studio (devstudio)
> Issue Type: Sub-task
> Components: central-update, rpm
> Affects Versions: 10.2.0.AM3
> Reporter: Nick Boldt
> Assignee: Nick Boldt
> Fix For: 10.3.0.AM1
>
>
> atlassian: depends on javax.servlet 3.1.0 (via req-bundle on javax.xml.rpc 1.1.0 from c.a.conn.eclipse.jira.core)
> : also depends on org.eclipse.core.runtime.compatibility.auth
> : also depends on mortbay, which breaks because of javax/servlet/Servlet
> {code}
> !MESSAGE Authorization infrastructure (org.eclipse.core.runtime.compatibility.auth) not installed.
> !STACK 0
> java.lang.ClassNotFoundException: org.eclipse.core.internal.runtime.auth.AuthorizationDatabase cannot be found by org.eclipse.core.runtime_3.12.0.v20160920-1429
> at org.eclipse.osgi.internal.loader.BundleLoader.findClassInternal(BundleLoader.java:461)
> at org.eclipse.osgi.internal.loader.BundleLoader.findClass(BundleLoader.java:372)
> at org.eclipse.osgi.internal.loader.BundleLoader.findClass(BundleLoader.java:364)
> at org.eclipse.osgi.internal.loader.ModuleClassLoader.loadClass(ModuleClassLoader.java:161)
> at java.lang.ClassLoader.loadClass(ClassLoader.java:357)
> at java.lang.Class.forName0(Native Method)
> at java.lang.Class.forName(Class.java:264)
> at org.eclipse.core.internal.runtime.AuthorizationHandler.getAuthClass(AuthorizationHandler.java:48)
> at org.eclipse.core.internal.runtime.AuthorizationHandler.loadKeyring(AuthorizationHandler.java:69)
> at org.eclipse.core.internal.runtime.AuthorizationHandler.flushAuthorizationInfo(AuthorizationHandler.java:231)
> at org.eclipse.core.runtime.Platform.flushAuthorizationInfo(Platform.java:590)
> at com.atlassian.connector.eclipse.internal.commons.ui.MigrateToSecureStorageJob.migrateToSecureStorage(MigrateToSecureStorageJob.java:89)
> at com.atlassian.connector.eclipse.internal.commons.ui.MigrateToSecureStorageJob.runInUIThread(MigrateToSecureStorageJob.java:60)
> !ENTRY org.eclipse.core.jobs 4 2 2016-11-17 21:09:30.244
> !MESSAGE An internal error occurred during: "Start Embedded Web Server".
> !STACK 0
> java.lang.LinkageError: loader constraint violation: when resolving method "org.mortbay.jetty.servlet.ServletHolder.<init>(Ljavax/servlet/Servlet;)V" the class loader (instance of org/eclipse/osgi/internal/loader/EquinoxClassLoader) of the current class, com/atlassian/connector/eclipse/internal/directclickthrough/ui/DirectClickThroughUiPlugin$2, and the class loader (instance of org/eclipse/osgi/internal/loader/EquinoxClassLoader) for the method's defining class, org/mortbay/jetty/servlet/ServletHolder, have different Class objects for the type javax/servlet/Servlet used in the signature
> at com.atlassian.connector.eclipse.internal.directclickthrough.ui.DirectClickThroughUiPlugin$2.runImpl(DirectClickThroughUiPlugin.java:88)
> at com.atlassian.connector.eclipse.internal.core.jobs.JobWithStatus.run(JobWithStatus.java:50)
> at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55)
> depends on and installs javax.servlet:
> * com.atlassian.connector.eclipse.bamboo.feature
> * com.atlassian.connector.eclipse.directclickthrough.feature
> * com.atlassian.connector.eclipse.jira.feature
> * com.atlassian.connector.commons.feature -> connector.commons -> javax.xml.rpc 1.1.0 -> javax.servlet 3.1.0
> {code}
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
7 years, 6 months