[JBoss JIRA] (JBIDE-21105) Deprecate BIRT
by Paul Leacu (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21105?page=com.atlassian.jira.plugi... ]
Paul Leacu commented on JBIDE-21105:
------------------------------------
+1 - I'll generate a JBTIS Jira to track the addition of the Birt reporting engine dependency into the JBTIS target platform for Neon.
> Deprecate 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, birt-wizard-new-library.png, birt-wizard-new-library__NEON.png, birt-wizards.png, birt-wizards__NEON.png, eclipse-after-birt.png, install-jboss-birt-sites.png, install-jboss-birt-sites__NEON.png, install-jboss-birt.png, install-jboss-birt__NEON.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*.
> *Alexey Kazakov:* I changed the title from "Remove Birt?" to "Deprecate Birt" as we agreed to deprecate/sunset it for JBDS 10 / JBT 4.4 / Neon.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years
[JBoss JIRA] (JBIDE-21673) JBoss Runtime Detection preference page throws StackOverflowError
by Radim Hopp (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21673?page=com.atlassian.jira.plugi... ]
Radim Hopp commented on JBIDE-21673:
------------------------------------
Hi [~scabanovich],
Aren't there any restrictions (OS, java, gtk2/3, ...) when this issue happens? I tried to reproduce it (the exception) with JBDS 9.1.0.Beta2 without success.
About that weird resizing... Is it part of fix in this jira? Because I tried it with JBDS 9.1.0.CR1-v20160314-1117-B409 and it still behaves quite oddly: https://youtu.be/eJIus4cXtdg (sorry for the sound in there)
> JBoss Runtime Detection preference page throws StackOverflowError
> -----------------------------------------------------------------
>
> Key: JBIDE-21673
> URL: https://issues.jboss.org/browse/JBIDE-21673
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: central, runtime-detection
> Affects Versions: 4.3.1.Beta2
> Reporter: Viacheslav Kabanovich
> Assignee: Rob Stryker
> Priority: Critical
> Fix For: 4.3.1.CR1, 4.4.0.Alpha1
>
>
> 1. Start Eclipse.
> 2. Open Preferences.
> 3. Select JBoss Runtime Detection.
> Exception:
> {code}
> !ENTRY org.eclipse.ui 4 0 2016-02-10 19:18:24.266
> !MESSAGE Unhandled event loop exception
> !STACK 0
> org.eclipse.swt.SWTException: Failed to execute runnable (java.lang.StackOverflowError)
> at org.eclipse.swt.SWT.error(SWT.java:4503)
> at org.eclipse.swt.SWT.error(SWT.java:4418)
> at org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchronizer.java:138)
> at org.eclipse.swt.widgets.Display.runAsyncMessages(Display.java:3795)
> at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3434)
> at org.eclipse.jface.window.Window.runEventLoop(Window.java:818)
> at org.eclipse.jface.window.Window.open(Window.java:794)
> at org.eclipse.ui.internal.dialogs.WorkbenchPreferenceDialog.open(WorkbenchPreferenceDialog.java:211)
> at org.eclipse.ui.internal.OpenPreferencesAction.run(OpenPreferencesAction.java:63)
> at org.eclipse.jface.action.Action.runWithEvent(Action.java:473)
> at org.eclipse.jface.action.ActionContributionItem.handleWidgetSelection(ActionContributionItem.java:564)
> at org.eclipse.jface.action.ActionContributionItem.lambda$4(ActionContributionItem.java:396)
> at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84)
> at org.eclipse.swt.widgets.Display.sendEvent(Display.java:4482)
> at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1329)
> at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3820)
> at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3431)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$4.run(PartRenderingEngine.java:1132)
> 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)
> Caused by: java.lang.StackOverflowError
> at org.eclipse.swt.internal.gtk.OS._gtk_widget_size_allocate(Native Method)
> at org.eclipse.swt.internal.gtk.OS.gtk_widget_size_allocate(OS.java:14919)
> ----infinitle repeated part begin----
> at org.eclipse.swt.custom.TableEditor$1.controlMoved(TableEditor.java:95)
> at org.eclipse.swt.widgets.TypedListener.handleEvent(TypedListener.java:224)
> at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84)
> at org.eclipse.swt.widgets.Display.sendEvent(Display.java:4482)
> at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1329)
> at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1353)
> at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1334)
> at org.eclipse.swt.widgets.TableColumn.gtk_size_allocate(TableColumn.java:395)
> at org.eclipse.swt.widgets.Widget.windowProc(Widget.java:1991)
> at org.eclipse.swt.widgets.Display.windowProc(Display.java:4718)
> at org.eclipse.swt.internal.gtk.OS._gtk_widget_size_allocate(Native Method)
> at org.eclipse.swt.internal.gtk.OS.gtk_widget_size_allocate(OS.java:14919)
> at org.eclipse.swt.widgets.Control.forceResize(Control.java:780)
> at org.eclipse.swt.widgets.Table.getClientArea(Table.java:1154)
> at org.eclipse.swt.custom.TableEditor.computeBounds(TableEditor.java:120)
> at org.eclipse.swt.custom.ControlEditor.layout(ControlEditor.java:223)
> at org.eclipse.swt.custom.TableEditor.layout(TableEditor.java:265)
> at org.eclipse.swt.custom.TableEditor$1.controlMoved(TableEditor.java:95)
> at org.eclipse.swt.widgets.TypedListener.handleEvent(TypedListener.java:224)
> at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84)
> at org.eclipse.swt.widgets.Display.sendEvent(Display.java:4482)
> at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1329)
> at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1353)
> at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1334)
> at org.eclipse.swt.widgets.TableColumn.gtk_size_allocate(TableColumn.java:395)
> at org.eclipse.swt.widgets.Widget.windowProc(Widget.java:1991)
> at org.eclipse.swt.widgets.Display.windowProc(Display.java:4718)
> at org.eclipse.swt.internal.gtk.OS._gtk_widget_size_allocate(Native Method)
> at org.eclipse.swt.internal.gtk.OS.gtk_widget_size_allocate(OS.java:14919)
> at org.eclipse.swt.widgets.Control.forceResize(Control.java:780)
> at org.eclipse.swt.widgets.Table.getClientArea(Table.java:1154)
> at org.eclipse.swt.custom.TableEditor.computeBounds(TableEditor.java:120)
> at org.eclipse.swt.custom.ControlEditor.layout(ControlEditor.java:223)
> at org.eclipse.swt.custom.TableEditor.layout(TableEditor.java:265)
> ----infinitle repeated part end----
> at org.eclipse.swt.custom.ControlEditor.setEditor(ControlEditor.java:251)
> at org.eclipse.swt.custom.TableEditor.setEditor(TableEditor.java:240)
> at org.eclipse.swt.custom.TableEditor.setEditor(TableEditor.java:256)
> at org.jboss.tools.runtime.ui.internal.preferences.RuntimePreferencePage.createDetectorViewer(RuntimePreferencePage.java:208)
> at org.jboss.tools.runtime.ui.internal.preferences.RuntimePreferencePage.createContents(RuntimePreferencePage.java:140)
> at org.eclipse.jface.preference.PreferencePage.createControl(PreferencePage.java:241)
> at org.eclipse.jface.preference.PreferenceDialog.createPageControl(PreferenceDialog.java:1429)
> at org.eclipse.jface.preference.PreferenceDialog$9.run(PreferenceDialog.java:1196)
> 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.preference.PreferenceDialog.showPage(PreferenceDialog.java:1188)
> at org.eclipse.ui.internal.dialogs.FilteredPreferenceDialog.showPage(FilteredPreferenceDialog.java:608)
> at org.eclipse.jface.preference.PreferenceDialog$5.lambda$0(PreferenceDialog.java:655)
> at org.eclipse.swt.custom.BusyIndicator.showWhile(BusyIndicator.java:70)
> at org.eclipse.jface.preference.PreferenceDialog$5.selectionChanged(PreferenceDialog.java:652)
> at org.eclipse.jface.viewers.StructuredViewer$3.run(StructuredViewer.java:876)
> 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.StructuredViewer.firePostSelectionChanged(StructuredViewer.java:873)
> at org.eclipse.jface.viewers.StructuredViewer.handlePostSelect(StructuredViewer.java:1242)
> at org.eclipse.jface.viewers.StructuredViewer$5.widgetSelected(StructuredViewer.java:1268)
> at org.eclipse.jface.util.OpenStrategy.firePostSelectionEvent(OpenStrategy.java:265)
> at org.eclipse.jface.util.OpenStrategy.access$5(OpenStrategy.java:259)
> at org.eclipse.jface.util.OpenStrategy$1.lambda$1(OpenStrategy.java:431)
> at org.eclipse.swt.widgets.RunnableLock.run(RunnableLock.java:35)
> at org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchronizer.java:135)
> ... 36 more
> {code}
> 4. Select another preference page.
> 5. Again try to select JBoss Runtime Detection.
> Now, it opens successfully.
> 6. Try to adjust split between the tree of pages and the page.
> Preferences dialog window starts uncontrollably expand until it fills the entire screen width.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years
[JBoss JIRA] (JBDS-3671) sshd needs to be installed and started
by Hardy Ferentschik (JIRA)
[ https://issues.jboss.org/browse/JBDS-3671?page=com.atlassian.jira.plugin.... ]
Hardy Ferentschik commented on JBDS-3671:
-----------------------------------------
{code}
this pacman worked for me and sshd -h would print out help text.
{code}
Ok, I did the same thing and it installs the binary. However, it does not install sshd as a service. I tried this gist - https://gist.github.com/samhocevar/00eec26d9e9988d080ac, but it did not work out of the box (still investigating).
The question here is really, does installing msys2 not introduce yet another unix-style environment? Is the whole point not to avoid installing things like cygwin & co?
Also, trying to execute {{sshd}} (except just -h), returns
{quote}
sshd re-exec requires execution with an absolute path
{quote}
> sshd needs to be installed and started
> --------------------------------------
>
> Key: JBDS-3671
> URL: https://issues.jboss.org/browse/JBDS-3671
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Feature Request
> Components: installer
> Reporter: Hardy Ferentschik
> Labels: havoc
> Fix For: 9.1.0.CR1
>
>
> As parts of the Docker story we need to be able to mount the users home directory into the VM (as docker-machine does as well). Only this way the user can then use Docker mounts to mount for example project directories into a Docker container.
> docker-machine uses the vbguest additions for that, but we still need to determine whether this is possible for us due to potential licensing issues.
> An alternative approach is to use [sshfs|https://github.com/dustymabe/vagrant-sshfs/] and use ssh to mount the user's home directory into the VM. sshfs, however, requires a running sshd on the host. On Windows I am aware of two ways of doing that
> * Cygwin - http://docs.oracle.com/cd/E24628_01/install.121/e22624/preinstall_req_cyg...
> * Win32-OpenSSH - https://github.com/PowerShell/Win32-OpenSSH
> I think the Windows ssh port would be the preferred solution, however, when testing it, the connection failed when using sshfs. I was able to simple ssh from the guest (CDK) to the host (Windows), but when using sshfs the connection would just abort. More investigation is required for using vagrant-sshfs with Win32-OpenSSH. It might just be that the Windows port is not fully functional which would leave use with the cygwin approach.
> Bottom line, if we want to use the sshfs approach as an alternative for vbguest additions, we need to get sshd installed one way or the other.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years
[JBoss JIRA] (JBIDE-21821) Old org.eclipse.egit.importer.ui in JBDS Marketplace Install Breaks Egit in Mars.2
by Mickael Istria (JIRA)
[ https://issues.jboss.org/browse/JBIDE-21821?page=com.atlassian.jira.plugi... ]
Mickael Istria updated JBIDE-21821:
-----------------------------------
Summary: Old org.eclipse.egit.importer.ui in JBDS Marketplace Install Breaks Egit in Mars.2 (was: JBoss Developer Studio Marketplace Install Breaks Egit in Mars.2)
> Old org.eclipse.egit.importer.ui in JBDS Marketplace Install Breaks Egit in Mars.2
> ----------------------------------------------------------------------------------
>
> Key: JBIDE-21821
> URL: https://issues.jboss.org/browse/JBIDE-21821
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: build, marketplace
> Reporter: Thomas Mäder
> Assignee: Nick Boldt
> Priority: Blocker
> Fix For: 4.3.1.CR1
>
> Attachments: FrameworkEvent ERROR.txt, jbt-error, jgit40_41_JBDS.installed.txt, jgit40_41_JBT.installed.txt
>
>
> Installing Red Hat JBoss Developer Studio 9.0.0GA into a fresh Eclipse 4.5.2 (for Eclipse Committers) causes Egit to break.
> # Install Eclipse 4.5.2
> # In the Marketplace, search for "jboss developer studio"
> # You get a single result: Red Hat JBoss Developer Studio 9.0.0 GA
> # Install it
> # Restart
> # Observe: the EGit views and preferences are missing
> # Observe: you get messages in the Eclipse error log concerning a dependency version incompatibility
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years
[JBoss JIRA] (JBDS-3680) Error loading file switchyard.xml. Unable to load the generated resource.
by CDW Engine (JIRA)
[ https://issues.jboss.org/browse/JBDS-3680?page=com.atlassian.jira.plugin.... ]
CDW Engine updated JBDS-3680:
-----------------------------
> Error loading file switchyard.xml. Unable to load the generated resource.
> -------------------------------------------------------------------------
>
> Key: JBDS-3680
> URL: https://issues.jboss.org/browse/JBDS-3680
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Bug
> Affects Versions: 9.0.0.GA
> Environment: After creating a new switchyard project, next time it starts up JBDS is not able to open its own generated siwtchyard.xml file. The error "Error loading file switchyard.xml. Unable to load the generated resource" is displayed. The only choice is the OK button. Pressing it, the JBDS screen doesn't display but JBDS seems to be started and the LCK file created. The only option the user has is to kill the process.
> Tested on Windows 7 and Windows 10 with Java 8.
> Reporter: nicolas duminil
> Priority: Blocker
>
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years
[JBoss JIRA] (JBDS-3680) Error loading file switchyard.xml. Unable to load the generated resource.
by nicolas duminil (JIRA)
nicolas duminil created JBDS-3680:
-------------------------------------
Summary: Error loading file switchyard.xml. Unable to load the generated resource.
Key: JBDS-3680
URL: https://issues.jboss.org/browse/JBDS-3680
Project: Developer Studio (JBoss Developer Studio)
Issue Type: Bug
Affects Versions: 9.0.0.GA
Environment: After creating a new switchyard project, next time it starts up JBDS is not able to open its own generated siwtchyard.xml file. The error "Error loading file switchyard.xml. Unable to load the generated resource" is displayed. The only choice is the OK button. Pressing it, the JBDS screen doesn't display but JBDS seems to be started and the LCK file created. The only option the user has is to kill the process.
Tested on Windows 7 and Windows 10 with Java 8.
Reporter: nicolas duminil
Priority: Blocker
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years