[JBoss JIRA] (JBIDE-21044) Error when trying to import Thym or JS project
by Mickael Istria (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21044?page=com.atlassian.jira.plugi... ]
Mickael Istria commented on JBIDE-21044:
----------------------------------------
[~gercan] This requires to consume a more recent build of THyM for JBT 4.3.1.Beta1. Is this possible?
> Error when trying to import Thym or JS project
> ----------------------------------------------
>
> Key: JBIDE-21044
> URL: https://issues.jboss.org/browse/JBIDE-21044
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: aerogear-hybrid, easymport, target-platform
> Affects Versions: 4.3.1.Beta1
> Environment: Nightly jboss-devstudio-9.0.1.Beta1-v20151101-1911-B132 with Hybrid mobile tools installed
> Reporter: Lucia Jelinkova
> Assignee: Mickael Istria
> Priority: Critical
> Fix For: 4.3.1.Beta1, 4.4.0.Alpha1
>
>
> When I try to import the kitchensink-cordova example for the 2nd time, an error occurs and the following error is logged.
> {code}
> java.lang.reflect.InvocationTargetException
> at org.eclipse.jface.operation.ModalContext.runInCurrentThread(ModalContext.java:478)
> at org.eclipse.jface.operation.ModalContext.run(ModalContext.java:371)
> at org.eclipse.jface.wizard.WizardDialog.run(WizardDialog.java:1002)
> at org.eclipse.ui.internal.wizards.datatransfer.ImportProposalsWizardPage.updateTreeContent(ImportProposalsWizardPage.java:185)
> at org.eclipse.ui.internal.wizards.datatransfer.ImportProposalsWizardPage.pageChanged(ImportProposalsWizardPage.java:221)
> at org.eclipse.jface.wizard.WizardDialog$9.run(WizardDialog.java:1505)
> 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.wizard.WizardDialog.firePageChanged(WizardDialog.java:1502)
> at org.eclipse.jface.wizard.WizardDialog.update(WizardDialog.java:1308)
> at org.eclipse.jface.wizard.WizardDialog.updateForPage(WizardDialog.java:1234)
> at org.eclipse.jface.wizard.WizardDialog.access$4(WizardDialog.java:1208)
> at org.eclipse.jface.wizard.WizardDialog$8.run(WizardDialog.java:1197)
> at org.eclipse.swt.custom.BusyIndicator.showWhile(BusyIndicator.java:70)
> at org.eclipse.jface.wizard.WizardDialog.showPage(WizardDialog.java:1194)
> at org.eclipse.jface.wizard.WizardDialog.nextPressed(WizardDialog.java:885)
> at org.eclipse.jface.wizard.WizardDialog.buttonPressed(WizardDialog.java:425)
> at org.eclipse.jface.dialogs.Dialog$2.widgetSelected(Dialog.java:619)
> at org.eclipse.swt.widgets.TypedListener.handleEvent(TypedListener.java:248)
> 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.jface.window.Window.runEventLoop(Window.java:827)
> at org.eclipse.jface.window.Window.open(Window.java:803)
> at org.eclipse.ui.internal.wizards.datatransfer.OpenFolderCommand.execute(OpenFolderCommand.java:91)
> 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.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.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: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: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.AbstractMethodError
> at org.eclipse.ui.internal.wizards.datatransfer.EasymportJob.getImportProposals(EasymportJob.java:548)
> at org.eclipse.ui.internal.wizards.datatransfer.ImportProposalsWizardPage$8.run(ImportProposalsWizardPage.java:188)
> at org.eclipse.jface.operation.ModalContext.runInCurrentThread(ModalContext.java:463)
> ... 72 more
> Root exception:
> java.lang.AbstractMethodError
> at org.eclipse.ui.internal.wizards.datatransfer.EasymportJob.getImportProposals(EasymportJob.java:548)
> at org.eclipse.ui.internal.wizards.datatransfer.ImportProposalsWizardPage$8.run(ImportProposalsWizardPage.java:188)
> at org.eclipse.jface.operation.ModalContext.runInCurrentThread(ModalContext.java:463)
> at org.eclipse.jface.operation.ModalContext.run(ModalContext.java:371)
> at org.eclipse.jface.wizard.WizardDialog.run(WizardDialog.java:1002)
> at org.eclipse.ui.internal.wizards.datatransfer.ImportProposalsWizardPage.updateTreeContent(ImportProposalsWizardPage.java:185)
> at org.eclipse.ui.internal.wizards.datatransfer.ImportProposalsWizardPage.pageChanged(ImportProposalsWizardPage.java:221)
> at org.eclipse.jface.wizard.WizardDialog$9.run(WizardDialog.java:1505)
> 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.wizard.WizardDialog.firePageChanged(WizardDialog.java:1502)
> at org.eclipse.jface.wizard.WizardDialog.update(WizardDialog.java:1308)
> at org.eclipse.jface.wizard.WizardDialog.updateForPage(WizardDialog.java:1234)
> at org.eclipse.jface.wizard.WizardDialog.access$4(WizardDialog.java:1208)
> at org.eclipse.jface.wizard.WizardDialog$8.run(WizardDialog.java:1197)
> at org.eclipse.swt.custom.BusyIndicator.showWhile(BusyIndicator.java:70)
> at org.eclipse.jface.wizard.WizardDialog.showPage(WizardDialog.java:1194)
> at org.eclipse.jface.wizard.WizardDialog.nextPressed(WizardDialog.java:885)
> at org.eclipse.jface.wizard.WizardDialog.buttonPressed(WizardDialog.java:425)
> at org.eclipse.jface.dialogs.Dialog$2.widgetSelected(Dialog.java:619)
> at org.eclipse.swt.widgets.TypedListener.handleEvent(TypedListener.java:248)
> 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.jface.window.Window.runEventLoop(Window.java:827)
> at org.eclipse.jface.window.Window.open(Window.java:803)
> at org.eclipse.ui.internal.wizards.datatransfer.OpenFolderCommand.execute(OpenFolderCommand.java:91)
> 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.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.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: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: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)
> {code}
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 4 months
[JBoss JIRA] (JBIDE-21109) [application wizard] 2 connections from same server but for different users result in project mismatch
by Fred Bricon (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21109?page=com.atlassian.jira.plugi... ]
Fred Bricon updated JBIDE-21109:
--------------------------------
Fix Version/s: 4.3.1.Beta1
4.4.0.Alpha1
> [application wizard] 2 connections from same server but for different users result in project mismatch
> ------------------------------------------------------------------------------------------------------
>
> Key: JBIDE-21109
> URL: https://issues.jboss.org/browse/JBIDE-21109
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: openshift
> Reporter: Fred Bricon
> Fix For: 4.3.1.Beta1, 4.4.0.Alpha1
>
>
> In JBT, connecting 2 users on the same server, results in wrong projects being shown for the 2nd connection (in the new application wizard).
> This is caused by calling Connection.ownResource(project), having
> {code}
> public boolean ownsResource(IResource resource) {
> if (resource == null) {
> return false;
> }
> IClient client = resource.accept(new CapabilityVisitor<IClientCapability, IClient>() {
> @Override
> public IClient visit(IClientCapability capability) {
> return capability.getClient();
> }
> }, null);
> return ObjectUtils.equals(this.client, client);
> }
> {code}
> The problem is the clients are equals for both connections. A check for token equality should be performed to distinguish them
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 4 months
[JBoss JIRA] (JBIDE-21109) [application wizard] 2 connections from same server but for different users result in project mismatch
by Jeff Cantrill (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21109?page=com.atlassian.jira.plugi... ]
Jeff Cantrill updated JBIDE-21109:
----------------------------------
Project: Tools (JBoss Tools) (was: OpenShift Java Client)
Key: JBIDE-21109 (was: OSJC-229)
Component/s: openshift
(was: core)
Affects Version/s: (was: 3.0.0)
> [application wizard] 2 connections from same server but for different users result in project mismatch
> ------------------------------------------------------------------------------------------------------
>
> Key: JBIDE-21109
> URL: https://issues.jboss.org/browse/JBIDE-21109
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: openshift
> Reporter: Fred Bricon
>
> In JBT, connecting 2 users on the same server, results in wrong projects being shown for the 2nd connection (in the new application wizard).
> This is caused by calling Connection.ownResource(project), having
> {code}
> public boolean ownsResource(IResource resource) {
> if (resource == null) {
> return false;
> }
> IClient client = resource.accept(new CapabilityVisitor<IClientCapability, IClient>() {
> @Override
> public IClient visit(IClientCapability capability) {
> return capability.getClient();
> }
> }, null);
> return ObjectUtils.equals(this.client, client);
> }
> {code}
> The problem is the clients are equals for both connections. A check for token equality should be performed to distinguish them
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 4 months
[JBoss JIRA] (JBIDE-21105) Remove BIRT?
by Konstantin Marmalyukov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21105?page=com.atlassian.jira.plugi... ]
Konstantin Marmalyukov edited comment on JBIDE-21105 at 11/18/15 10:53 AM:
---------------------------------------------------------------------------
I install latest available birt from http://download.eclipse.org/birt/update-site/4.5/
After that I look into Eclipse plugins directory and notice that nothing changed after birt installation from Jetty POV. !eclipse-after-birt.png!
So here comes new question: [~nickboldt], are you sure that Birt depends on 9.2.9?
P.S. Please take a look, do I install correct birt? :)
was (Author: kmarmaliykov):
I install latest available birt from http://download.eclipse.org/birt/update-site/4.5/
After that I look into Eclipse plugins directory and notice that nothing changed after birt installation from Jetty POV. !eclipse-after-birt.png!
So here comes new question: [~nickboldt], are you sure that Birt depends on 9.2.9?
> Remove BIRT?
> ------------
>
> Key: JBIDE-21105
> URL: https://issues.jboss.org/browse/JBIDE-21105
> Project: Tools (JBoss Tools)
> Issue Type: Sub-task
> Components: birt, target-platform
> Affects Versions: 4.4.0.Alpha1
> Reporter: Nick Boldt
> Assignee: Nick Boldt
> Fix For: 4.4.0.Alpha1
>
> Attachments: birt-4.5-vs-mars-interim.txt, birt-4.5-vs-mars-interim_summary.txt, birt-depends-on-jetty-deploy-929.png, birt-depends-on-jetty-osgi-boot-929.png, eclipse-after-birt.png
>
>
> {quote}
> (2015-11-17 11:42:50) kmarmaliykov: nickboldt: I look into neon M3 and see that there is no jetty 9.2.9 there
> (2015-11-17 11:43:18) nickboldt: kmarmaliykov: yes, 9.2.9 is from Birt site
> (2015-11-17 11:43:21) nickboldt: because Birt needs it
> (2015-11-17 11:43:33) nickboldt: but there's no Birt for Neon yet so we have to include the Birt for Mars
> (2015-11-17 11:43:37) maxandersen: nickboldt: akazakov: are you talking about having birt in Neon ?
> (2015-11-17 11:43:44) maxandersen: afaik birt is dead.
> (2015-11-17 11:43:53) maxandersen: won't participate in neon release afaik.
> (2015-11-17 11:43:56) nickboldt: maxandersen: so we should remove birt from JBT 4.4?
> (2015-11-17 11:44:24) maxandersen: well, check first if birt is actually in neon. if it is not the decision is very easy.
> (2015-11-17 11:44:38) akazakov: +1
> (2015-11-17 11:45:36) maxandersen: if it is in, then lets talk options. but if birt requires us to jump through too many hoops its not worth keeping it in.
> (2015-11-17 11:45:55) nickboldt: birt 4.5.0.v201506092134 is in Neon from 201511131000 (M3) - http://download.eclipse.org/releases/neon/201511131000/
> (2015-11-17 11:47:08) nickboldt: and there's a newer birt 4.5.0.v201510231925 (same major.minor.service, newer datestamp) in http://download.eclipse.org/birt/update-site/mars-interim/
> {quote}
> So, yesterday as part of updates for JBIDE-20976, I pulled a new BIRT mirror here:
> http://download.jboss.org/jbosstools/updates/requirements/birt/4.5.0.v201...
> But we could also just use the old one from Mars.0:
> http://download.jboss.org/jbosstools/updates/requirements/birt/4.5.0.v201...
> Or we could remove support for BIRT and its webtools / charting integration entirely from JBT 4.4.0.Alpha1, since as Max says BIRT is at EOL.
> *DISCUSS*.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 4 months
[JBoss JIRA] (JBIDE-21105) Remove BIRT?
by Konstantin Marmalyukov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21105?page=com.atlassian.jira.plugi... ]
Konstantin Marmalyukov commented on JBIDE-21105:
------------------------------------------------
I install latest available birt from http://download.eclipse.org/birt/update-site/4.5/
After that I look into Eclipse plugins directory and notice that nothing changed after birt installation from Jetty POV. !eclipse-after-birt.png!
So here comes new question: [~nickboldt], are you sure that Birt depends on 9.2.9?
> Remove BIRT?
> ------------
>
> Key: JBIDE-21105
> URL: https://issues.jboss.org/browse/JBIDE-21105
> Project: Tools (JBoss Tools)
> Issue Type: Sub-task
> Components: birt, target-platform
> Affects Versions: 4.4.0.Alpha1
> Reporter: Nick Boldt
> Assignee: Nick Boldt
> Fix For: 4.4.0.Alpha1
>
> Attachments: birt-4.5-vs-mars-interim.txt, birt-4.5-vs-mars-interim_summary.txt, birt-depends-on-jetty-deploy-929.png, birt-depends-on-jetty-osgi-boot-929.png, eclipse-after-birt.png
>
>
> {quote}
> (2015-11-17 11:42:50) kmarmaliykov: nickboldt: I look into neon M3 and see that there is no jetty 9.2.9 there
> (2015-11-17 11:43:18) nickboldt: kmarmaliykov: yes, 9.2.9 is from Birt site
> (2015-11-17 11:43:21) nickboldt: because Birt needs it
> (2015-11-17 11:43:33) nickboldt: but there's no Birt for Neon yet so we have to include the Birt for Mars
> (2015-11-17 11:43:37) maxandersen: nickboldt: akazakov: are you talking about having birt in Neon ?
> (2015-11-17 11:43:44) maxandersen: afaik birt is dead.
> (2015-11-17 11:43:53) maxandersen: won't participate in neon release afaik.
> (2015-11-17 11:43:56) nickboldt: maxandersen: so we should remove birt from JBT 4.4?
> (2015-11-17 11:44:24) maxandersen: well, check first if birt is actually in neon. if it is not the decision is very easy.
> (2015-11-17 11:44:38) akazakov: +1
> (2015-11-17 11:45:36) maxandersen: if it is in, then lets talk options. but if birt requires us to jump through too many hoops its not worth keeping it in.
> (2015-11-17 11:45:55) nickboldt: birt 4.5.0.v201506092134 is in Neon from 201511131000 (M3) - http://download.eclipse.org/releases/neon/201511131000/
> (2015-11-17 11:47:08) nickboldt: and there's a newer birt 4.5.0.v201510231925 (same major.minor.service, newer datestamp) in http://download.eclipse.org/birt/update-site/mars-interim/
> {quote}
> So, yesterday as part of updates for JBIDE-20976, I pulled a new BIRT mirror here:
> http://download.jboss.org/jbosstools/updates/requirements/birt/4.5.0.v201...
> But we could also just use the old one from Mars.0:
> http://download.jboss.org/jbosstools/updates/requirements/birt/4.5.0.v201...
> Or we could remove support for BIRT and its webtools / charting integration entirely from JBT 4.4.0.Alpha1, since as Max says BIRT is at EOL.
> *DISCUSS*.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 4 months
[JBoss JIRA] (JBIDE-21105) Remove BIRT?
by Konstantin Marmalyukov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21105?page=com.atlassian.jira.plugi... ]
Konstantin Marmalyukov updated JBIDE-21105:
-------------------------------------------
Attachment: eclipse-after-birt.png
> Remove BIRT?
> ------------
>
> Key: JBIDE-21105
> URL: https://issues.jboss.org/browse/JBIDE-21105
> Project: Tools (JBoss Tools)
> Issue Type: Sub-task
> Components: birt, target-platform
> Affects Versions: 4.4.0.Alpha1
> Reporter: Nick Boldt
> Assignee: Nick Boldt
> Fix For: 4.4.0.Alpha1
>
> Attachments: birt-4.5-vs-mars-interim.txt, birt-4.5-vs-mars-interim_summary.txt, birt-depends-on-jetty-deploy-929.png, birt-depends-on-jetty-osgi-boot-929.png, eclipse-after-birt.png
>
>
> {quote}
> (2015-11-17 11:42:50) kmarmaliykov: nickboldt: I look into neon M3 and see that there is no jetty 9.2.9 there
> (2015-11-17 11:43:18) nickboldt: kmarmaliykov: yes, 9.2.9 is from Birt site
> (2015-11-17 11:43:21) nickboldt: because Birt needs it
> (2015-11-17 11:43:33) nickboldt: but there's no Birt for Neon yet so we have to include the Birt for Mars
> (2015-11-17 11:43:37) maxandersen: nickboldt: akazakov: are you talking about having birt in Neon ?
> (2015-11-17 11:43:44) maxandersen: afaik birt is dead.
> (2015-11-17 11:43:53) maxandersen: won't participate in neon release afaik.
> (2015-11-17 11:43:56) nickboldt: maxandersen: so we should remove birt from JBT 4.4?
> (2015-11-17 11:44:24) maxandersen: well, check first if birt is actually in neon. if it is not the decision is very easy.
> (2015-11-17 11:44:38) akazakov: +1
> (2015-11-17 11:45:36) maxandersen: if it is in, then lets talk options. but if birt requires us to jump through too many hoops its not worth keeping it in.
> (2015-11-17 11:45:55) nickboldt: birt 4.5.0.v201506092134 is in Neon from 201511131000 (M3) - http://download.eclipse.org/releases/neon/201511131000/
> (2015-11-17 11:47:08) nickboldt: and there's a newer birt 4.5.0.v201510231925 (same major.minor.service, newer datestamp) in http://download.eclipse.org/birt/update-site/mars-interim/
> {quote}
> So, yesterday as part of updates for JBIDE-20976, I pulled a new BIRT mirror here:
> http://download.jboss.org/jbosstools/updates/requirements/birt/4.5.0.v201...
> But we could also just use the old one from Mars.0:
> http://download.jboss.org/jbosstools/updates/requirements/birt/4.5.0.v201...
> Or we could remove support for BIRT and its webtools / charting integration entirely from JBT 4.4.0.Alpha1, since as Max says BIRT is at EOL.
> *DISCUSS*.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years, 4 months