[JBoss JIRA] (JBIDE-21377) Include Yaml editor in JBoss Tools (& JBDS) via feature dep from o.j.t.central & add to CoreTools category, too
by Victor Rubezhny (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21377?page=com.atlassian.jira.plugi... ]
Victor Rubezhny commented on JBIDE-21377:
-----------------------------------------
[~mickael_istria] No, it's not available yet. It's pushed into WTP just before NY and last couple of builds are failed (because of JPA problems) in early 2016, so we still have to wait for green build to be declared.
> Include Yaml editor in JBoss Tools (& JBDS) via feature dep from o.j.t.central & add to CoreTools category, too
> ---------------------------------------------------------------------------------------------------------------
>
> Key: JBIDE-21377
> URL: https://issues.jboss.org/browse/JBIDE-21377
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: updatesite
> Affects Versions: 4.3.1.Beta1
> Reporter: Mickael Istria
> Assignee: Nick Boldt
> Fix For: 4.3.1.Beta2
>
>
> There is a decent Yaml editor existing for Eclipse IDE: https://github.com/oyse/yedit . It has 21 stars and is included in STS ( JBDS-3465 ). Similarly to JSon Editor, we should provide it to JBoss Tools users by default.
> This would require adding it to the TP and adding a dependency from a JBT feature to it.
> On longer-term, we should get it touch with the author to get this plugin migrated to Eclipse.org world, most likely under the WTP/SSE project (cc [~vrubezhny])
> --
> Story points - 8 (fibonacci):
> * update Central TP,
> * update JBT/JBDS TPs,
> * update JBT/JBDS category.xml files,
> * update JBDS feature.xml,
> * send announcement email re: TP changes
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 5 months
[JBoss JIRA] (JBDS-3579) Fuse archetype catalog cannot be added with JBDS 9
by Fred Bricon (JIRA)
[ https://issues.jboss.org/browse/JBDS-3579?page=com.atlassian.jira.plugin.... ]
Fred Bricon commented on JBDS-3579:
-----------------------------------
This is a regression. The newer archetyper version used in m2e 1.6 exposes an old bug in https://github.com/takari/aether-connector-okhttp/blob/master/src/main/ja... where HTTP return codes are ignored
The best workaround would probably to publish the archetype in nexus to a separate, fixed location, using archetype-catalog.xml as file name, or at least use some url rewriting/redirecting, at the http server level.
> Fuse archetype catalog cannot be added with JBDS 9
> --------------------------------------------------
>
> Key: JBDS-3579
> URL: https://issues.jboss.org/browse/JBDS-3579
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Feature Request
> Components: maven
> Affects Versions: 9.0.0.GA
> Reporter: Keith Babo
> Assignee: Fred Bricon
>
> When adding the Fuse Integration Services archetype catalog to JBDS 9, the IDE reports that the catalog is empty. This works in Eclipse and I've heard reports that it also works in earlier versions of JBDS (although I have not confirmed this personally).
> Archetype catalog in question:
> https://repo.fusesource.com/nexus/content/groups/public/io/fabric8/archet...
> Steps to reproduce:
> - Preferences -> Maven -> Archetypes -> Add Remote Catalog
> - Add URL above for Catalog File
> - Click Verify ... and you get the message "Remote catalog is empty"
> - Click Finish and try to use the catalog from the New Maven Project wizard and the message is "No archetypes available for this catalog."
> Impact here is that Fuse customers looking to use Fuse on OpenShift cannot use JBDS to create new projects using our Maven archetypes (the primary means of getting started).
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 5 months
[JBoss JIRA] (JBDS-3579) Fuse archetype catalog cannot be added with JBDS 9
by Max Rydahl Andersen (JIRA)
[ https://issues.jboss.org/browse/JBDS-3579?page=com.atlassian.jira.plugin.... ]
Max Rydahl Andersen commented on JBDS-3579:
-------------------------------------------
so is this an regression in m2e or something that just worked by log in past ?
> Fuse archetype catalog cannot be added with JBDS 9
> --------------------------------------------------
>
> Key: JBDS-3579
> URL: https://issues.jboss.org/browse/JBDS-3579
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Feature Request
> Components: maven
> Affects Versions: 9.0.0.GA
> Reporter: Keith Babo
> Assignee: Fred Bricon
>
> When adding the Fuse Integration Services archetype catalog to JBDS 9, the IDE reports that the catalog is empty. This works in Eclipse and I've heard reports that it also works in earlier versions of JBDS (although I have not confirmed this personally).
> Archetype catalog in question:
> https://repo.fusesource.com/nexus/content/groups/public/io/fabric8/archet...
> Steps to reproduce:
> - Preferences -> Maven -> Archetypes -> Add Remote Catalog
> - Add URL above for Catalog File
> - Click Verify ... and you get the message "Remote catalog is empty"
> - Click Finish and try to use the catalog from the New Maven Project wizard and the message is "No archetypes available for this catalog."
> Impact here is that Fuse customers looking to use Fuse on OpenShift cannot use JBDS to create new projects using our Maven archetypes (the primary means of getting started).
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 5 months
[JBoss JIRA] (JBDS-3579) Fuse archetype catalog cannot be added with JBDS 9
by Max Rydahl Andersen (JIRA)
[ https://issues.jboss.org/browse/JBDS-3579?page=com.atlassian.jira.plugin.... ]
Max Rydahl Andersen edited comment on JBDS-3579 at 1/11/16 5:39 AM:
--------------------------------------------------------------------
so is this an regression in m2e or something that just worked by luck in past ?
was (Author: maxandersen):
so is this an regression in m2e or something that just worked by log in past ?
> Fuse archetype catalog cannot be added with JBDS 9
> --------------------------------------------------
>
> Key: JBDS-3579
> URL: https://issues.jboss.org/browse/JBDS-3579
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Feature Request
> Components: maven
> Affects Versions: 9.0.0.GA
> Reporter: Keith Babo
> Assignee: Fred Bricon
>
> When adding the Fuse Integration Services archetype catalog to JBDS 9, the IDE reports that the catalog is empty. This works in Eclipse and I've heard reports that it also works in earlier versions of JBDS (although I have not confirmed this personally).
> Archetype catalog in question:
> https://repo.fusesource.com/nexus/content/groups/public/io/fabric8/archet...
> Steps to reproduce:
> - Preferences -> Maven -> Archetypes -> Add Remote Catalog
> - Add URL above for Catalog File
> - Click Verify ... and you get the message "Remote catalog is empty"
> - Click Finish and try to use the catalog from the New Maven Project wizard and the message is "No archetypes available for this catalog."
> Impact here is that Fuse customers looking to use Fuse on OpenShift cannot use JBDS to create new projects using our Maven archetypes (the primary means of getting started).
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 5 months
[JBoss JIRA] (JBDS-3516) Need better doc on using Central zip (online/offline modes) [was: Install all from central zip fails on CordovaSim]
by Misha Ali (JIRA)
[ https://issues.jboss.org/browse/JBDS-3516?page=com.atlassian.jira.plugin.... ]
Misha Ali updated JBDS-3516:
----------------------------
Sprint: 12-Oct >> 25-Oct 2015-JBDS/JBT, 04-Jan >> 17-Jan 2016-JBDS/JBT (was: 12-Oct >> 25-Oct 2015-JBDS/JBT)
> Need better doc on using Central zip (online/offline modes) [was: Install all from central zip fails on CordovaSim]
> -------------------------------------------------------------------------------------------------------------------
>
> Key: JBDS-3516
> URL: https://issues.jboss.org/browse/JBDS-3516
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Bug
> Components: central, documentation, updatesite
> Affects Versions: 9.0.0.CR1
> Environment: jboss-devstudio-9.0.0.CR1-v20150912-1100-B100
> jboss-devstudio-9.0.0.CR1-updatesite-central.zip from https://devstudio.redhat.com/9.0/staging/updates/core/jboss-devstudio-9.0...
> Reporter: Jan Richter
> Assignee: Misha Ali
> Fix For: 9.1.0.Beta2
>
>
> This is what comes up when I try to install everything from the central zip:
> {noformat}
> Cannot complete the install because one or more required items could not be found.
> Software being installed: JBoss Tools Apache Cordova Simulator 3.7.0.CR1-v20150911-0408-B28 (org.jboss.tools.cordovasim.feature.feature.group 3.7.0.CR1-v20150911-0408-B28)
> Missing requirement: Eclipse integrations of BrowserSim 3.7.0.CR1-v20150911-0408-B28 (org.jboss.tools.cordovasim.eclipse 3.7.0.CR1-v20150911-0408-B28) requires 'bundle org.eclipse.thym.core 0.3.0' but it could not be found
> Cannot satisfy dependency:
> From: JBoss Tools Apache Cordova Simulator 3.7.0.CR1-v20150911-0408-B28 (org.jboss.tools.cordovasim.feature.feature.group 3.7.0.CR1-v20150911-0408-B28)
> To: org.jboss.tools.cordovasim.eclipse [3.7.0.CR1-v20150911-0408-B28]
> {noformat}
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 5 months
[JBoss JIRA] (JBIDE-21433) Application wizard: No projects nor server templates when launched from explorer context menu
by Viacheslav Kabanovich (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21433?page=com.atlassian.jira.plugi... ]
Viacheslav Kabanovich edited comment on JBIDE-21433 at 1/8/16 10:05 PM:
------------------------------------------------------------------------
Just a guess. Is it possible that in some cases WizardUtils.openWizardDialog(IWorkbenchWizard, Shell) cannot find selection in the right view?
Since NewApplicationWizard is not good without selected openshift object, it would be good to report in NewApplicationWizard.init() failure to find it, with logging what was found in selection.
was (Author: scabanovich):
Just a guess. There is handler org.jboss.tools.openshift.internal.ui.handler.NewApplicationHandler registered in a command, that starts NewApplicationWizard without invoking its init() method and maybe when this command provides menu item, the result is the uninitialized dialog.
NewApplicationWizard is also registered in extension point org.jboss.tools.openshift.ui.newApplicationWizard, and probably when it is started that way, everything is ok.
> Application wizard: No projects nor server templates when launched from explorer context menu
> ---------------------------------------------------------------------------------------------
>
> Key: JBIDE-21433
> URL: https://issues.jboss.org/browse/JBIDE-21433
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.3.1.Beta2
> Reporter: Marián Labuda
> Labels: application_wizard, openshift_v3
> Fix For: 4.3.1.Beta2
>
> Attachments: empty_project.png
>
>
> Opening a New OpenShift application wizard via context menu of a project makes wizard not usable, because project is not shown and also no templates are available.
> !empty_project.png!
> This is happening if previously a connection having the project where context menu were opened was used to create a new Server adapter, or at least it passed New Server adapter wizard beyond the page with a connection.
> Stack trace:
> {code}
> org.eclipse.e4.core.di.InjectionException: org.jboss.tools.openshift.core.connection.ConnectionNotFoundException: Unable to find the connection for a Project named someproject
> at org.eclipse.e4.core.internal.di.MethodRequestor.execute(MethodRequestor.java:68)
> 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:1329)
> 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: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: org.jboss.tools.openshift.core.connection.ConnectionNotFoundException: Unable to find the connection for a Project named someproject
> at org.jboss.tools.openshift.core.connection.ConnectionsRegistryUtil.getConnectionFor(ConnectionsRegistryUtil.java:41)
> at org.jboss.tools.openshift.internal.ui.handler.NewProjectHandler.execute(NewProjectHandler.java:44)
> 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.GeneratedMethodAccessor81.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)
> ... 38 more
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 5 months
[JBoss JIRA] (JBIDE-21433) Application wizard: No projects nor server templates when launched from explorer context menu
by Viacheslav Kabanovich (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21433?page=com.atlassian.jira.plugi... ]
Viacheslav Kabanovich commented on JBIDE-21433:
-----------------------------------------------
Just a guess. There is handler org.jboss.tools.openshift.internal.ui.handler.NewApplicationHandler registered in a command, that starts NewApplicationWizard without invoking its init() method and maybe when this command provides menu item, the result is the uninitialized dialog.
NewApplicationWizard is also registered in extension point org.jboss.tools.openshift.ui.newApplicationWizard, and probably when it is started that way, everything is ok.
> Application wizard: No projects nor server templates when launched from explorer context menu
> ---------------------------------------------------------------------------------------------
>
> Key: JBIDE-21433
> URL: https://issues.jboss.org/browse/JBIDE-21433
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.3.1.Beta2
> Reporter: Marián Labuda
> Labels: application_wizard, openshift_v3
> Fix For: 4.3.1.Beta2
>
> Attachments: empty_project.png
>
>
> Opening a New OpenShift application wizard via context menu of a project makes wizard not usable, because project is not shown and also no templates are available.
> !empty_project.png!
> This is happening if previously a connection having the project where context menu were opened was used to create a new Server adapter, or at least it passed New Server adapter wizard beyond the page with a connection.
> Stack trace:
> {code}
> org.eclipse.e4.core.di.InjectionException: org.jboss.tools.openshift.core.connection.ConnectionNotFoundException: Unable to find the connection for a Project named someproject
> at org.eclipse.e4.core.internal.di.MethodRequestor.execute(MethodRequestor.java:68)
> 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:1329)
> 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: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: org.jboss.tools.openshift.core.connection.ConnectionNotFoundException: Unable to find the connection for a Project named someproject
> at org.jboss.tools.openshift.core.connection.ConnectionsRegistryUtil.getConnectionFor(ConnectionsRegistryUtil.java:41)
> at org.jboss.tools.openshift.internal.ui.handler.NewProjectHandler.execute(NewProjectHandler.java:44)
> 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.GeneratedMethodAccessor81.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)
> ... 38 more
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 5 months