[JBoss JIRA] (JBIDE-22923) ClassCastException in InsertContributionItem.<init>
by Ilya Buziuk (JIRA)
[ https://issues.jboss.org/browse/JBIDE-22923?page=com.atlassian.jira.plugi... ]
Ilya Buziuk updated JBIDE-22923:
--------------------------------
Fix Version/s: LATER
> ClassCastException in InsertContributionItem.<init>
> ---------------------------------------------------
>
> Key: JBIDE-22923
> URL: https://issues.jboss.org/browse/JBIDE-22923
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: visual-page-editor-core
> Reporter: Automated Error Reporting Bot
> Assignee: Ilya Buziuk
> Fix For: LATER
>
>
> The following problem was reported via the automated error reporting:
> Message: Class load Failure: 'org.jboss.tools.vpe.editor.menu.InsertContributionItem'
> {noformat}
> java.lang.ClassCastException: org.jboss.tools.jst.jsp.jspeditor.JSPMultiPageEditor cannot be cast to org.jboss.tools.jst.web.ui.internal.editor.jspeditor.JSPMultiPageEditor
> at org.jboss.tools.vpe.editor.menu.InsertContributionItem.<init>(InsertContributionItem.java:73)
> at org.jboss.tools.vpe.editor.menu.InsertContributionItem.<init>(InsertContributionItem.java:63)
> at sun.reflect.NativeConstructorAccessorImpl.newInstance0(NativeConstructorAccessorImpl.java:-2)
> at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:62)
> at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
> at java.lang.reflect.Constructor.newInstance(Constructor.java:423)
> at java.lang.Class.newInstance(Class.java:442)
> at org.eclipse.core.internal.registry.osgi.RegistryStrategyOSGI.createExecutableExtension(RegistryStrategyOSGI.java:184)
> at org.eclipse.core.internal.registry.ExtensionRegistry.createExecutableExtension(ExtensionRegistry.java:905)
> at org.eclipse.core.internal.registry.ConfigurationElement.createExecutableExtension(ConfigurationElement.java:243)
> at org.eclipse.core.internal.registry.ConfigurationElementHandle.createExecutableExtension(ConfigurationElementHandle.java:55)
> at org.eclipse.ui.internal.util.Util.safeLoadExecutableExtension(Util.java:812)
> at org.eclipse.ui.internal.menus.DynamicMenuContributionItem.createContributionItem(DynamicMenuContributionItem.java:166)
> at org.eclipse.ui.internal.menus.DynamicMenuContributionItem.getContributionItem(DynamicMenuContributionItem.java:159)
> at org.eclipse.ui.internal.menus.DynamicMenuContributionItem.fill(DynamicMenuContributionItem.java:145)
> at org.eclipse.jface.action.MenuManager.doItemFill(MenuManager.java:728)
> at org.eclipse.jface.action.MenuManager.update(MenuManager.java:810)
> at org.eclipse.jface.action.MenuManager.update(MenuManager.java:669)
> at org.eclipse.e4.ui.workbench.renderers.swt.MenuManagerRenderer.scheduleManagerUpdate(MenuManagerRenderer.java:1185)
> at org.eclipse.e4.ui.workbench.renderers.swt.MenuManagerRenderer.processContents(MenuManagerRenderer.java:648)
> at org.eclipse.e4.ui.workbench.renderers.swt.MenuManagerRenderer.subscribeTopicChildAdded(MenuManagerRenderer.java:319)
> at sun.reflect.GeneratedMethodAccessor.invoke(null:-1)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:498)
> at org.eclipse.e4.core.internal.di.MethodRequestor.execute(MethodRequestor.java:54)
> {noformat}
> Bundles:
> | org.eclipse.e4.core.di | 1.5.0.v20150421-2214 | 1.6.0.v20160319-0612 |
> | org.eclipse.e4.ui.workbench.renderers.swt | 0.13.0.v20150603-0857 | 0.14.0.v20160525-0940 |
> | org.eclipse.jface | 3.11.0.v20150602-1400 | 3.12.0.v20160518-1929 |
> | org.eclipse.ui | 3.107.0.v20150507-1945 | 3.108.0.v20160518-1929 |
> | org.jboss.tools.vpe | 3.7.1.Final-v20160331-0327-B91 | 3.8.0.Final-v20160609-2229-B3 |
> Operating Systems:
> | Linux | 4.4.0 | 4.4.0 |
> | Windows | 6.1.0 | 6.1.0 |
> The above information is a snapshot of the collected data. Visit [this page|https://redhat.ctrlflow.com/reviewers/#!/problems/57977d33e4b0300861...] for the latest data.
> Thank you for your assistance.
> Your friendly error-reports-inbox.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 7 months
[JBoss JIRA] (JBIDE-22923) ClassCastException in InsertContributionItem.<init>
by Ilya Buziuk (JIRA)
[ https://issues.jboss.org/browse/JBIDE-22923?page=com.atlassian.jira.plugi... ]
Ilya Buziuk reassigned JBIDE-22923:
-----------------------------------
Assignee: Ilya Buziuk
> ClassCastException in InsertContributionItem.<init>
> ---------------------------------------------------
>
> Key: JBIDE-22923
> URL: https://issues.jboss.org/browse/JBIDE-22923
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: visual-page-editor-core
> Reporter: Automated Error Reporting Bot
> Assignee: Ilya Buziuk
>
> The following problem was reported via the automated error reporting:
> Message: Class load Failure: 'org.jboss.tools.vpe.editor.menu.InsertContributionItem'
> {noformat}
> java.lang.ClassCastException: org.jboss.tools.jst.jsp.jspeditor.JSPMultiPageEditor cannot be cast to org.jboss.tools.jst.web.ui.internal.editor.jspeditor.JSPMultiPageEditor
> at org.jboss.tools.vpe.editor.menu.InsertContributionItem.<init>(InsertContributionItem.java:73)
> at org.jboss.tools.vpe.editor.menu.InsertContributionItem.<init>(InsertContributionItem.java:63)
> at sun.reflect.NativeConstructorAccessorImpl.newInstance0(NativeConstructorAccessorImpl.java:-2)
> at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:62)
> at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
> at java.lang.reflect.Constructor.newInstance(Constructor.java:423)
> at java.lang.Class.newInstance(Class.java:442)
> at org.eclipse.core.internal.registry.osgi.RegistryStrategyOSGI.createExecutableExtension(RegistryStrategyOSGI.java:184)
> at org.eclipse.core.internal.registry.ExtensionRegistry.createExecutableExtension(ExtensionRegistry.java:905)
> at org.eclipse.core.internal.registry.ConfigurationElement.createExecutableExtension(ConfigurationElement.java:243)
> at org.eclipse.core.internal.registry.ConfigurationElementHandle.createExecutableExtension(ConfigurationElementHandle.java:55)
> at org.eclipse.ui.internal.util.Util.safeLoadExecutableExtension(Util.java:812)
> at org.eclipse.ui.internal.menus.DynamicMenuContributionItem.createContributionItem(DynamicMenuContributionItem.java:166)
> at org.eclipse.ui.internal.menus.DynamicMenuContributionItem.getContributionItem(DynamicMenuContributionItem.java:159)
> at org.eclipse.ui.internal.menus.DynamicMenuContributionItem.fill(DynamicMenuContributionItem.java:145)
> at org.eclipse.jface.action.MenuManager.doItemFill(MenuManager.java:728)
> at org.eclipse.jface.action.MenuManager.update(MenuManager.java:810)
> at org.eclipse.jface.action.MenuManager.update(MenuManager.java:669)
> at org.eclipse.e4.ui.workbench.renderers.swt.MenuManagerRenderer.scheduleManagerUpdate(MenuManagerRenderer.java:1185)
> at org.eclipse.e4.ui.workbench.renderers.swt.MenuManagerRenderer.processContents(MenuManagerRenderer.java:648)
> at org.eclipse.e4.ui.workbench.renderers.swt.MenuManagerRenderer.subscribeTopicChildAdded(MenuManagerRenderer.java:319)
> at sun.reflect.GeneratedMethodAccessor.invoke(null:-1)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:498)
> at org.eclipse.e4.core.internal.di.MethodRequestor.execute(MethodRequestor.java:54)
> {noformat}
> Bundles:
> | org.eclipse.e4.core.di | 1.5.0.v20150421-2214 | 1.6.0.v20160319-0612 |
> | org.eclipse.e4.ui.workbench.renderers.swt | 0.13.0.v20150603-0857 | 0.14.0.v20160525-0940 |
> | org.eclipse.jface | 3.11.0.v20150602-1400 | 3.12.0.v20160518-1929 |
> | org.eclipse.ui | 3.107.0.v20150507-1945 | 3.108.0.v20160518-1929 |
> | org.jboss.tools.vpe | 3.7.1.Final-v20160331-0327-B91 | 3.8.0.Final-v20160609-2229-B3 |
> Operating Systems:
> | Linux | 4.4.0 | 4.4.0 |
> | Windows | 6.1.0 | 6.1.0 |
> The above information is a snapshot of the collected data. Visit [this page|https://redhat.ctrlflow.com/reviewers/#!/problems/57977d33e4b0300861...] for the latest data.
> Thank you for your assistance.
> Your friendly error-reports-inbox.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 7 months
[JBoss JIRA] (JBIDE-22925) SWTException below VpeEditorPart.setFocus (thrown in Widget.checkWidget)
by Ilya Buziuk (JIRA)
[ https://issues.jboss.org/browse/JBIDE-22925?page=com.atlassian.jira.plugi... ]
Ilya Buziuk reassigned JBIDE-22925:
-----------------------------------
Assignee: Ilya Buziuk
> SWTException below VpeEditorPart.setFocus (thrown in Widget.checkWidget)
> ------------------------------------------------------------------------
>
> Key: JBIDE-22925
> URL: https://issues.jboss.org/browse/JBIDE-22925
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: visual-page-editor-core
> Affects Versions: 4.4.x
> Reporter: Automated Error Reporting Bot
> Assignee: Ilya Buziuk
>
> The following problem was reported via the automated error reporting:
> Message: Error setting focus to : org.eclipse.e4.ui.model.application.ui.basic.impl.PartImpl index.jsp
> {noformat}
> org.eclipse.swt.SWTException: Widget is disposed
> at org.eclipse.swt.widgets.Widget.checkWidget(Widget.java:354)
> at org.eclipse.swt.widgets.Control.setFocus(Control.java:3354)
> at org.eclipse.swt.widgets.Composite.setFocus(Composite.java:1056)
> at org.eclipse.swt.widgets.Composite.setFocus(Composite.java:1056)
> at org.eclipse.ui.texteditor.StatusTextEditor.setFocus(StatusTextEditor.java:120)
> at org.jboss.tools.vpe.editor.VpeEditorPart.setFocus(VpeEditorPart.java:870)
> at org.jboss.tools.jst.web.ui.internal.editor.jspeditor.JSPMultiPageEditorPart.setFocus(JSPMultiPageEditorPart.java:186)
> at org.jboss.tools.jst.web.ui.internal.editor.jspeditor.JSPMultiPageEditorPart.setFocus(JSPMultiPageEditorPart.java:171)
> at org.eclipse.ui.internal.e4.compatibility.CompatibilityPart.delegateSetFocus(CompatibilityPart.java:204)
> at sun.reflect.GeneratedMethodAccessor.invoke(null:-1)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(null:-1)
> at java.lang.reflect.Method.invoke(null:-1)
> at org.eclipse.e4.core.internal.di.MethodRequestor.execute(MethodRequestor.java:56)
> {noformat}
> Bundles:
> | org.eclipse.e4.core.di | 1.5.0.v20150421-2214 | 1.6.0.v20160319-0612 |
> | org.eclipse.swt | 3.104.2.v20160212-1350 | 3.105.0.v20160603-0902 |
> | org.eclipse.ui | 3.107.0.v20150507-1945 | 3.108.0.v20160518-1929 |
> | org.jboss.tools.jst.web.ui | 3.7.1.Final-v20160331-0256-B96 | 3.8.0.Final-v20160609-2146-B2 |
> | org.jboss.tools.vpe | 3.7.1.Final-v20160331-0327-B91 | 3.8.0.Final-v20160609-2229-B3 |
> Operating Systems:
> | Linux | 3.19.0 | 4.6.0 |
> | Windows | 6.1.0 | 10.0.0 |
> The above information is a snapshot of the collected data. Visit [this page|https://redhat.ctrlflow.com/reviewers/#!/problems/571d229ce4b0e9dd9c...] for the latest data.
> Thank you for your assistance.
> Your friendly error-reports-inbox.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 7 months
[JBoss JIRA] (JBIDE-23022) "Unable to initializa some runtime paths" error when detecting seam runtimes.
by Radim Hopp (JIRA)
Radim Hopp created JBIDE-23022:
----------------------------------
Summary: "Unable to initializa some runtime paths" error when detecting seam runtimes.
Key: JBIDE-23022
URL: https://issues.jboss.org/browse/JBIDE-23022
Project: Tools (JBoss Tools)
Issue Type: Feature Request
Components: runtime-detection
Affects Versions: 4.4.1.AM3
Environment: Devstudio 10.1.0.AM3-v20160819-0530-B5800
Reporter: Radim Hopp
Detecting seam runtime causes "Unable to initializa some runtime paths" error. I have tried seam 2.1.2 and seam 2.3.1.Final.
The same is happening when downloading these runtimes via runtime detection.
There is "All runtime detectors failed to initialize jboss-seam-2.3.1.Final" message in error log. Nothing more.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 7 months
[JBoss JIRA] (JBIDE-23008) openshift.cdk.feature.source missing from JBT site; causes baseline check to fail
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-23008?page=com.atlassian.jira.plugi... ]
Andre Dietisheim edited comment on JBIDE-23008 at 8/19/16 6:38 AM:
-------------------------------------------------------------------
[~nickboldt] in [#1288|https://github.com/jbosstools/jbosstools-openshift/pull/1288] you in the cdk feature moved the openshift feature from *<includes>* -> *<requires>*. This made the build blue again?
was (Author: adietish):
[~nickboldt] in [#1288|https://github.com/jbosstools/jbosstools-openshift/pull/1288] you moved the openshift feature *<includes>* -> *<requires>* in the cdk feature. This made the thing blue again?
> openshift.cdk.feature.source missing from JBT site; causes baseline check to fail
> ---------------------------------------------------------------------------------
>
> Key: JBIDE-23008
> URL: https://issues.jboss.org/browse/JBIDE-23008
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: build, openshift, updatesite
> Affects Versions: 4.4.1.AM3
> Reporter: Nick Boldt
> Assignee: Nick Boldt
> Fix For: 4.4.1.Final
>
>
> Since the weekend (after I published an AM3 build into /neon/staging/updates/):
> {code}
> [INFO] --- tycho-source-plugin:0.25.0:plugin-source (plugin-source) @ org.jboss.tools.openshift.cdk.server ---
> [INFO] Building jar: /Users/fbricon/Dev/projects/jbosstools-openshift/plugins/org.jboss.tools.openshift.cdk.server/target/org.jboss.tools.openshift.cdk.server-3.3.0-SNAPSHOT-sources.jar
> [INFO]
> [INFO] --- target-platform-configuration:0.25.0:target-platform (default-target-platform) @ org.jboss.tools.openshift.cdk.server ---
> [INFO]
> [INFO] --- tycho-packaging-plugin:0.25.0:package-plugin (default-package-plugin) @ org.jboss.tools.openshift.cdk.server ---
> [INFO] Building jar: /Users/fbricon/Dev/projects/jbosstools-openshift/plugins/org.jboss.tools.openshift.cdk.server/target/org.jboss.tools.openshift.cdk.server-3.3.0-SNAPSHOT.jar
> [INFO]
> [INFO] --- tycho-p2-plugin:0.25.0:p2-metadata-default (default-p2-metadata-default) @ org.jboss.tools.openshift.cdk.server ---
> [WARNING] MavenProject: org.jboss.tools.openshift.plugins:org.jboss.tools.openshift.cdk.server:3.3.0-SNAPSHOT @ /Users/fbricon/Dev/projects/jbosstools-openshift/plugins/org.jboss.tools.openshift.cdk.server/pom.xml: baseline and build artifacts have same version but different contents
> [INFO] MavenProject: org.jboss.tools.openshift.plugins:org.jboss.tools.openshift.cdk.server:3.3.0-SNAPSHOT @ /Users/fbricon/Dev/projects/jbosstools-openshift/plugins/org.jboss.tools.openshift.cdk.server/pom.xml
> The main artifact has been replaced with the baseline version.
> The following attached artifacts are not present in the baseline and have been removed: [sources]{code}
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 7 months
[JBoss JIRA] (JBIDE-23008) openshift.cdk.feature.source missing from JBT site; causes baseline check to fail
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-23008?page=com.atlassian.jira.plugi... ]
Andre Dietisheim edited comment on JBIDE-23008 at 8/19/16 6:37 AM:
-------------------------------------------------------------------
[~nickboldt] in [#1288|https://github.com/jbosstools/jbosstools-openshift/pull/1288] you moved the openshift feature *<includes>* -> *<requires>* in the cdk feature. This made the thing blue again?
was (Author: adietish):
[~nickboldt] in [#1288|https://github.com/jbosstools/jbosstools-openshift/pull/1288] you moved the openshift feature <includes> -> <requires> in the cdk feature. This made the thing blue again?
> openshift.cdk.feature.source missing from JBT site; causes baseline check to fail
> ---------------------------------------------------------------------------------
>
> Key: JBIDE-23008
> URL: https://issues.jboss.org/browse/JBIDE-23008
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: build, openshift, updatesite
> Affects Versions: 4.4.1.AM3
> Reporter: Nick Boldt
> Assignee: Nick Boldt
> Fix For: 4.4.1.Final
>
>
> Since the weekend (after I published an AM3 build into /neon/staging/updates/):
> {code}
> [INFO] --- tycho-source-plugin:0.25.0:plugin-source (plugin-source) @ org.jboss.tools.openshift.cdk.server ---
> [INFO] Building jar: /Users/fbricon/Dev/projects/jbosstools-openshift/plugins/org.jboss.tools.openshift.cdk.server/target/org.jboss.tools.openshift.cdk.server-3.3.0-SNAPSHOT-sources.jar
> [INFO]
> [INFO] --- target-platform-configuration:0.25.0:target-platform (default-target-platform) @ org.jboss.tools.openshift.cdk.server ---
> [INFO]
> [INFO] --- tycho-packaging-plugin:0.25.0:package-plugin (default-package-plugin) @ org.jboss.tools.openshift.cdk.server ---
> [INFO] Building jar: /Users/fbricon/Dev/projects/jbosstools-openshift/plugins/org.jboss.tools.openshift.cdk.server/target/org.jboss.tools.openshift.cdk.server-3.3.0-SNAPSHOT.jar
> [INFO]
> [INFO] --- tycho-p2-plugin:0.25.0:p2-metadata-default (default-p2-metadata-default) @ org.jboss.tools.openshift.cdk.server ---
> [WARNING] MavenProject: org.jboss.tools.openshift.plugins:org.jboss.tools.openshift.cdk.server:3.3.0-SNAPSHOT @ /Users/fbricon/Dev/projects/jbosstools-openshift/plugins/org.jboss.tools.openshift.cdk.server/pom.xml: baseline and build artifacts have same version but different contents
> [INFO] MavenProject: org.jboss.tools.openshift.plugins:org.jboss.tools.openshift.cdk.server:3.3.0-SNAPSHOT @ /Users/fbricon/Dev/projects/jbosstools-openshift/plugins/org.jboss.tools.openshift.cdk.server/pom.xml
> The main artifact has been replaced with the baseline version.
> The following attached artifacts are not present in the baseline and have been removed: [sources]{code}
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 7 months
[JBoss JIRA] (JBIDE-23008) openshift.cdk.feature.source missing from JBT site; causes baseline check to fail
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-23008?page=com.atlassian.jira.plugi... ]
Andre Dietisheim commented on JBIDE-23008:
------------------------------------------
[~nickboldt] in [#1288|https://github.com/jbosstools/jbosstools-openshift/pull/1288] you moved the openshift feature <includes> -> <requires> in the cdk feature. This made the thing blue again?
> openshift.cdk.feature.source missing from JBT site; causes baseline check to fail
> ---------------------------------------------------------------------------------
>
> Key: JBIDE-23008
> URL: https://issues.jboss.org/browse/JBIDE-23008
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: build, openshift, updatesite
> Affects Versions: 4.4.1.AM3
> Reporter: Nick Boldt
> Assignee: Nick Boldt
> Fix For: 4.4.1.Final
>
>
> Since the weekend (after I published an AM3 build into /neon/staging/updates/):
> {code}
> [INFO] --- tycho-source-plugin:0.25.0:plugin-source (plugin-source) @ org.jboss.tools.openshift.cdk.server ---
> [INFO] Building jar: /Users/fbricon/Dev/projects/jbosstools-openshift/plugins/org.jboss.tools.openshift.cdk.server/target/org.jboss.tools.openshift.cdk.server-3.3.0-SNAPSHOT-sources.jar
> [INFO]
> [INFO] --- target-platform-configuration:0.25.0:target-platform (default-target-platform) @ org.jboss.tools.openshift.cdk.server ---
> [INFO]
> [INFO] --- tycho-packaging-plugin:0.25.0:package-plugin (default-package-plugin) @ org.jboss.tools.openshift.cdk.server ---
> [INFO] Building jar: /Users/fbricon/Dev/projects/jbosstools-openshift/plugins/org.jboss.tools.openshift.cdk.server/target/org.jboss.tools.openshift.cdk.server-3.3.0-SNAPSHOT.jar
> [INFO]
> [INFO] --- tycho-p2-plugin:0.25.0:p2-metadata-default (default-p2-metadata-default) @ org.jboss.tools.openshift.cdk.server ---
> [WARNING] MavenProject: org.jboss.tools.openshift.plugins:org.jboss.tools.openshift.cdk.server:3.3.0-SNAPSHOT @ /Users/fbricon/Dev/projects/jbosstools-openshift/plugins/org.jboss.tools.openshift.cdk.server/pom.xml: baseline and build artifacts have same version but different contents
> [INFO] MavenProject: org.jboss.tools.openshift.plugins:org.jboss.tools.openshift.cdk.server:3.3.0-SNAPSHOT @ /Users/fbricon/Dev/projects/jbosstools-openshift/plugins/org.jboss.tools.openshift.cdk.server/pom.xml
> The main artifact has been replaced with the baseline version.
> The following attached artifacts are not present in the baseline and have been removed: [sources]{code}
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 7 months
[JBoss JIRA] (JBDS-4010) DevSuite installer should check if virtualization extension is enabled
by Denis Golovin (JIRA)
[ https://issues.jboss.org/browse/JBDS-4010?page=com.atlassian.jira.plugin.... ]
Denis Golovin updated JBDS-4010:
--------------------------------
> DevSuite installer should check if virtualization extension is enabled
> ----------------------------------------------------------------------
>
> Key: JBDS-4010
> URL: https://issues.jboss.org/browse/JBDS-4010
> Project: Red Hat JBoss Developer Studio (devstudio)
> Issue Type: Feature Request
> Components: platform-installer
> Reporter: Denis Golovin
> Fix For: 10.2.0.AM1
>
>
> Oracle Virtualbox wont work w/o virtualization enabled in BIOS, so we should tell people to enable it for virtualbox to work after installation. Fortunately there is easy way to check it with powershell under windows.
> {code}PS C:\Users\eskimo> Get-WmiObject -class win32_processor -Property "VirtualizationFirmwareEnabled","SecondLevelAddressTr
> anslationExtensions"
> __GENUS : 2
> __CLASS : Win32_Processor
> __SUPERCLASS :
> __DYNASTY :
> __RELPATH :
> __PROPERTY_COUNT : 2
> __DERIVATION : {}
> __SERVER :
> __NAMESPACE :
> __PATH :
> SecondLevelAddressTranslationExtensions : True
> VirtualizationFirmwareEnabled : True
> PSComputerName :{code}
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 7 months
[JBoss JIRA] (JBDS-4010) DevSuite installer should check if virtualization extension is enabled
by CDW Engine (JIRA)
[ https://issues.jboss.org/browse/JBDS-4010?page=com.atlassian.jira.plugin.... ]
CDW Engine updated JBDS-4010:
-----------------------------
> DevSuite installer should check if virtualization extension is enabled
> ----------------------------------------------------------------------
>
> Key: JBDS-4010
> URL: https://issues.jboss.org/browse/JBDS-4010
> Project: Red Hat JBoss Developer Studio (devstudio)
> Issue Type: Feature Request
> Components: platform-installer
> Reporter: Denis Golovin
> Fix For: 10.2.0.AM1
>
>
> Oracle Virtualbox wont work w/o virtualization enabled in BIOS, so we should tell people to enable it for virtualbox to work after installation. Fortunately there is easy way to check it with powershell under windows.
> {code}PS C:\Users\eskimo> Get-WmiObject -class win32_processor -Property "VirtualizationFirmwareEnabled","SecondLevelAddressTr
> anslationExtensions"
> __GENUS : 2
> __CLASS : Win32_Processor
> __SUPERCLASS :
> __DYNASTY :
> __RELPATH :
> __PROPERTY_COUNT : 2
> __DERIVATION : {}
> __SERVER :
> __NAMESPACE :
> __PATH :
> SecondLevelAddressTranslationExtensions : True
> VirtualizationFirmwareEnabled : True
> PSComputerName :{code}
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 7 months