[JBoss JIRA] (JBDS-3633) Uninstaller does nothing
by Eric D. Schabell (JIRA)
[ https://issues.jboss.org/browse/JBDS-3633?page=com.atlassian.jira.plugin.... ]
Eric D. Schabell commented on JBDS-3633:
----------------------------------------
I have added some install steps to my cdk-install-demo that checks if an install has been previously run and cleans up the vagrant enough to ensure that everything starts for the user, no matter how many times you run the install scripts. I have one for unix and windows, here is the unix version:
https://github.com/eschabell/cdk-install-demo/blob/master/init.sh
See lines 131 onwards for the steps I use to clean it up and put it in a state that will always start for the user.
> Uninstaller does nothing
> ------------------------
>
> Key: JBDS-3633
> URL: https://issues.jboss.org/browse/JBDS-3633
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Feature Request
> Components: installer
> Reporter: Denis Golovin
> Assignee: Denis Golovin
> Labels: havoc
> Fix For: 9.1.0.GA
>
>
> Current implementation just removes record about installation from windows registry.
> What it should do:
> 1. Remove virtual box from vagrant:
> {code}vagrant box remove cdk_v2{code}
> 2. Remove virtual machine from virtual box
> {code}vboxmanage --unregister ${vmname}{code}
> 3. Uninstall what was installed:
> vargant
> virtual box
> developer studio
> 4. Delete:
> CDK
> Open JDK 8
> 5. Cleanup PATH env variable
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years
[JBoss JIRA] (JBIDE-21910) Cannot start Forge 3.0.1 runtime - Windows
by Pavol Srna (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21910?page=com.atlassian.jira.plugi... ]
Pavol Srna commented on JBIDE-21910:
------------------------------------
There are 3 error beiing thrown:
1)
{code}
java.lang.reflect.InvocationTargetException
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:497)
at org.jboss.forge.furnace.proxy.ClassLoaderAdapterCallback$2.call(ClassLoaderAdapterCallback.java:124)
at org.jboss.forge.furnace.util.ClassLoaders.executeIn(ClassLoaders.java:42)
at org.jboss.forge.furnace.proxy.ClassLoaderAdapterCallback.invoke(ClassLoaderAdapterCallback.java:97)
at org.javassist.tmp.java.util.Iterator_$$_javassist_b7dab253-0bc2-4f7e-bb23-eb255727489e.next(Iterator_$$_javassist_b7dab253-0bc2-4f7e-bb23-eb255727489e.java)
at org.jboss.tools.forge.core.furnace.FurnaceRuntime.getAllCandidatesAsMap(FurnaceRuntime.java:157)
at org.jboss.tools.forge.core.furnace.FurnaceRuntime.start(FurnaceRuntime.java:92)
at org.jboss.tools.forge.ui.util.ForgeHelper$1.runInWorkspace(ForgeHelper.java:52)
at org.eclipse.core.internal.resources.InternalWorkspaceJob.run(InternalWorkspaceJob.java:39)
at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55)
Caused by: java.lang.LinkageError: loader constraint violation: when resolving method "org.slf4j.impl.StaticLoggerBinder.getLoggerFactory()Lorg/slf4j/ILoggerFactory;" the class loader (instance of org/jboss/modules/ModuleClassLoader) of the current class, org/slf4j/LoggerFactory, and the class loader (instance of org/jboss/modules/ModuleClassLoader) for the method's defining class, org/slf4j/impl/StaticLoggerBinder, have different Class objects for the type org/slf4j/ILoggerFactory used in the signature
at org.slf4j.LoggerFactory.getILoggerFactory(LoggerFactory.java:335)
at org.slf4j.LoggerFactory.getLogger(LoggerFactory.java:283)
at org.slf4j.LoggerFactory.getLogger(LoggerFactory.java:304)
at io.fabric8.kubernetes.api.KubernetesHelper.<clinit>(KubernetesHelper.java:123)
at io.fabric8.forge.kubernetes.AbstractKubernetesCommand.<clinit>(AbstractKubernetesCommand.java:45)
at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:62)
at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
at java.lang.reflect.Constructor.newInstance(Constructor.java:422)
at org.jboss.weld.injection.ConstructorInjectionPoint.newInstance(ConstructorInjectionPoint.java:119)
at org.jboss.weld.injection.ConstructorInjectionPoint.invokeAroundConstructCallbacks(ConstructorInjectionPoint.java:92)
at org.jboss.weld.injection.ConstructorInjectionPoint.newInstance(ConstructorInjectionPoint.java:78)
at org.jboss.weld.injection.producer.AbstractInstantiator.newInstance(AbstractInstantiator.java:28)
at org.jboss.weld.injection.producer.BasicInjectionTarget.produce(BasicInjectionTarget.java:116)
at org.jboss.weld.injection.producer.BeanInjectionTarget.produce(BeanInjectionTarget.java:180)
at org.jboss.weld.bean.ManagedBean.create(ManagedBean.java:158)
at org.jboss.weld.context.unbound.DependentContextImpl.get(DependentContextImpl.java:70)
at org.jboss.weld.bean.ContextualInstanceStrategy$DefaultContextualInstanceStrategy.get(ContextualInstanceStrategy.java:101)
at org.jboss.weld.bean.ContextualInstance.get(ContextualInstance.java:50)
at org.jboss.weld.manager.BeanManagerImpl.getReference(BeanManagerImpl.java:742)
at org.jboss.weld.manager.BeanManagerImpl.getReference(BeanManagerImpl.java:765)
at org.jboss.forge.furnace.container.cdi.services.ExportedInstanceImpl$1.call(ExportedInstanceImpl.java:64)
at org.jboss.forge.furnace.util.ClassLoaders.executeIn(ClassLoaders.java:42)
at org.jboss.forge.furnace.container.cdi.services.ExportedInstanceImpl.get(ExportedInstanceImpl.java:72)
at org.jboss.forge.furnace.impl.addons.ImportedImpl$ImportedIteratorImpl.next(ImportedImpl.java:182)
... 13 more
Root exception:
java.lang.LinkageError: loader constraint violation: when resolving method "org.slf4j.impl.StaticLoggerBinder.getLoggerFactory()Lorg/slf4j/ILoggerFactory;" the class loader (instance of org/jboss/modules/ModuleClassLoader) of the current class, org/slf4j/LoggerFactory, and the class loader (instance of org/jboss/modules/ModuleClassLoader) for the method's defining class, org/slf4j/impl/StaticLoggerBinder, have different Class objects for the type org/slf4j/ILoggerFactory used in the signature
at org.slf4j.LoggerFactory.getILoggerFactory(LoggerFactory.java:335)
at org.slf4j.LoggerFactory.getLogger(LoggerFactory.java:283)
at org.slf4j.LoggerFactory.getLogger(LoggerFactory.java:304)
at io.fabric8.kubernetes.api.KubernetesHelper.<clinit>(KubernetesHelper.java:123)
at io.fabric8.forge.kubernetes.AbstractKubernetesCommand.<clinit>(AbstractKubernetesCommand.java:45)
at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:62)
at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
at java.lang.reflect.Constructor.newInstance(Constructor.java:422)
at org.jboss.weld.injection.ConstructorInjectionPoint.newInstance(ConstructorInjectionPoint.java:119)
at org.jboss.weld.injection.ConstructorInjectionPoint.invokeAroundConstructCallbacks(ConstructorInjectionPoint.java:92)
at org.jboss.weld.injection.ConstructorInjectionPoint.newInstance(ConstructorInjectionPoint.java:78)
at org.jboss.weld.injection.producer.AbstractInstantiator.newInstance(AbstractInstantiator.java:28)
at org.jboss.weld.injection.producer.BasicInjectionTarget.produce(BasicInjectionTarget.java:116)
at org.jboss.weld.injection.producer.BeanInjectionTarget.produce(BeanInjectionTarget.java:180)
at org.jboss.weld.bean.ManagedBean.create(ManagedBean.java:158)
at org.jboss.weld.context.unbound.DependentContextImpl.get(DependentContextImpl.java:70)
at org.jboss.weld.bean.ContextualInstanceStrategy$DefaultContextualInstanceStrategy.get(ContextualInstanceStrategy.java:101)
at org.jboss.weld.bean.ContextualInstance.get(ContextualInstance.java:50)
at org.jboss.weld.manager.BeanManagerImpl.getReference(BeanManagerImpl.java:742)
at org.jboss.weld.manager.BeanManagerImpl.getReference(BeanManagerImpl.java:765)
at org.jboss.forge.furnace.container.cdi.services.ExportedInstanceImpl$1.call(ExportedInstanceImpl.java:64)
at org.jboss.forge.furnace.util.ClassLoaders.executeIn(ClassLoaders.java:42)
at org.jboss.forge.furnace.container.cdi.services.ExportedInstanceImpl.get(ExportedInstanceImpl.java:72)
at org.jboss.forge.furnace.impl.addons.ImportedImpl$ImportedIteratorImpl.next(ImportedImpl.java:182)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:497)
at org.jboss.forge.furnace.proxy.ClassLoaderAdapterCallback$2.call(ClassLoaderAdapterCallback.java:124)
at org.jboss.forge.furnace.util.ClassLoaders.executeIn(ClassLoaders.java:42)
at org.jboss.forge.furnace.proxy.ClassLoaderAdapterCallback.invoke(ClassLoaderAdapterCallback.java:97)
at org.javassist.tmp.java.util.Iterator_$$_javassist_b7dab253-0bc2-4f7e-bb23-eb255727489e.next(Iterator_$$_javassist_b7dab253-0bc2-4f7e-bb23-eb255727489e.java)
at org.jboss.tools.forge.core.furnace.FurnaceRuntime.getAllCandidatesAsMap(FurnaceRuntime.java:157)
at org.jboss.tools.forge.core.furnace.FurnaceRuntime.start(FurnaceRuntime.java:92)
at org.jboss.tools.forge.ui.util.ForgeHelper$1.runInWorkspace(ForgeHelper.java:52)
at org.eclipse.core.internal.resources.InternalWorkspaceJob.run(InternalWorkspaceJob.java:39)
at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55)
{code}
2)
{code}
java.lang.reflect.InvocationTargetException
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:497)
at org.jboss.forge.furnace.proxy.ClassLoaderInterceptor$1.call(ClassLoaderInterceptor.java:87)
at org.jboss.forge.furnace.util.ClassLoaders.executeIn(ClassLoaders.java:42)
at org.jboss.forge.furnace.proxy.ClassLoaderInterceptor.invoke(ClassLoaderInterceptor.java:103)
at org.jboss.forge.addon.ui.impl.command.CommandFactoryImpl_$$_javassist_aa202be3-3b5b-43e2-847a-55476f89ea35.getCommands(CommandFactoryImpl_$$_javassist_aa202be3-3b5b-43e2-847a-55476f89ea35.java)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:497)
at org.jboss.forge.furnace.proxy.ClassLoaderAdapterCallback$2.call(ClassLoaderAdapterCallback.java:124)
at org.jboss.forge.furnace.util.ClassLoaders.executeIn(ClassLoaders.java:42)
at org.jboss.forge.furnace.proxy.ClassLoaderAdapterCallback.invoke(ClassLoaderAdapterCallback.java:97)
at org.jboss.forge.addon.ui.command.CommandFactory_$$_javassist_146336be-6c29-4373-9c7b-f8a358646f45.getCommands(CommandFactory_$$_javassist_146336be-6c29-4373-9c7b-f8a358646f45.java)
at org.jboss.tools.forge.ui.internal.ext.dialog.WizardDialogHelper.getAllCandidatesAsList(WizardDialogHelper.java:62)
at org.jboss.tools.forge.ui.internal.ext.dialog.UICommandListDialog.getProviders(UICommandListDialog.java:255)
at org.jboss.tools.forge.ui.internal.ext.dialog.UICommandListDialog.access$1(UICommandListDialog.java:251)
at org.jboss.tools.forge.ui.internal.ext.dialog.UICommandListDialog$1.run(UICommandListDialog.java:202)
at org.eclipse.swt.custom.BusyIndicator.showWhile(BusyIndicator.java:70)
at org.jboss.tools.forge.ui.internal.ext.dialog.UICommandListDialog.createDialogArea(UICommandListDialog.java:191)
at org.eclipse.jface.dialogs.PopupDialog.createContents(PopupDialog.java:690)
at org.eclipse.jface.window.Window.create(Window.java:430)
at org.eclipse.jface.dialogs.PopupDialog.open(PopupDialog.java:1134)
at org.jboss.tools.forge.ui.internal.ext.handlers.ForgeCommandHandler$1.lambda$0(ForgeCommandHandler.java:56)
at org.eclipse.swt.widgets.RunnableLock.run(RunnableLock.java:35)
at org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchronizer.java:135)
at org.eclipse.swt.widgets.Display.runAsyncMessages(Display.java:4155)
at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3772)
at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$4.run(PartRenderingEngine.java:1127)
at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:337)
at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.run(PartRenderingEngine.java:1018)
at org.eclipse.e4.ui.internal.workbench.E4Workbench.createAndRunUI(E4Workbench.java:156)
at org.eclipse.ui.internal.Workbench$5.run(Workbench.java:694)
at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:337)
at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:606)
at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:150)
at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:139)
at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:196)
at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:134)
at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:104)
at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:380)
at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:235)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:497)
at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:669)
at org.eclipse.equinox.launcher.Main.basicRun(Main.java:608)
at org.eclipse.equinox.launcher.Main.run(Main.java:1515)
at org.eclipse.equinox.launcher.Main.main(Main.java:1488)
Caused by: java.lang.NoClassDefFoundError: Could not initialize class io.fabric8.forge.kubernetes.PodInfo
at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:62)
at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
at java.lang.reflect.Constructor.newInstance(Constructor.java:422)
at org.jboss.weld.injection.ConstructorInjectionPoint.newInstance(ConstructorInjectionPoint.java:119)
at org.jboss.weld.injection.ConstructorInjectionPoint.invokeAroundConstructCallbacks(ConstructorInjectionPoint.java:92)
at org.jboss.weld.injection.ConstructorInjectionPoint.newInstance(ConstructorInjectionPoint.java:78)
at org.jboss.weld.injection.producer.AbstractInstantiator.newInstance(AbstractInstantiator.java:28)
at org.jboss.weld.injection.producer.BasicInjectionTarget.produce(BasicInjectionTarget.java:116)
at org.jboss.weld.injection.producer.BeanInjectionTarget.produce(BeanInjectionTarget.java:180)
at org.jboss.weld.bean.ManagedBean.create(ManagedBean.java:158)
at org.jboss.weld.context.unbound.DependentContextImpl.get(DependentContextImpl.java:70)
at org.jboss.weld.bean.ContextualInstanceStrategy$DefaultContextualInstanceStrategy.get(ContextualInstanceStrategy.java:101)
at org.jboss.weld.bean.ContextualInstance.get(ContextualInstance.java:50)
at org.jboss.weld.manager.BeanManagerImpl.getReference(BeanManagerImpl.java:742)
at org.jboss.weld.manager.BeanManagerImpl.getReference(BeanManagerImpl.java:765)
at org.jboss.forge.furnace.container.cdi.services.ExportedInstanceImpl$1.call(ExportedInstanceImpl.java:64)
at org.jboss.forge.furnace.util.ClassLoaders.executeIn(ClassLoaders.java:42)
at org.jboss.forge.furnace.container.cdi.services.ExportedInstanceImpl.get(ExportedInstanceImpl.java:72)
at org.jboss.forge.furnace.impl.addons.ImportedImpl$ImportedIteratorImpl.next(ImportedImpl.java:182)
at org.jboss.forge.addon.ui.impl.command.CommandFactoryImpl.getCommands(CommandFactoryImpl.java:189)
at org.jboss.forge.addon.ui.impl.command.CommandFactoryImpl.getCachedCommands(CommandFactoryImpl.java:166)
at org.jboss.forge.addon.ui.impl.command.CommandFactoryImpl.getCommands(CommandFactoryImpl.java:56)
... 52 more
{code}
3)
{code}
rg.eclipse.swt.SWTException: Failed to execute runnable (java.lang.IllegalArgumentException: Argument cannot be null)
at org.eclipse.swt.SWT.error(SWT.java:4491)
at org.eclipse.swt.SWT.error(SWT.java:4406)
at org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchronizer.java:138)
at org.eclipse.swt.widgets.Display.runAsyncMessages(Display.java:4155)
at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3772)
at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$4.run(PartRenderingEngine.java:1127)
at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:337)
at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.run(PartRenderingEngine.java:1018)
at org.eclipse.e4.ui.internal.workbench.E4Workbench.createAndRunUI(E4Workbench.java:156)
at org.eclipse.ui.internal.Workbench$5.run(Workbench.java:694)
at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:337)
at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:606)
at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:150)
at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:139)
at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:196)
at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:134)
at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:104)
at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:380)
at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:235)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:497)
at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:669)
at org.eclipse.equinox.launcher.Main.basicRun(Main.java:608)
at org.eclipse.equinox.launcher.Main.run(Main.java:1515)
at org.eclipse.equinox.launcher.Main.main(Main.java:1488)
Caused by: java.lang.IllegalArgumentException: Argument cannot be null
at org.eclipse.swt.SWT.error(SWT.java:4472)
at org.eclipse.swt.SWT.error(SWT.java:4406)
at org.eclipse.swt.SWT.error(SWT.java:4377)
at org.eclipse.swt.widgets.Widget.error(Widget.java:482)
at org.eclipse.swt.widgets.Label.setText(Label.java:395)
at org.jboss.tools.forge.ui.notifications.NotificationDialog.createMessage(NotificationDialog.java:125)
at org.jboss.tools.forge.ui.notifications.NotificationDialog.createClientComposite(NotificationDialog.java:102)
at org.jboss.tools.forge.ui.notifications.NotificationDialog.<init>(NotificationDialog.java:64)
at org.jboss.tools.forge.ui.notifications.NotificationDialog.notify(NotificationDialog.java:37)
at org.jboss.tools.forge.ui.internal.ForgeUIPlugin$1.run(ForgeUIPlugin.java:65)
at org.eclipse.swt.widgets.RunnableLock.run(RunnableLock.java:35)
at org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchronizer.java:135)
... 24 more
{code}
> Cannot start Forge 3.0.1 runtime - Windows
> ------------------------------------------
>
> Key: JBIDE-21910
> URL: https://issues.jboss.org/browse/JBIDE-21910
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: forge
> Affects Versions: 4.3.1.CR1
> Environment: windows
> Reporter: Pavol Srna
> Assignee: George Gastaldi
> Priority: Blocker
> Fix For: 4.3.1.CR1
>
> Attachments: forge-err-xIUnMqLO.png
>
>
> An internal error occurred during: "Starting JBoss Forge 3.0.1.Final"
> java.lang.reflect.InvocationTargetException
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years
[JBoss JIRA] (JBIDE-21920) Cannot use features which are using oc binary
by Marián Labuda (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21920?page=com.atlassian.jira.plugi... ]
Marián Labuda commented on JBIDE-21920:
---------------------------------------
I am running latest nightly build of JBT (B240).
ASSERT: Have an OpenShift 3 connection in OpenShift explorer view.
EXEC: Create a new application on the connection.
ASSERT: Application is running and there is application pod.
EXEC: Set path to oc binary in OpenShift 3 preference page.
EXEC: Try to open application pod logs via context menu of application pod in OpenShift Explorer view.
RESULT: Error message is shown in console and no pod log is displayed.
EXPECTED RESULT: Pod log is shown in console.
> Cannot use features which are using oc binary
> ---------------------------------------------
>
> Key: JBIDE-21920
> URL: https://issues.jboss.org/browse/JBIDE-21920
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.3.1.CR1
> Reporter: Marián Labuda
> Priority: Blocker
> Labels: openshift_v3
> Fix For: 4.3.1.CR1
>
>
> After latest update of nightly JBT I am not able to get logs from pods(/builds) or work with server adapter, because there is something wrong with setting oc path. When I set path on OpenShift 3 preference page to be pointing to correct oc binary, following e.g. getting log from pod results in showing following message in console
> {code}
> The OpenShift 'oc' binary location was not specified. Set the property openshift.restclient.oc.location
> {code}
> There is no stack trace available for this error in error log.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years
[JBoss JIRA] (JBIDE-21920) Cannot use features which are using oc binary
by Marián Labuda (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21920?page=com.atlassian.jira.plugi... ]
Marián Labuda edited comment on JBIDE-21920 at 3/21/16 9:13 AM:
----------------------------------------------------------------
I am running latest nightly build of JBT (B240). Tried it on fresh installation as well as on updated JBT to latest nightly.
ASSERT: Have an OpenShift 3 connection in OpenShift explorer view.
EXEC: Create a new application on the connection.
ASSERT: Application is running and there is application pod.
EXEC: Set path to oc binary in OpenShift 3 preference page.
EXEC: Try to open application pod logs via context menu of application pod in OpenShift Explorer view.
RESULT: Error message is shown in console and no pod log is displayed.
EXPECTED RESULT: Pod log is shown in console.
was (Author: mlabuda):
I am running latest nightly build of JBT (B240).
ASSERT: Have an OpenShift 3 connection in OpenShift explorer view.
EXEC: Create a new application on the connection.
ASSERT: Application is running and there is application pod.
EXEC: Set path to oc binary in OpenShift 3 preference page.
EXEC: Try to open application pod logs via context menu of application pod in OpenShift Explorer view.
RESULT: Error message is shown in console and no pod log is displayed.
EXPECTED RESULT: Pod log is shown in console.
> Cannot use features which are using oc binary
> ---------------------------------------------
>
> Key: JBIDE-21920
> URL: https://issues.jboss.org/browse/JBIDE-21920
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.3.1.CR1
> Reporter: Marián Labuda
> Priority: Blocker
> Labels: openshift_v3
> Fix For: 4.3.1.CR1
>
>
> After latest update of nightly JBT I am not able to get logs from pods(/builds) or work with server adapter, because there is something wrong with setting oc path. When I set path on OpenShift 3 preference page to be pointing to correct oc binary, following e.g. getting log from pod results in showing following message in console
> {code}
> The OpenShift 'oc' binary location was not specified. Set the property openshift.restclient.oc.location
> {code}
> There is no stack trace available for this error in error log.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years
[JBoss JIRA] (JBTIS-602) Fix creating a SY project with intpkg
by Brian Fitzpatrick (JIRA)
[ https://issues.jboss.org/browse/JBTIS-602?page=com.atlassian.jira.plugin.... ]
Brian Fitzpatrick edited comment on JBTIS-602 at 3/21/16 9:10 AM:
------------------------------------------------------------------
Andrej, we'll need a lot more here. Can you provide additional details? Or is this a QE-only issue?
was (Author: bfitzpat):
Andrej, we'll need a lot more here. Can you provide additional details?
> Fix creating a SY project with intpkg
> -------------------------------------
>
> Key: JBTIS-602
> URL: https://issues.jboss.org/browse/JBTIS-602
> Project: JBoss Tools Integration Stack
> Issue Type: Task
> Components: QE, switchyard
> Affects Versions: 4.2.6.CR1
> Reporter: Andrej Podhradsky
> Assignee: Andrej Podhradsky
>
> The problem is that the behaviour depends eclipse base (luna or mars)
> - detect correct runtime label
> - get rid of switchyard vs integration version
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years