[JBoss JIRA] (JBTIS-564) Cannot install Fuse / SwitchYard tooling in offline mode
by Andrej Podhradsky (JIRA)
[ https://issues.jboss.org/browse/JBTIS-564?page=com.atlassian.jira.plugin.... ]
Andrej Podhradsky closed JBTIS-564.
-----------------------------------
Fix Version/s: 9.0.0.Beta1
Resolution: Done
Verified with JBDS 9.1.0.Beta2 + JBDS-IS 9.0.0.Beta1b EA Zip file
> Cannot install Fuse / SwitchYard tooling in offline mode
> --------------------------------------------------------
>
> Key: JBTIS-564
> URL: https://issues.jboss.org/browse/JBTIS-564
> Project: JBoss Tools Integration Stack
> Issue Type: Bug
> Components: distribution
> Affects Versions: 9.0.0.Beta1
> Environment: JBDS 9.1.0.Beta2 + JBDS-IS 9.0.0.Beta1a EA Zip (md5 6ab445b312d39c451802232c5a54846b)
> Reporter: Andrej Podhradsky
> Assignee: Paul Leacu
> Priority: Critical
> Fix For: 9.0.0.Beta1
>
>
> {code}
> Cannot complete the install because one or more required items could not be found.
> Software being installed: SwitchYard BPEL Support 2.1.0.Beta3-v20160226-2057-B645 (org.switchyard.tools.bpel.feature.feature.group 2.1.0.Beta3-v20160226-2057-B645)
> Missing requirement: SwitchYard 2.1.0.Beta3-v20160226-2057-B645 (org.switchyard.tools.feature.feature.group 2.1.0.Beta3-v20160226-2057-B645) requires 'org.eclipse.zest.feature.group [1.5.0,2.0.0)' but it could not be found
> Cannot satisfy dependency:
> From: SwitchYard BPEL Support 2.1.0.Beta3-v20160226-2057-B645 (org.switchyard.tools.bpel.feature.feature.group 2.1.0.Beta3-v20160226-2057-B645)
> To: org.switchyard.tools.feature.feature.group 0.0.0
> {code}
> {code}
> Cannot complete the install because one or more required items could not be found.
> Software being installed: JBoss Fuse Tooling Apache Camel Editor 8.0.0.Beta1-v20160222-1935-B731 (org.fusesource.ide.camel.editor.feature.feature.group 8.0.0.Beta1-v20160222-1935-B731)
> Missing requirement: JBoss Fuse Tooling Apache Camel Editor 8.0.0.Beta1-v20160222-1935-B731 (org.fusesource.ide.camel.editor.feature.feature.group 8.0.0.Beta1-v20160222-1935-B731) requires 'org.eclipse.zest.core 0.0.0' but it could not be found
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 10 months
[JBoss JIRA] (JBIDE-21170) Problems with CDK Adapter resulting from missing PATH in Eclipse on Mac
by Martin Malina (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21170?page=com.atlassian.jira.plugi... ]
Martin Malina commented on JBIDE-21170:
---------------------------------------
[~fbricon], which new PR? https://github.com/jbosstools/jbosstools-openshift/pull/990 ?
That's really strange. It doesn't work for me and Rob eventually found out that what he does cannot work - he checks if the PATH is empty and if so, he will do his magic to get the PATH. But in my case there is a very limited PATH - if I go to launch config -> Environment and click the Select button, I can see this PATH there:
{code}/usr/bin:/bin:/usr/sbin:/sbin{code}
So Rob's code doesn't work for this use case:
{code}
if( existingPath.isEmpty() && pathCommand != null) {
{code}
He'll need to come up with something that works in this scenario.
> Problems with CDK Adapter resulting from missing PATH in Eclipse on Mac
> -----------------------------------------------------------------------
>
> Key: JBIDE-21170
> URL: https://issues.jboss.org/browse/JBIDE-21170
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: cdk
> Affects Versions: 4.3.1.Beta1
> Reporter: Martin Malina
> Assignee: Rob Stryker
> Fix For: 4.3.1.CR1
>
>
> The problem is that CDK tooling relies on PATH to find vagrant. And the "vagrant up" command in turn depends on PATH to find e.g. VBoxManage.
> On Mac, when you start your Eclipse / JBDS as an app by double-clicking an icon on your Desktop or in Finder, the Eclipse instance will have no PATH env variable.
> One workaround is to start your Eclipse from command line by going inside the package:
> {code}
> cd Eclipse.app/Contents/MacOS
> ./eclipse
> {code}
> But this is definitely not the recommended way to start Eclipse - I'm not sure if eclipse.ini is located properly in this case. But at least PATH is correct then.
> There is actually one more workaround. To add your PATH to the Environment tab in Launch config. That works for me.
> So that might be a potential solution to this problem - have a predefined PATH for each OS in case there is none defined in the Eclipse process.
> After I set up a CDK server adapter and fixed the wrong path to vagrant in the launch config, I then started the server adapter and got this:
> Server CDK Server Adapter at localhost failed to start.
> Console:
> {code}
> The provider 'virtualbox' that was requested to back the machine
> 'default' is reporting that it isn't usable on this system. The
> reason is shown below:
> Vagrant could not detect VirtualBox! Make sure VirtualBox is properly installed.
> Vagrant uses the `VBoxManage` binary that ships with VirtualBox, and requires
> this to be available on the PATH. If VirtualBox is installed, please find the
> `VBoxManage` binary and add it to the PATH environmental variable.
> {code}
> Along with this, there was an Unhandled event loop exception in the error view:
> {code}
> org.eclipse.swt.SWTException: Failed to execute runnable (java.lang.NullPointerException)
> 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:4024)
> at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3700)
> 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:654)
> at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:337)
> at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:598)
> 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:520)
> 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)
> Caused by: java.lang.NullPointerException
> at org.jboss.tools.central.editors.GettingStartedHtmlPage.updateEarlyAccess(GettingStartedHtmlPage.java:359)
> at org.jboss.tools.central.editors.GettingStartedHtmlPage.access$14(GettingStartedHtmlPage.java:342)
> at org.jboss.tools.central.editors.GettingStartedHtmlPage$6$1.run(GettingStartedHtmlPage.java:327)
> at org.eclipse.ui.internal.UILockListener.doPendingWork(UILockListener.java:162)
> at org.eclipse.ui.internal.UISynchronizer$3.run(UISynchronizer.java:154)
> at org.eclipse.swt.widgets.RunnableLock.run(RunnableLock.java:35)
> at org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchronizer.java:135)
> ... 23 more
> {code}
> In the command line, VBoxManage is accessible and it is located in /usr/local/bin/ and on my PATH.
> Max suggested I could try to start Eclipse from command line instead of double-clicking in Finder (which is the normal way to do it on Mac) and that helped.
> So for some reason when you start Eclipse using Eclipse.app from Finder, the PATH is incorrect.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 10 months
[JBoss JIRA] (JBDS-3616) Installer is rejecting a valid user account - CDK error is indicated in debugger, but no error is logged
by Jan Richter (JIRA)
[ https://issues.jboss.org/browse/JBDS-3616?page=com.atlassian.jira.plugin.... ]
Jan Richter edited comment on JBDS-3616 at 3/1/16 2:52 AM:
-----------------------------------------------------------
It does not look fixed on our side.
Login success/failure is still determined by a single boolean (so any failed attempt will cause the same output no matter the cause).
And we do not log any login events as of yet.
Edit: Oh, there is a second boolean to check whether or not the T&C have been accepted.
was (Author: jrichter1):
It does not look fixed on our side.
Login success/failure is still determined by a single boolean (so any failed attempt will cause the same output no matter the cause).
And we do not log any login events as of yet.
> Installer is rejecting a valid user account - CDK error is indicated in debugger, but no error is logged
> ---------------------------------------------------------------------------------------------------------
>
> Key: JBDS-3616
> URL: https://issues.jboss.org/browse/JBDS-3616
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Bug
> Components: installer
> Reporter: Len DiMaggio
> Labels: havoc
> Attachments: Screenshot (25).png
>
>
> I have been seeing this problem for several days, both for when the installer is built from source and when the installer is downloaded from: http://machydra.tpb.lab.eng.brq.redhat.com:8080/view/Developer%20Tooling/...
> See the attached screenshot - the user account - that had previously been used successfully - is now being rejected with an error of "invalid account information" - no additional information or error is logged - the install log only contains:
> -----------------------------------------------------------------
> Tue, 26 Jan 2016 18:08:01 GMT-Developer Platform installer v0.0.2
> -----------------------------------------------------------------
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 10 months
[JBoss JIRA] (JBIDE-21737) Error while selecting a project in the OpenShift Explorer view
by Viacheslav Kabanovich (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21737?page=com.atlassian.jira.plugi... ]
Viacheslav Kabanovich commented on JBIDE-21737:
-----------------------------------------------
I reproduced this problem on clean workspace, when JBDS is run without org.jboss.tools.openshift.express.ui plugin. Context org.jboss.tools.openshift.explorer.context.connection is defined in its plugin xml. The definition should be moved to org.jboss.tools.openshift.common.ui plugin.
> Error while selecting a project in the OpenShift Explorer view
> --------------------------------------------------------------
>
> Key: JBIDE-21737
> URL: https://issues.jboss.org/browse/JBIDE-21737
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.3.1.Beta2
> Reporter: Xavier Coulon
> Fix For: 4.3.1.CR1
>
>
> I have the following exception *many times* in the console when I select a project in the OpenShift Explorer view:
> {code}
> org.eclipse.core.commands.common.NotDefinedException: Cannot get the parent identifier from an undefined context. org.jboss.tools.openshift.explorer.context.connection
> at org.eclipse.core.commands.contexts.Context.getParentId(Context.java:197)
> at org.eclipse.e4.ui.bindings.internal.ContextSet$CComp.getLevel(ContextSet.java:49)
> at org.eclipse.e4.ui.bindings.internal.ContextSet$CComp.compare(ContextSet.java:38)
> at org.eclipse.e4.ui.bindings.internal.ContextSet$CComp.compare(ContextSet.java:1)
> at java.util.TimSort.binarySort(TimSort.java:292)
> at java.util.TimSort.sort(TimSort.java:217)
> at java.util.Arrays.sort(Arrays.java:1512)
> at java.util.ArrayList.sort(ArrayList.java:1454)
> at java.util.Collections.sort(Collections.java:175)
> at org.eclipse.e4.ui.bindings.internal.ContextSet.<init>(ContextSet.java:77)
> at org.eclipse.e4.ui.bindings.internal.BindingTableManager.createContextSet(BindingTableManager.java:90)
> at org.eclipse.e4.ui.bindings.internal.BindingServiceImpl.setContextIds(BindingServiceImpl.java:177)
> at sun.reflect.GeneratedMethodAccessor27.invoke(Unknown Source)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:497)
> at org.eclipse.e4.core.internal.di.MethodRequestor.execute(MethodRequestor.java:56)
> at org.eclipse.e4.core.internal.contexts.ContextObjectSupplier$ContextInjectionListener.update(ContextObjectSupplier.java:90)
> at org.eclipse.e4.core.internal.contexts.TrackableComputationExt.update(TrackableComputationExt.java:111)
> at org.eclipse.e4.core.internal.contexts.EclipseContext.processScheduled(EclipseContext.java:341)
> at org.eclipse.e4.core.internal.contexts.EclipseContext.set(EclipseContext.java:356)
> at org.eclipse.e4.ui.internal.services.ContextContextService.activateContext(ContextContextService.java:56)
> at org.eclipse.ui.internal.contexts.ContextService.activateContext(ContextService.java:170)
> at org.eclipse.ui.internal.contexts.ContextService.activateContext(ContextService.java:102)
> at org.jboss.tools.openshift.internal.common.ui.explorer.OpenShiftExplorerView$Contexts.activate(OpenShiftExplorerView.java:201)
> at org.jboss.tools.openshift.internal.common.ui.explorer.OpenShiftExplorerView$OpenShiftExplorerContextsHandler$2.selectionChanged(OpenShiftExplorerView.java:187)
> at org.eclipse.jface.viewers.Viewer$2.run(Viewer.java:163)
> at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42)
> at org.eclipse.ui.internal.JFaceUtil$1.run(JFaceUtil.java:50)
> at org.eclipse.jface.util.SafeRunnable.run(SafeRunnable.java:173)
> at org.eclipse.jface.viewers.Viewer.fireSelectionChanged(Viewer.java:160)
> at org.eclipse.jface.viewers.StructuredViewer.updateSelection(StructuredViewer.java:2197)
> at org.eclipse.jface.viewers.StructuredViewer.handleSelect(StructuredViewer.java:1228)
> at org.eclipse.ui.navigator.CommonViewer.handleSelect(CommonViewer.java:461)
> at org.eclipse.jface.viewers.StructuredViewer$4.widgetSelected(StructuredViewer.java:1257)
> at org.eclipse.jface.util.OpenStrategy.fireSelectionEvent(OpenStrategy.java:242)
> at org.eclipse.jface.util.OpenStrategy.access$4(OpenStrategy.java:236)
> at org.eclipse.jface.util.OpenStrategy$1.handleEvent(OpenStrategy.java:408)
> at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84)
> at org.eclipse.swt.widgets.Display.sendEvent(Display.java:4230)
> at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1491)
> at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1514)
> at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1499)
> at org.eclipse.swt.widgets.Widget.notifyListeners(Widget.java:1299)
> at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:4072)
> at org.eclipse.swt.widgets.Display.applicationNextEventMatchingMask(Display.java:5045)
> at org.eclipse.swt.widgets.Display.applicationProc(Display.java:5432)
> at org.eclipse.swt.internal.cocoa.OS.objc_msgSendSuper(Native Method)
> at org.eclipse.swt.widgets.Widget.callSuper(Widget.java:227)
> at org.eclipse.swt.widgets.Widget.mouseDownSuper(Widget.java:1121)
> at org.eclipse.swt.widgets.Tree.mouseDownSuper(Tree.java:2066)
> at org.eclipse.swt.widgets.Widget.mouseDown(Widget.java:1113)
> at org.eclipse.swt.widgets.Control.mouseDown(Control.java:2571)
> at org.eclipse.swt.widgets.Tree.mouseDown(Tree.java:2034)
> at org.eclipse.swt.widgets.Display.windowProc(Display.java:5692)
> at org.eclipse.swt.internal.cocoa.OS.objc_msgSendSuper(Native Method)
> at org.eclipse.swt.widgets.Widget.callSuper(Widget.java:227)
> at org.eclipse.swt.widgets.Widget.windowSendEvent(Widget.java:2130)
> at org.eclipse.swt.widgets.Shell.windowSendEvent(Shell.java:2337)
> at org.eclipse.swt.widgets.Display.windowProc(Display.java:5756)
> at org.eclipse.swt.internal.cocoa.OS.objc_msgSendSuper(Native Method)
> at org.eclipse.swt.widgets.Display.applicationSendEvent(Display.java:5193)
> at org.eclipse.swt.widgets.Display.applicationProc(Display.java:5342)
> at org.eclipse.swt.internal.cocoa.OS.objc_msgSend(Native Method)
> at org.eclipse.swt.internal.cocoa.NSApplication.sendEvent(NSApplication.java:128)
> at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3695)
> 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)
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 10 months
[JBoss JIRA] (JBDS-3635) Add the ability to detect/select existing dependencies/tools
by Jan Richter (JIRA)
[ https://issues.jboss.org/browse/JBDS-3635?page=com.atlassian.jira.plugin.... ]
Jan Richter commented on JBDS-3635:
-----------------------------------
https://github.com/jrichter1/developer-platform-install/tree/using-existi...
I basically made a proof of concept while waiting for my automated tests to complete, so I wouldn't trust my life on it :)
But it should work to some extent - just to demonstrate the idea.
> Add the ability to detect/select existing dependencies/tools
> ------------------------------------------------------------
>
> Key: JBDS-3635
> URL: https://issues.jboss.org/browse/JBDS-3635
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Feature Request
> Components: installer
> Reporter: Jan Richter
> Labels: havoc
> Attachments: pdkinstaller.png
>
>
> It would be great if the installer allowed the user to use some of the required tools they have already installed.
> The idea is to detect if the dependencies are already present and let the user decide if they want to use them, or install new ones. Also, it could let the user select the tools themselves if they want to use a different installation than detected, etc.
> The confirmation page we currently have looks like the place to put all this, since it already displays most of the stuff that is going to get installed. Anyway, I have tried to modify it and squeeze the controls in and this is how the selection turned out (imagine the messages looking a bit smarter):
> !pdkinstaller.png|thumbnail!
> [~dgolovin] & [~crobson], what's your opinion on this?
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 10 months
[JBoss JIRA] (JBIDE-21798) ExplorerViewTabbedPropertyAdapterFactory is incorrectly referenced in org.jboss.tools.openshift.ui.plugin.xml
by Viacheslav Kabanovich (JIRA)
Viacheslav Kabanovich created JBIDE-21798:
---------------------------------------------
Summary: ExplorerViewTabbedPropertyAdapterFactory is incorrectly referenced in org.jboss.tools.openshift.ui.plugin.xml
Key: JBIDE-21798
URL: https://issues.jboss.org/browse/JBIDE-21798
Project: Tools (JBoss Tools)
Issue Type: Feature Request
Components: openshift
Affects Versions: 4.3.1.Beta2
Reporter: Viacheslav Kabanovich
Fix For: 4.4.0.Alpha1
1. Run JBDS without org.jboss.tools.openshift.express.ui plugin.
2. Open OpenShift Explorer and Properties views.
3. Select a connection.
Tabbed property sheet is not loaded in Properties, and Error log has entry:
{code}
!MESSAGE Plug-in org.jboss.tools.openshift.ui was unable to load class org.jboss.tools.openshift.internal.ui.property.tabbed.ExplorerViewTabbedPropertyAdapterFactory.
!STACK 0
java.lang.ClassNotFoundException: org.jboss.tools.openshift.internal.ui.property.tabbed.ExplorerViewTabbedPropertyAdapterFactory cannot be found by org.jboss.tools.openshift.ui_3.2.0.qualifier
at org.eclipse.osgi.internal.loader.BundleLoader.findClassInternal(BundleLoader.java:444)
at org.eclipse.osgi.internal.loader.BundleLoader.findClass(BundleLoader.java:357)
at org.eclipse.osgi.internal.loader.BundleLoader.findClass(BundleLoader.java:349)
at org.eclipse.osgi.internal.loader.ModuleClassLoader.loadClass(ModuleClassLoader.java:160)
at java.lang.ClassLoader.loadClass(ClassLoader.java:357)
at org.eclipse.osgi.internal.framework.EquinoxBundle.loadClass(EquinoxBundle.java:554)
at org.eclipse.core.internal.registry.osgi.RegistryStrategyOSGI.createExecutableExtension(RegistryStrategyOSGI.java:174)
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.core.internal.adapter.AdapterFactoryProxy.loadFactory(AdapterFactoryProxy.java:136)
at org.eclipse.core.internal.adapter.AdapterFactoryProxy.getAdapter(AdapterFactoryProxy.java:81)
at org.eclipse.core.internal.runtime.AdapterManager.getAdapter(AdapterManager.java:295)
at org.eclipse.ui.part.WorkbenchPart.getAdapter(WorkbenchPart.java:143)
at org.eclipse.ui.navigator.CommonNavigator.getAdapter(CommonNavigator.java:462)
at org.eclipse.core.runtime.Adapters.adapt(Adapters.java:59)
at org.eclipse.core.runtime.Adapters.adapt(Adapters.java:94)
at org.eclipse.ui.views.properties.PropertySheet.doCreatePage(PropertySheet.java:199)
at org.eclipse.ui.part.PageBookView.createPage(PageBookView.java:400)
at org.eclipse.ui.part.PageBookView.partActivated(PageBookView.java:743)
at org.eclipse.ui.views.properties.PropertySheet.partActivated(PropertySheet.java:291)
at org.eclipse.ui.part.PageBookView$4.partActivated(PageBookView.java:1043)
at org.eclipse.ui.internal.WorkbenchPage$15.run(WorkbenchPage.java:4909)
at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42)
at org.eclipse.ui.internal.WorkbenchPage.firePartActivated(WorkbenchPage.java:4906)
at org.eclipse.ui.internal.WorkbenchPage.access$19(WorkbenchPage.java:4885)
at org.eclipse.ui.internal.WorkbenchPage$E4PartListener.partActivated(WorkbenchPage.java:207)
at org.eclipse.e4.ui.internal.workbench.PartServiceImpl$3.run(PartServiceImpl.java:245)
at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42)
at org.eclipse.e4.ui.internal.workbench.PartServiceImpl.firePartActivated(PartServiceImpl.java:242)
at org.eclipse.e4.ui.internal.workbench.PartServiceImpl.activate(PartServiceImpl.java:724)
at org.eclipse.e4.ui.internal.workbench.PartServiceImpl.switchPerspective(PartServiceImpl.java:625)
at org.eclipse.e4.ui.workbench.renderers.swt.PerspectiveStackRenderer.showTab(PerspectiveStackRenderer.java:106)
at org.eclipse.e4.ui.workbench.renderers.swt.LazyStackRenderer.postProcess(LazyStackRenderer.java:103)
at org.eclipse.e4.ui.workbench.renderers.swt.PerspectiveStackRenderer.postProcess(PerspectiveStackRenderer.java:63)
at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.safeCreateGui(PartRenderingEngine.java:670)
at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.safeCreateGui(PartRenderingEngine.java:758)
at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.access$0(PartRenderingEngine.java:729)
at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$2.run(PartRenderingEngine.java:723)
at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42)
at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.createGui(PartRenderingEngine.java:707)
at org.eclipse.e4.ui.workbench.renderers.swt.SWTPartRenderer.processContents(SWTPartRenderer.java:72)
at org.eclipse.e4.ui.workbench.renderers.swt.SashRenderer.processContents(SashRenderer.java:151)
at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.safeCreateGui(PartRenderingEngine.java:666)
at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.safeCreateGui(PartRenderingEngine.java:758)
at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.access$0(PartRenderingEngine.java:729)
at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$2.run(PartRenderingEngine.java:723)
at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42)
at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.createGui(PartRenderingEngine.java:707)
at org.eclipse.e4.ui.workbench.renderers.swt.SWTPartRenderer.processContents(SWTPartRenderer.java:72)
at org.eclipse.e4.ui.workbench.renderers.swt.WBWRenderer.processContents(WBWRenderer.java:614)
at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.safeCreateGui(PartRenderingEngine.java:666)
at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.safeCreateGui(PartRenderingEngine.java:758)
at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.access$0(PartRenderingEngine.java:729)
at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$2.run(PartRenderingEngine.java:723)
at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42)
at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.createGui(PartRenderingEngine.java:707)
at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$4.run(PartRenderingEngine.java:1066)
at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:336)
at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.run(PartRenderingEngine.java:1023)
at org.eclipse.e4.ui.internal.workbench.E4Workbench.createAndRunUI(E4Workbench.java:157)
at org.eclipse.ui.internal.Workbench$5.run(Workbench.java:651)
at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:336)
at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:595)
at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:150)
at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:138)
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:388)
at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:243)
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:498)
at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:670)
at org.eclipse.equinox.launcher.Main.basicRun(Main.java:609)
at org.eclipse.equinox.launcher.Main.run(Main.java:1516)
at org.eclipse.equinox.launcher.Main.main(Main.java:1489)
{code}
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 10 months
[JBoss JIRA] (TOOLSDOC-709) JBDS 9.1 GA: Document a use case for Forge Tooling
by Misha Ali (JIRA)
[ https://issues.jboss.org/browse/TOOLSDOC-709?page=com.atlassian.jira.plug... ]
Misha Ali updated TOOLSDOC-709:
-------------------------------
Sprint: 01-Feb >> 14-Feb 2016-JBDS/JBT, 15-Feb >> 28-Feb 2016-JBDS/JBT, 29-Feb >> 13-Mar 2016-JBDS/JBT (was: 01-Feb >> 14-Feb 2016-JBDS/JBT, 15-Feb >> 28-Feb 2016-JBDS/JBT)
> JBDS 9.1 GA: Document a use case for Forge Tooling
> --------------------------------------------------
>
> Key: TOOLSDOC-709
> URL: https://issues.jboss.org/browse/TOOLSDOC-709
> Project: Documentation for JBoss Tools and Developer Studio
> Issue Type: Enhancement
> Components: General documentation issues
> Affects Versions: 9.1 GA
> Reporter: Misha Ali
> Assignee: Supriya Bharadwaj
> Labels: Forge
> Fix For: 9.1 GA
>
>
> Document a use case for Forge tooling.
> 1. Draft a potential use case for what users may want to do with forge.
> 2. Get review on use case idea from a relevant SME or QE person
> 3. Write an intro and flesh out the use case with relevant screenshots
> 4. Get QE review
> 5. Create upstream and downstream versions of approved content.
> a. Add CSP version to customer portal
> b. Send Misha upstream version
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 10 months
[JBoss JIRA] (TOOLSDOC-696) Support for the CDK in JBDS 9.1.beta1 should be more prominent in the release notes
by Misha Ali (JIRA)
[ https://issues.jboss.org/browse/TOOLSDOC-696?page=com.atlassian.jira.plug... ]
Misha Ali updated TOOLSDOC-696:
-------------------------------
Sprint: 04-Jan >> 17-Jan 2016-JBDS/JBT, 18-Jan >> 31-Jan 2016-JBDS/JBT, 15-Feb >> 28-Feb 2016-JBDS/JBT, 29-Feb >> 13-Mar 2016-JBDS/JBT (was: 04-Jan >> 17-Jan 2016-JBDS/JBT, 18-Jan >> 31-Jan 2016-JBDS/JBT, 15-Feb >> 28-Feb 2016-JBDS/JBT)
> Support for the CDK in JBDS 9.1.beta1 should be more prominent in the release notes
> -----------------------------------------------------------------------------------
>
> Key: TOOLSDOC-696
> URL: https://issues.jboss.org/browse/TOOLSDOC-696
> Project: Documentation for JBoss Tools and Developer Studio
> Issue Type: Bug
> Components: Release Notes
> Affects Versions: 9.1 GA
> Environment: Build Name: 23115, 9.1 Beta1 Release Notes-9.1-Beta1
> Build Date: 18-12-2015 22:13:00
> Topic ID: 44506-773485 [Latest]
> Reporter: Len DiMaggio
> Assignee: Misha Ali
> Labels: CDK
> Fix For: 9.1 GA
>
>
> Title: New Features
> Describe the issue:
> The text describing the new support fo rthe CDK in JBDS 9.1 is correct in the draft release notes:
> '...Integration with Red Hat Container Development Kit: A new server adapter has been added to help start and stop the Red Hat Container Development Kit (CDK), a set of tools meant to quickly set up an OpenShift instance inside a Docker container running inside a virtual machine. While the server adapter itself has limited functionality, it is able to start and stop the CDK virtual machine via its Vagrantfile. Once started, Docker and OpenShift connections should appear in their respective views, allowing the user to quickly create a new OpenShift application and begin developing their AwesomeApp in a highly-replicatable environment...'
> But - I'd suggest that this moved to a more prominent location in the release notes as it is a major reason for the creation of the beta1 release.
> Can we also add a screenshot?
> Suggestions for improvement:
> Additional information:
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 10 months
[JBoss JIRA] (TOOLSDOC-700) JBDS 9.1 Beta2: Additional docker functionality
by Misha Ali (JIRA)
[ https://issues.jboss.org/browse/TOOLSDOC-700?page=com.atlassian.jira.plug... ]
Misha Ali updated TOOLSDOC-700:
-------------------------------
Sprint: 18-Jan >> 31-Jan 2016-JBDS/JBT, 01-Feb >> 14-Feb 2016-JBDS/JBT, 15-Feb >> 28-Feb 2016-JBDS/JBT, 29-Feb >> 13-Mar 2016-JBDS/JBT (was: 18-Jan >> 31-Jan 2016-JBDS/JBT, 01-Feb >> 14-Feb 2016-JBDS/JBT, 15-Feb >> 28-Feb 2016-JBDS/JBT)
> JBDS 9.1 Beta2: Additional docker functionality
> -----------------------------------------------
>
> Key: TOOLSDOC-700
> URL: https://issues.jboss.org/browse/TOOLSDOC-700
> Project: Documentation for JBoss Tools and Developer Studio
> Issue Type: Bug
> Components: General documentation issues
> Affects Versions: 9.1 Beta2
> Reporter: Misha Ali
> Assignee: Misha Ali
> Labels: Docker
>
> Docker (in 9.0.0, adding CDK target and usability improvements):
> - [Server Adapter to start/stop/restart/auto-configure the CDK's Vagrant VM|https://issues.jboss.org/browse/JBIDE-20153]
> - docker run
> - docker build
> - docker logs
> - run/build as launch configurations so users can rerun
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 10 months