[JBoss JIRA] (JBIDE-19795) Bower support
by Ilya Buziuk (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19795?page=com.atlassian.jira.plugi... ]
Ilya Buziuk commented on JBIDE-19795:
-------------------------------------
Adding UI for "Bower Init" launch shortcut: https://github.com/jbosstools/jbosstools-jst/pull/493
Here is the demo video with complete use case of bower tools - https://vimeo.com/132219215
> Bower support
> -------------
>
> Key: JBIDE-19795
> URL: https://issues.jboss.org/browse/JBIDE-19795
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: javascript
> Affects Versions: 4.3.0.Alpha2
> Reporter: Ilya Buziuk
> Assignee: Ilya Buziuk
> Labels: new_and_noteworthy
> Fix For: 4.3.0.Final
>
>
> Need to have initial [Bower|http://bower.io/] tools support:
> *The gist*
> Bower tooling should initially support several bower API commands :
> |Command||Description|
> | *bower init* |creates a *bower.json* file|
> |*bower install <package>*|installs packages to *bower_components* folder|
> |*bower uninstall <package>*|uninstalls a package locally from *bower_components* directory|
> |*bower update* |updates installed packages to their newest version according to *bower.json*|
> Basically, the main idea of the implementation is the following:
> Eclipse plugin that will execute *external* bower commands - implementation will fall back on *native* bower installation via *ILaunchConfiguration*
> Native bower tools must be preinstalled
> *The main questions & proposals:*
> 1. https://github.com/jbosstools/jbosstools-playground is probably the best place for initial implementation of bower stuff (infrastructure / build etc.)
> 2. UI. should it be ILaunchShortcuts ("bower init" / "bower update" etc.) + launch configuration enabled for projects with js nature?
> 3. Implementation details:
> - the way of detecting bower? Should user point to it's installation dir and this location will be used for IExternalToolConstants.ATTR_LOCATION (windows case: *\user\AppData\Roaming\npm\node_modules\bower* )
> - if bower was not detected / installed - "Error message with a link to the bower website with installation details depending on the platform"
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 9 months
[JBoss JIRA] (JBIDE-19990) "See JBoss Tools Visual Editor FAQ" link is not working.
by Konstantin Marmalyukov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19990?page=com.atlassian.jira.plugi... ]
Konstantin Marmalyukov commented on JBIDE-19990:
------------------------------------------------
I'm surprised you are able to reproduce this issue, it works fine for me. Haven't you done any tricks with your system removing Firefox(or any other browser) from default system web browser?
> "See JBoss Tools Visual Editor FAQ" link is not working.
> --------------------------------------------------------
>
> Key: JBIDE-19990
> URL: https://issues.jboss.org/browse/JBIDE-19990
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: central, visual-page-editor-core
> Affects Versions: 4.3.0.Beta1
> Reporter: Radim Hopp
> Assignee: Radim Hopp
> Fix For: 4.3.0.Beta2
>
>
> When the browser cannot be instantiated, error is shown and on the bottom of the editor is "See JBoss Tools Visual Editor FAQ" link (see here: http://i.imgur.com/F2l9Hgi.png).
> This link is not working. Clicking on it just writes into console, from where JBDS/JBT was started, this:
> _env: /home/rhopp/http:/tools.jboss.org/documentation/faq/visualeditor.html: Directory or file does not exist_
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 9 months
[JBoss JIRA] (JBIDE-20166) Application wizard: Cannot create OpenShift v3 application from default template ruby-sample-helloworld
by Jeff Cantrill (JIRA)
[ https://issues.jboss.org/browse/JBIDE-20166?page=com.atlassian.jira.plugi... ]
Jeff Cantrill commented on JBIDE-20166:
---------------------------------------
[~mlabuda] Using the latest code on master (which I think matches the nightly at the moment), I am unable to reproduce this issue. Investigated the null pointer and it doesn't appear that this is possible given the restclient always returns a Map. I'll modify the code to return gracefully at the given point but I think maybe we just have a difference in code. If you can reproduce or provide even more detailed steps, please reopen the issue.
> Application wizard: Cannot create OpenShift v3 application from default template ruby-sample-helloworld
> -------------------------------------------------------------------------------------------------------
>
> Key: JBIDE-20166
> URL: https://issues.jboss.org/browse/JBIDE-20166
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.3.0.Beta2
> Reporter: Marián Labuda
> Assignee: Jeff Cantrill
> Priority: Critical
> Labels: application_wizard, openshift_v3
> Fix For: 4.3.0.Beta2
>
>
> All resources, except buildconfig, are created for a new application from OpenShift v3 template ruby-sample-helloworld which is on OpenShift v3 server. While proceeding through wizard, there is a NPE invoked once "openshift" tree item in the wizard is selected.
> {code}
> java.lang.RuntimeException: java.lang.NullPointerException
> at org.eclipse.core.internal.databinding.beans.BeanPropertyHelper.writeProperty(BeanPropertyHelper.java:65)
> at org.eclipse.core.internal.databinding.beans.BeanValueProperty.doSetValue(BeanValueProperty.java:54)
> at org.eclipse.core.databinding.property.value.ValueProperty.setValue(ValueProperty.java:85)
> at org.eclipse.core.internal.databinding.property.value.SimplePropertyObservableValue.doSetValue(SimplePropertyObservableValue.java:111)
> at org.eclipse.core.databinding.observable.value.AbstractObservableValue.setValue(AbstractObservableValue.java:58)
> at org.eclipse.core.databinding.observable.value.DecoratingObservableValue.setValue(DecoratingObservableValue.java:111)
> at org.eclipse.core.databinding.observable.value.DecoratingObservableValue.setValue(DecoratingObservableValue.java:111)
> at org.eclipse.core.databinding.UpdateValueStrategy.doSet(UpdateValueStrategy.java:487)
> at org.eclipse.core.databinding.ValueBinding$3$1.run(ValueBinding.java:206)
> at org.eclipse.core.databinding.observable.Realm$1.run(Realm.java:150)
> at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42)
> at org.eclipse.core.databinding.observable.Realm.safeRun(Realm.java:154)
> at org.eclipse.core.databinding.observable.Realm.exec(Realm.java:172)
> at org.eclipse.core.databinding.ValueBinding$3.run(ValueBinding.java:196)
> at org.eclipse.core.databinding.observable.Realm$1.run(Realm.java:150)
> at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42)
> at org.eclipse.core.databinding.observable.Realm.safeRun(Realm.java:154)
> at org.eclipse.core.databinding.observable.Realm.exec(Realm.java:172)
> at org.eclipse.core.databinding.ValueBinding.doUpdate(ValueBinding.java:158)
> at org.eclipse.core.databinding.ValueBinding.access$4(ValueBinding.java:147)
> at org.eclipse.core.databinding.ValueBinding$1.handleValueChange(ValueBinding.java:46)
> at org.eclipse.core.databinding.observable.value.ValueChangeEvent.dispatch(ValueChangeEvent.java:63)
> at org.eclipse.core.databinding.observable.ChangeManager.fireEvent(ChangeManager.java:119)
> at org.eclipse.core.databinding.observable.value.DecoratingObservableValue.fireValueChange(DecoratingObservableValue.java:57)
> at org.eclipse.core.databinding.observable.value.DecoratingObservableValue.handleValueChange(DecoratingObservableValue.java:99)
> at org.eclipse.core.databinding.observable.value.DecoratingObservableValue$1.handleValueChange(DecoratingObservableValue.java:72)
> at org.eclipse.core.databinding.observable.value.ValueChangeEvent.dispatch(ValueChangeEvent.java:63)
> at org.eclipse.core.databinding.observable.ChangeManager.fireEvent(ChangeManager.java:119)
> at org.eclipse.core.databinding.observable.value.AbstractObservableValue.fireValueChange(AbstractObservableValue.java:74)
> at org.eclipse.core.internal.databinding.property.value.SimplePropertyObservableValue.notifyIfChanged(SimplePropertyObservableValue.java:127)
> at org.eclipse.core.internal.databinding.property.value.SimplePropertyObservableValue.access$2(SimplePropertyObservableValue.java:119)
> at org.eclipse.core.internal.databinding.property.value.SimplePropertyObservableValue$1$1.run(SimplePropertyObservableValue.java:69)
> at org.eclipse.core.databinding.observable.Realm$1.run(Realm.java:150)
> at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42)
> at org.eclipse.core.databinding.observable.Realm.safeRun(Realm.java:154)
> at org.eclipse.core.databinding.observable.Realm.exec(Realm.java:172)
> at org.eclipse.core.internal.databinding.property.value.SimplePropertyObservableValue$1.handleEvent(SimplePropertyObservableValue.java:65)
> at org.eclipse.core.databinding.property.NativePropertyListener.fireChange(NativePropertyListener.java:65)
> at org.eclipse.jface.internal.databinding.viewers.SelectionChangedListener.selectionChanged(SelectionChangedListener.java:36)
> 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.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:4481)
> at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1327)
> at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3819)
> at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3430)
> at org.eclipse.jface.window.Window.runEventLoop(Window.java:827)
> at org.eclipse.jface.window.Window.open(Window.java:803)
> at org.jboss.tools.common.ui.WizardUtils.openWizardDialog(WizardUtils.java:244)
> at org.jboss.tools.openshift.internal.ui.handler.NewApplicationHandler.execute(NewApplicationHandler.java:46)
> at org.eclipse.ui.internal.handlers.HandlerProxy.execute(HandlerProxy.java:295)
> at org.eclipse.ui.internal.handlers.E4HandlerProxy.execute(E4HandlerProxy.java:90)
> at sun.reflect.GeneratedMethodAccessor73.invoke(Unknown Source)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:483)
> at org.eclipse.e4.core.internal.di.MethodRequestor.execute(MethodRequestor.java:56)
> at org.eclipse.e4.core.internal.di.InjectorImpl.invokeUsingClass(InjectorImpl.java:252)
> at org.eclipse.e4.core.internal.di.InjectorImpl.invoke(InjectorImpl.java:234)
> at org.eclipse.e4.core.contexts.ContextInjectionFactory.invoke(ContextInjectionFactory.java:132)
> at org.eclipse.e4.core.commands.internal.HandlerServiceHandler.execute(HandlerServiceHandler.java:152)
> at org.eclipse.core.commands.Command.executeWithChecks(Command.java:493)
> at org.eclipse.core.commands.ParameterizedCommand.executeWithChecks(ParameterizedCommand.java:486)
> at org.eclipse.e4.core.commands.internal.HandlerServiceImpl.executeHandler(HandlerServiceImpl.java:210)
> at org.eclipse.e4.ui.workbench.renderers.swt.HandledContributionItem.executeItem(HandledContributionItem.java:799)
> at org.eclipse.e4.ui.workbench.renderers.swt.HandledContributionItem.handleWidgetSelection(HandledContributionItem.java:675)
> at org.eclipse.e4.ui.workbench.renderers.swt.HandledContributionItem.access$7(HandledContributionItem.java:659)
> at org.eclipse.e4.ui.workbench.renderers.swt.HandledContributionItem$4.handleEvent(HandledContributionItem.java:592)
> at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84)
> at org.eclipse.swt.widgets.Display.sendEvent(Display.java:4481)
> at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1327)
> at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3819)
> at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3430)
> 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:483)
> 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.NullPointerException
> at org.jboss.tools.openshift.internal.ui.wizard.application.NewApplicationWizardModel.setLabels(NewApplicationWizardModel.java:167)
> at org.jboss.tools.openshift.internal.ui.wizard.application.NewApplicationWizardModel.setTemplate(NewApplicationWizardModel.java:81)
> at sun.reflect.GeneratedMethodAccessor70.invoke(Unknown Source)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:483)
> at org.eclipse.core.internal.databinding.beans.BeanPropertyHelper.writeProperty(BeanPropertyHelper.java:59)
> ... 102 more
> {code}
> It is possible to proceed to wizard, but once it is created, all resources show green mark (everythink is ok), but buildconfig is not created. If I am using this template json directly, from file system (its in repo under examples/jenkins/application-template.json), then the buildconfig is created.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 9 months
[JBoss JIRA] (JBIDE-20092) Connection wizard: hitting retrivial link with mouse does not do anything on OSX (hitting enter works)
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-20092?page=com.atlassian.jira.plugi... ]
Andre Dietisheim edited comment on JBIDE-20092 at 6/30/15 10:39 AM:
--------------------------------------------------------------------
This definitely is a platform issue, we should file an issue against SWT/MacOS in eclipse bugzilla
was (Author: adietish):
This definitely is a platform issue.
> Connection wizard: hitting retrivial link with mouse does not do anything on OSX (hitting enter works)
> ------------------------------------------------------------------------------------------------------
>
> Key: JBIDE-20092
> URL: https://issues.jboss.org/browse/JBIDE-20092
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Reporter: Max Rydahl Andersen
> Assignee: Andre Dietisheim
> Priority: Critical
> Labels: connection_wizard, openshift_v3
> Fix For: 4.3.0.Beta2
>
> Attachments: new-connection-link.png, retrieve-token-link.png, singnup-link.png, styled-text-link.png
>
>
> using https://console.stg.openshift.com as server
> the retrieve link does nothing if clicked.
> Only if I use "enter" on the keyboard does it actually show a browser.
> Steps:
> # ASSERT: make sure that you're using MacOS
> # EXEC: launch new connection wizard,
> # EXEC: provide host, pick "OpenShift v3" and make sure you have "Oauth" authentication chosen
> # EXEC: hit "retrieve" link
> !retrieve-token-link.png!
> Result:
> Nothing happens
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 9 months
[JBoss JIRA] (JBIDE-20092) Connection wizard: hitting retrivial link with mouse does not do anything on OSX (hitting enter works)
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-20092?page=com.atlassian.jira.plugi... ]
Andre Dietisheim commented on JBIDE-20092:
------------------------------------------
merged and pushed to upstream/master
> Connection wizard: hitting retrivial link with mouse does not do anything on OSX (hitting enter works)
> ------------------------------------------------------------------------------------------------------
>
> Key: JBIDE-20092
> URL: https://issues.jboss.org/browse/JBIDE-20092
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Reporter: Max Rydahl Andersen
> Assignee: Max Rydahl Andersen
> Priority: Critical
> Labels: connection_wizard, openshift_v3
> Fix For: 4.3.0.Beta2
>
> Attachments: new-connection-link.png, retrieve-token-link.png, singnup-link.png, styled-text-link.png
>
>
> using https://console.stg.openshift.com as server
> the retrieve link does nothing if clicked.
> Only if I use "enter" on the keyboard does it actually show a browser.
> Steps:
> # ASSERT: make sure that you're using MacOS
> # EXEC: launch new connection wizard,
> # EXEC: provide host, pick "OpenShift v3" and make sure you have "Oauth" authentication chosen
> # EXEC: hit "retrieve" link
> !retrieve-token-link.png!
> Result:
> Nothing happens
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 9 months
[JBoss JIRA] (JBIDE-20092) Connection wizard: hitting retrivial link with mouse does not do anything on OSX (hitting enter works)
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-20092?page=com.atlassian.jira.plugi... ]
Andre Dietisheim commented on JBIDE-20092:
------------------------------------------
This definitely is a platform issue.
> Connection wizard: hitting retrivial link with mouse does not do anything on OSX (hitting enter works)
> ------------------------------------------------------------------------------------------------------
>
> Key: JBIDE-20092
> URL: https://issues.jboss.org/browse/JBIDE-20092
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Reporter: Max Rydahl Andersen
> Assignee: Max Rydahl Andersen
> Priority: Critical
> Labels: connection_wizard, openshift_v3
> Fix For: 4.3.0.Beta2
>
> Attachments: new-connection-link.png, retrieve-token-link.png, singnup-link.png, styled-text-link.png
>
>
> using https://console.stg.openshift.com as server
> the retrieve link does nothing if clicked.
> Only if I use "enter" on the keyboard does it actually show a browser.
> Steps:
> # ASSERT: make sure that you're using MacOS
> # EXEC: launch new connection wizard,
> # EXEC: provide host, pick "OpenShift v3" and make sure you have "Oauth" authentication chosen
> # EXEC: hit "retrieve" link
> !retrieve-token-link.png!
> Result:
> Nothing happens
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
10 years, 9 months
