[JBoss JIRA] (JBIDE-20531) Expose additional service ports from deploy docker image wizard
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-20531?page=com.atlassian.jira.plugi... ]
Andre Dietisheim updated JBIDE-20531:
-------------------------------------
Labels: docker new_and_noteworthy (was: docker)
> Expose additional service ports from deploy docker image wizard
> ---------------------------------------------------------------
>
> Key: JBIDE-20531
> URL: https://issues.jboss.org/browse/JBIDE-20531
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: openshift
> Affects Versions: 4.3.0.CR1
> Reporter: Jeff Cantrill
> Assignee: Jeff Cantrill
> Labels: docker, new_and_noteworthy
> Fix For: 4.3.1.Beta1
>
> Attachments: PortWindow.png, Service and routing page.png, service port edit dialog.png
>
>
> Allow a user to add ports to a deployment other then just those explicitly exposed on the docker image
> * Also only remove those which were added
> * Only reset those which are defaults
> * Edit via double click
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 3 months
[JBoss JIRA] (JBIDE-20571) OpenShift Explorer: Build/Pod activity should be refreshed automatically
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-20571?page=com.atlassian.jira.plugi... ]
Andre Dietisheim updated JBIDE-20571:
-------------------------------------
Labels: new_and_noteworthy (was: )
> OpenShift Explorer: Build/Pod activity should be refreshed automatically
> ------------------------------------------------------------------------
>
> Key: JBIDE-20571
> URL: https://issues.jboss.org/browse/JBIDE-20571
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: openshift
> Affects Versions: 4.3.0.CR1
> Reporter: Fred Bricon
> Assignee: Jeff Cantrill
> Labels: new_and_noteworthy
> Fix For: 4.3.1.Beta1
>
>
> Currently, when a build is running on openshift, users need to manually refresh the OpenShift Explorer view, to see when a build or a deployment finishes.
> We need to be able to let the explorer "watch" some specific project events (via websockets or some other method).
> As a workaround we might be able to trigger automatic refreshes of the viewer, every 5secs, when we detect a pod is in pending, building, deploying or some other status.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 3 months
[JBoss JIRA] (JBIDE-20571) OpenShift Explorer: Build/Pod activity should be refreshed automatically
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-20571?page=com.atlassian.jira.plugi... ]
Andre Dietisheim closed JBIDE-20571.
------------------------------------
Resolution: Done
re-closing
> OpenShift Explorer: Build/Pod activity should be refreshed automatically
> ------------------------------------------------------------------------
>
> Key: JBIDE-20571
> URL: https://issues.jboss.org/browse/JBIDE-20571
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: openshift
> Affects Versions: 4.3.0.CR1
> Reporter: Fred Bricon
> Assignee: Jeff Cantrill
> Labels: new_and_noteworthy
> Fix For: 4.3.1.Beta1
>
>
> Currently, when a build is running on openshift, users need to manually refresh the OpenShift Explorer view, to see when a build or a deployment finishes.
> We need to be able to let the explorer "watch" some specific project events (via websockets or some other method).
> As a workaround we might be able to trigger automatic refreshes of the viewer, every 5secs, when we detect a pod is in pending, building, deploying or some other status.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 3 months
[JBoss JIRA] (JBIDE-21336) CDK cannot locate VBoxManage on MacOSX
by Alexey Kazakov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21336?page=com.atlassian.jira.plugi... ]
Alexey Kazakov resolved JBIDE-21336.
------------------------------------
Fix Version/s: 4.3.1.Beta2
Assignee: Rob Stryker
Resolution: Duplicate Issue
> CDK cannot locate VBoxManage on MacOSX
> --------------------------------------
>
> Key: JBIDE-21336
> URL: https://issues.jboss.org/browse/JBIDE-21336
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.3.1.Beta1
> Reporter: Xavier Coulon
> Assignee: Rob Stryker
> Fix For: 4.3.1.Beta2
>
>
> I get the following error message when starting the CDK Server Adapter on MacOSX (DevStudio was started from the dock, not from CLI):
> {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}
> when starting DevStudio from CLI, it inherits from the terminal PATH and then it works.
> We had a similar issue in Docker tooling ('docker-machine' needs to be in the PATH, as well as 'VBoxManage' or any other VM driver) so we ended up adding some preferences to set the correct path.
> That might be interesting to see how the Docker tooling, the Vagrant tooling and the CDK tooling could use the same preferences.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 3 months
[JBoss JIRA] (JBIDE-21336) CDK cannot locate VBoxManage on MacOSX
by Alexey Kazakov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21336?page=com.atlassian.jira.plugi... ]
Alexey Kazakov commented on JBIDE-21336:
----------------------------------------
It's a duplicate of JBIDE-21170, isn't it?
> CDK cannot locate VBoxManage on MacOSX
> --------------------------------------
>
> Key: JBIDE-21336
> URL: https://issues.jboss.org/browse/JBIDE-21336
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.3.1.Beta1
> Reporter: Xavier Coulon
>
> I get the following error message when starting the CDK Server Adapter on MacOSX (DevStudio was started from the dock, not from CLI):
> {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}
> when starting DevStudio from CLI, it inherits from the terminal PATH and then it works.
> We had a similar issue in Docker tooling ('docker-machine' needs to be in the PATH, as well as 'VBoxManage' or any other VM driver) so we ended up adding some preferences to set the correct path.
> That might be interesting to see how the Docker tooling, the Vagrant tooling and the CDK tooling could use the same preferences.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 3 months
[JBoss JIRA] (JBIDE-21200) Plug-in "org.jboss.tools.vpe" was unable to instantiate class "org.jboss.tools.vpe.editor.menu.SetupTemplateContributionItem
by Pavol Srna (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21200?page=com.atlassian.jira.plugi... ]
Pavol Srna closed JBIDE-21200.
------------------------------
Verified in jbds 9.1.0.Beta1 B189 build
> Plug-in "org.jboss.tools.vpe" was unable to instantiate class "org.jboss.tools.vpe.editor.menu.SetupTemplateContributionItem
> ----------------------------------------------------------------------------------------------------------------------------
>
> Key: JBIDE-21200
> URL: https://issues.jboss.org/browse/JBIDE-21200
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: visual-page-editor-core
> Affects Versions: 4.3.0.Beta1
> Environment: Mac OS
> Reporter: Pavol Srna
> Assignee: Konstantin Marmalyukov
> Fix For: 4.3.1.Beta1
>
>
> 1. Create JSF 1.2 Kick Start project
> 2. Open inputUserName.jsp in VPE
> 3. Right Click on 'user' text within <h:inputText> tag
> {code}
> org.eclipse.core.runtime.CoreException: Plug-in "org.jboss.tools.vpe" was unable to instantiate class "org.jboss.tools.vpe.editor.menu.SetupTemplateContributionItem".
> at org.eclipse.core.internal.registry.osgi.RegistryStrategyOSGI.throwException(RegistryStrategyOSGI.java:194)
> at org.eclipse.core.internal.registry.osgi.RegistryStrategyOSGI.createExecutableExtension(RegistryStrategyOSGI.java:186)
> 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:872)
> at org.eclipse.ui.internal.menus.DynamicMenuContributionItem.createContributionItem(DynamicMenuContributionItem.java:234)
> at org.eclipse.ui.internal.menus.DynamicMenuContributionItem.getContributionItem(DynamicMenuContributionItem.java:227)
> at org.eclipse.ui.internal.menus.DynamicMenuContributionItem.fill(DynamicMenuContributionItem.java:206)
> at org.eclipse.jface.action.MenuManager.doItemFill(MenuManager.java:724)
> at org.eclipse.jface.action.MenuManager.update(MenuManager.java:806)
> at org.eclipse.jface.action.MenuManager.update(MenuManager.java:665)
> at org.eclipse.e4.ui.workbench.renderers.swt.MenuManagerRenderer.scheduleManagerUpdate(MenuManagerRenderer.java:1164)
> at org.eclipse.e4.ui.workbench.renderers.swt.MenuManagerRenderer.processContents(MenuManagerRenderer.java:636)
> at org.eclipse.e4.ui.workbench.renderers.swt.MenuManagerRenderer.subscribeTopicChildAdded(MenuManagerRenderer.java:313)
> at sun.reflect.GeneratedMethodAccessor24.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.ui.internal.di.UIEventObjectSupplier$UIEventHandler$1.run(UIEventObjectSupplier.java:56)
> at org.eclipse.swt.widgets.Synchronizer.syncExec(Synchronizer.java:186)
> at org.eclipse.ui.internal.UISynchronizer.syncExec(UISynchronizer.java:145)
> at org.eclipse.swt.widgets.Display.syncExec(Display.java:4781)
> at org.eclipse.e4.ui.internal.workbench.swt.E4Application$1.syncExec(E4Application.java:211)
> at org.eclipse.e4.ui.internal.di.UIEventObjectSupplier$UIEventHandler.handleEvent(UIEventObjectSupplier.java:53)
> at org.eclipse.equinox.internal.event.EventHandlerWrapper.handleEvent(EventHandlerWrapper.java:197)
> at org.eclipse.equinox.internal.event.EventHandlerTracker.dispatchEvent(EventHandlerTracker.java:197)
> at org.eclipse.equinox.internal.event.EventHandlerTracker.dispatchEvent(EventHandlerTracker.java:1)
> at org.eclipse.osgi.framework.eventmgr.EventManager.dispatchEvent(EventManager.java:230)
> at org.eclipse.osgi.framework.eventmgr.ListenerQueue.dispatchEventSynchronous(ListenerQueue.java:148)
> at org.eclipse.equinox.internal.event.EventAdminImpl.dispatchEvent(EventAdminImpl.java:135)
> at org.eclipse.equinox.internal.event.EventAdminImpl.sendEvent(EventAdminImpl.java:78)
> at org.eclipse.equinox.internal.event.EventComponent.sendEvent(EventComponent.java:39)
> at org.eclipse.e4.ui.services.internal.events.EventBroker.send(EventBroker.java:85)
> at org.eclipse.e4.ui.internal.workbench.UIEventPublisher.notifyChanged(UIEventPublisher.java:59)
> at org.eclipse.emf.common.notify.impl.BasicNotifierImpl.eNotify(BasicNotifierImpl.java:374)
> at org.eclipse.emf.ecore.util.EcoreEList.dispatchNotification(EcoreEList.java:249)
> at org.eclipse.emf.common.notify.impl.NotifyingListImpl.addUnique(NotifyingListImpl.java:356)
> at org.eclipse.emf.common.util.AbstractEList.add(AbstractEList.java:341)
> at org.eclipse.e4.ui.workbench.renderers.swt.ContributionRecord.mergeIntoModel(ContributionRecord.java:250)
> at org.eclipse.e4.ui.workbench.renderers.swt.MenuManagerRenderer.processAddition(MenuManagerRenderer.java:554)
> at org.eclipse.e4.ui.workbench.renderers.swt.MenuManagerRenderer.generateContributions(MenuManagerRenderer.java:529)
> at org.eclipse.e4.ui.workbench.renderers.swt.MenuManagerRenderer.processContributions(MenuManagerRenderer.java:494)
> at org.eclipse.ui.internal.PopupMenuExtender.addMenuContributions(PopupMenuExtender.java:409)
> at org.eclipse.ui.internal.PopupMenuExtender.menuAboutToShow(PopupMenuExtender.java:381)
> at org.eclipse.jface.action.MenuManager.fireAboutToShow(MenuManager.java:333)
> at org.eclipse.jface.action.MenuManager.handleAboutToShow(MenuManager.java:466)
> at org.eclipse.jface.action.MenuManager.access$1(MenuManager.java:461)
> at org.eclipse.jface.action.MenuManager$2.menuShown(MenuManager.java:493)
> at org.eclipse.swt.widgets.TypedListener.handleEvent(TypedListener.java:255)
> 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:1495)
> at org.eclipse.swt.widgets.Menu.menuWillOpen(Menu.java:811)
> at org.eclipse.swt.widgets.Display.windowProc(Display.java:5746)
> at org.eclipse.swt.internal.cocoa.OS.objc_msgSend(Native Method)
> at org.eclipse.swt.internal.cocoa.NSMenu.popUpContextMenu(NSMenu.java:77)
> at org.eclipse.swt.widgets.Menu._setVisible(Menu.java:280)
> at org.eclipse.swt.widgets.Display.runPopups(Display.java:4149)
> at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3691)
> 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: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)
> Caused by: java.lang.NullPointerException
> at org.jboss.tools.vpe.editor.menu.SetupTemplateContributionItem.<init>(SetupTemplateContributionItem.java:55)
> 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 java.lang.Class.newInstance(Class.java:442)
> at org.eclipse.core.internal.registry.osgi.RegistryStrategyOSGI.createExecutableExtension(RegistryStrategyOSGI.java:184)
> ... 81 more
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 3 months
[JBoss JIRA] (JBIDE-21214) Domain modification via Credential preferences page doesn't work
by Vlado Pakan (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21214?page=com.atlassian.jira.plugi... ]
Vlado Pakan commented on JBIDE-21214:
-------------------------------------
Is this going to JBDS 9.1.0.Beta1 respin-a if so please add label respin-a. I can't verify it because no PR is linked and therefore I can't check to which branch fix was pushed
> Domain modification via Credential preferences page doesn't work
> ----------------------------------------------------------------
>
> Key: JBIDE-21214
> URL: https://issues.jboss.org/browse/JBIDE-21214
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: common/jst/core
> Affects Versions: 4.3.1.Beta1
> Environment: Fedora 22 KDE 64 bit
> Reporter: Vlado Pakan
> Assignee: Rob Stryker
> Fix For: 4.3.1.Beta1
>
>
> 1. Open Window > Preferences > JBoss Tools > Creddentials
> 2. Add Domain
> 3. Modify domain via Edit button and choose OK
> ERROR: Domain is not modified it shows previous domain name in prefences page
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 3 months
[JBoss JIRA] (JBIDE-21339) Domain modification via Credential preferences page doesn't work
by Vlado Pakan (JIRA)
Vlado Pakan created JBIDE-21339:
-----------------------------------
Summary: Domain modification via Credential preferences page doesn't work
Key: JBIDE-21339
URL: https://issues.jboss.org/browse/JBIDE-21339
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: common/jst/core
Affects Versions: 4.3.1.Beta1
Environment: Fedora 22 KDE 64 bit
Reporter: Vlado Pakan
Assignee: Rob Stryker
Fix For: 4.3.1.Beta1, 4.4.0.Alpha1
1. Open Window > Preferences > JBoss Tools > Creddentials
2. Add Domain
3. Modify domain via Edit button and choose OK
ERROR: Domain is not modified it shows previous domain name in prefences page
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 3 months