[JBoss JIRA] (JBIDE-24222) CDK3 Server adapter: fails to detect that cdk3 Beta3 was successfully started (on macos/xhyve?)
by Martin Malina (JIRA)
[ https://issues.jboss.org/browse/JBIDE-24222?page=com.atlassian.jira.plugi... ]
Martin Malina edited comment on JBIDE-24222 at 8/22/17 9:47 AM:
----------------------------------------------------------------
As discussed on the cabal call just now, I tested this to see if this bug is still relevant.
I used:
devstudio-11.1.0.AM1-v20170822-0754-B847-installer-standalone.jar
$ ./minishift version
minishift v1.3.1+a2d3799
CDK v3.1.0-1
The answer is: Yes, this issue is still replicable.
Here are the steps to replicate:
1. Make sure cdk with xhyve works for you in cli:
{code}
./minishift setup-cdk
./minishift start --username xx --password xx
{code}
2. Stop cdk from cli:
{code}
./minishift stop
{code}
3. Setup a cdk 3 server adapter in devstudio/eclipse (make sure xhyve provider is selected)
4. Start cdk fron eclipse
This will result in cdk starting, but an error window will pop up: Server Container Development Environment 3 failed to start. And at this point cdk is actually stopped.
was (Author: mmalina):
As discussed on the cabal call just now, I tested this to see if this bug is still relevant.
I used:
devstudio-11.1.0.AM1-v20170822-0754-B847-installer-standalone.jar
$ ./minishift version
minishift v1.3.1+a2d3799
CDK v3.1.0-1
The answer is: Yes, this issue is still replicable.
Here are the steps to replicate:
1. Make sure cdk with xhyve works for you in cli:
{code}
./minishift setup-cdk
./minishift start --username xx --password xx
{code}
2. Stop cdk from cli:
{code}
./minishift stop
{code}
3. Setup a cdk 3 server adapter in devstudio/eclipse (make sure xhyve provider is selected)
4. Start cdk fron eclipse
This will result in cdk starting, but an error window will pop up: Server Container Development Environment 3 failed to start.
> CDK3 Server adapter: fails to detect that cdk3 Beta3 was successfully started (on macos/xhyve?)
> -----------------------------------------------------------------------------------------------
>
> Key: JBIDE-24222
> URL: https://issues.jboss.org/browse/JBIDE-24222
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: cdk
> Affects Versions: 4.4.4.AM2
> Environment: macos
> xhyve supervisor
> cdk3 beta3
> Reporter: Andre Dietisheim
> Assignee: Andre Dietisheim
> Priority: Critical
> Labels: help_wanted
> Fix For: 4.5.x
>
> Attachments: Screenshot 2017-04-18 16.37.44.png, image-2017-04-04-15-48-59-677.png
>
>
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 7 months
[JBoss JIRA] (JBIDE-24222) CDK3 Server adapter: fails to detect that cdk3 Beta3 was successfully started (on macos/xhyve?)
by Martin Malina (JIRA)
[ https://issues.jboss.org/browse/JBIDE-24222?page=com.atlassian.jira.plugi... ]
Martin Malina commented on JBIDE-24222:
---------------------------------------
As discussed on the cabal call just now, I tested this to see if this bug is still relevant.
I used:
devstudio-11.1.0.AM1-v20170822-0754-B847-installer-standalone.jar
$ ./minishift version
minishift v1.3.1+a2d3799
CDK v3.1.0-1
The answer is: Yes, this issue is still replicable.
Here are the steps to replicate:
1. Make sure cdk with xhyve works for you in cli:
{code}
./minishift setup-cdk
./minishift start --username xx --password xx
{code}
2. Stop cdk from cli:
{code}
./minishift stop
{code}
3. Setup a cdk 3 server adapter in devstudio/eclipse (make sure xhyve provider is selected)
4. Start cdk fron eclipse
This will result in cdk starting, but an error window will pop up: Server Container Development Environment 3 failed to start.
> CDK3 Server adapter: fails to detect that cdk3 Beta3 was successfully started (on macos/xhyve?)
> -----------------------------------------------------------------------------------------------
>
> Key: JBIDE-24222
> URL: https://issues.jboss.org/browse/JBIDE-24222
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: cdk
> Affects Versions: 4.4.4.AM2
> Environment: macos
> xhyve supervisor
> cdk3 beta3
> Reporter: Andre Dietisheim
> Assignee: Andre Dietisheim
> Priority: Critical
> Labels: help_wanted
> Fix For: 4.5.x
>
> Attachments: Screenshot 2017-04-18 16.37.44.png, image-2017-04-04-15-48-59-677.png
>
>
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 7 months
[JBoss JIRA] (JBTIS-1162) Upgrade BPMN2-Modeler to 1.4.1
by Paul Leacu (JIRA)
Paul Leacu created JBTIS-1162:
---------------------------------
Summary: Upgrade BPMN2-Modeler to 1.4.1
Key: JBTIS-1162
URL: https://issues.jboss.org/browse/JBTIS-1162
Project: JBoss Tools Integration Stack
Issue Type: Task
Components: BPMN2
Affects Versions: 4.5.0.Final
Reporter: Paul Leacu
Assignee: Paul Leacu
Fix For: 4.5.1.CR1
Grab the latest BPMN2 Modeler
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 7 months
[JBoss JIRA] (JBTIS-1161) Unknown category 'org.jboss.tools.discovery.certification.earlyaccess' referenced by connector 'org.jboss.tools.esb.feature' ( NoStackTrace below DiscoveryViewer$18.run )
by Paul Leacu (JIRA)
[ https://issues.jboss.org/browse/JBTIS-1161?page=com.atlassian.jira.plugin... ]
Paul Leacu commented on JBTIS-1161:
-----------------------------------
@nboldt - we dropped ESB 2 years ago and the IS early access already doesn't reference org.jboss.tools.discovery.certification.earlyaccess. This can't be failing now - there's nothing I can do for it back in JBTIS 4.3.0.Alpha2a - quick check back w/ you before I close it.
> Unknown category 'org.jboss.tools.discovery.certification.earlyaccess' referenced by connector 'org.jboss.tools.esb.feature' ( NoStackTrace below DiscoveryViewer$18.run )
> ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------
>
> Key: JBTIS-1161
> URL: https://issues.jboss.org/browse/JBTIS-1161
> Project: JBoss Tools Integration Stack
> Issue Type: Bug
> Components: distribution, ESB
> Affects Versions: 11.0.0.GA
> Reporter: Automated Error Reporting Bot
> Assignee: Paul Leacu
>
> The following incident was reported via the automated error reporting:
> The user(s) left the following comments:
> --- manderse(a)redhat.com wrote: ---
> test message - why is this happening.
>
> code: 0
> plugin: org.eclipse.mylyn.discovery.core_3.17.0.v20150625-2042
> message: Unknown category 'org.jboss.tools.discovery.certification.earlyaccess' referenced by connector 'org.jboss.tools.esb.feature' declared in org.jboss.tools.central.discovery.integration_stack.earlyaccess_4.3.0.Alpha2a_v20151006_1928_B438.jar_806886544943382023.jar
> fingerprint: dd8fd5fff4740f5c681ba9438f20d2d5
> exception class: org.eclipse.epp.logging.aeri.core.util.NoStackTrace
> exception message: This event was logged without a stack trace. A synthetic stack trace was hence inserted.
> number of children: 0
>
> org.eclipse.epp.logging.aeri.core.util.NoStackTrace: This event was logged without a stack trace. A synthetic stack trace was hence inserted.
> at org.eclipse.mylyn.commons.core.StatusHandler.log(StatusHandler.java:47)
> at org.eclipse.mylyn.internal.discovery.core.model.ConnectorDiscovery.connectCertificationsToDescriptors(ConnectorDiscovery.java:235)
> at org.eclipse.mylyn.internal.discovery.core.model.ConnectorDiscovery.performDiscovery(ConnectorDiscovery.java:128)
> at org.jboss.tools.central.editors.xpl.DiscoveryViewer$18.run(DiscoveryViewer.java:1189)
> at org.eclipse.jface.operation.ModalContext$ModalContextThread.run(ModalContext.java:119)
>
>
> General Information:
> reported-by: manderse(a)redhat.com
> anonymous-id: 751eebb9-1908-48d7-882a-d109eb3ae47e
> eclipse-build-id: 4.5.0.I20150603-2000
> eclipse-product: org.eclipse.platform.ide
> operating system: MacOSX 10.11.2 (x86_64) - cocoa
> jre-version: 1.8.0_20-b26
> The following plug-ins were present on the execution stack (*):
> 1. org.eclipse.jface_3.11.0.v20150602-1400
> 2. org.eclipse.mylyn.commons.core_3.17.0.v20150625-2042
> 3. org.eclipse.mylyn.discovery.core_3.17.0.v20150625-2042
> 4. org.jboss.tools.central_2.0.0.Final-v20151001-1531-B45
> Please note that:
> * Messages, stacktraces, and nested status objects may be shortened.
> * Bug fields like status, resolution, and whiteboard are sent
> back to reporters.
> * The list of present bundles and their respective versions was
> calculated by package naming heuristics. This may or may not reflect reality.
> Other Resources:
> * Report: https://dev.eclipse.org/recommenders/committers/confess/#/problems/56b7dc...
> * Manual: https://dev.eclipse.org/recommenders/community/confess/#/guide
> Thank you for your assistance.
> Your friendly error-reports-inbox.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 7 months
[JBoss JIRA] (JBTIS-1161) Unknown category 'org.jboss.tools.discovery.certification.earlyaccess' referenced by connector 'org.jboss.tools.esb.feature' ( NoStackTrace below DiscoveryViewer$18.run )
by Paul Leacu (JIRA)
[ https://issues.jboss.org/browse/JBTIS-1161?page=com.atlassian.jira.plugin... ]
Paul Leacu edited comment on JBTIS-1161 at 8/22/17 9:10 AM:
------------------------------------------------------------
[~nickboldt] - we dropped ESB 2 years ago and the IS early access already doesn't reference org.jboss.tools.discovery.certification.earlyaccess. This can't be failing now - there's nothing I can do for it back in JBTIS 4.3.0.Alpha2a - quick check back w/ you before I close it.
was (Author: pleacu):
@nboldt - we dropped ESB 2 years ago and the IS early access already doesn't reference org.jboss.tools.discovery.certification.earlyaccess. This can't be failing now - there's nothing I can do for it back in JBTIS 4.3.0.Alpha2a - quick check back w/ you before I close it.
> Unknown category 'org.jboss.tools.discovery.certification.earlyaccess' referenced by connector 'org.jboss.tools.esb.feature' ( NoStackTrace below DiscoveryViewer$18.run )
> ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------
>
> Key: JBTIS-1161
> URL: https://issues.jboss.org/browse/JBTIS-1161
> Project: JBoss Tools Integration Stack
> Issue Type: Bug
> Components: distribution, ESB
> Affects Versions: 11.0.0.GA
> Reporter: Automated Error Reporting Bot
> Assignee: Paul Leacu
>
> The following incident was reported via the automated error reporting:
> The user(s) left the following comments:
> --- manderse(a)redhat.com wrote: ---
> test message - why is this happening.
>
> code: 0
> plugin: org.eclipse.mylyn.discovery.core_3.17.0.v20150625-2042
> message: Unknown category 'org.jboss.tools.discovery.certification.earlyaccess' referenced by connector 'org.jboss.tools.esb.feature' declared in org.jboss.tools.central.discovery.integration_stack.earlyaccess_4.3.0.Alpha2a_v20151006_1928_B438.jar_806886544943382023.jar
> fingerprint: dd8fd5fff4740f5c681ba9438f20d2d5
> exception class: org.eclipse.epp.logging.aeri.core.util.NoStackTrace
> exception message: This event was logged without a stack trace. A synthetic stack trace was hence inserted.
> number of children: 0
>
> org.eclipse.epp.logging.aeri.core.util.NoStackTrace: This event was logged without a stack trace. A synthetic stack trace was hence inserted.
> at org.eclipse.mylyn.commons.core.StatusHandler.log(StatusHandler.java:47)
> at org.eclipse.mylyn.internal.discovery.core.model.ConnectorDiscovery.connectCertificationsToDescriptors(ConnectorDiscovery.java:235)
> at org.eclipse.mylyn.internal.discovery.core.model.ConnectorDiscovery.performDiscovery(ConnectorDiscovery.java:128)
> at org.jboss.tools.central.editors.xpl.DiscoveryViewer$18.run(DiscoveryViewer.java:1189)
> at org.eclipse.jface.operation.ModalContext$ModalContextThread.run(ModalContext.java:119)
>
>
> General Information:
> reported-by: manderse(a)redhat.com
> anonymous-id: 751eebb9-1908-48d7-882a-d109eb3ae47e
> eclipse-build-id: 4.5.0.I20150603-2000
> eclipse-product: org.eclipse.platform.ide
> operating system: MacOSX 10.11.2 (x86_64) - cocoa
> jre-version: 1.8.0_20-b26
> The following plug-ins were present on the execution stack (*):
> 1. org.eclipse.jface_3.11.0.v20150602-1400
> 2. org.eclipse.mylyn.commons.core_3.17.0.v20150625-2042
> 3. org.eclipse.mylyn.discovery.core_3.17.0.v20150625-2042
> 4. org.jboss.tools.central_2.0.0.Final-v20151001-1531-B45
> Please note that:
> * Messages, stacktraces, and nested status objects may be shortened.
> * Bug fields like status, resolution, and whiteboard are sent
> back to reporters.
> * The list of present bundles and their respective versions was
> calculated by package naming heuristics. This may or may not reflect reality.
> Other Resources:
> * Report: https://dev.eclipse.org/recommenders/committers/confess/#/problems/56b7dc...
> * Manual: https://dev.eclipse.org/recommenders/community/confess/#/guide
> Thank you for your assistance.
> Your friendly error-reports-inbox.
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 7 months
[JBoss JIRA] (JBIDE-24878) Sometimes devstudio got stuck on Central CI rhel slave
by Ondrej Dockal (JIRA)
[ https://issues.jboss.org/browse/JBIDE-24878?page=com.atlassian.jira.plugi... ]
Ondrej Dockal reassigned JBIDE-24878:
-------------------------------------
Assignee: Ondrej Dockal
> Sometimes devstudio got stuck on Central CI rhel slave
> ------------------------------------------------------
>
> Key: JBIDE-24878
> URL: https://issues.jboss.org/browse/JBIDE-24878
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: integration-tests, qa
> Affects Versions: 4.5.1.AM1
> Environment: rhel
> Reporter: Ondrej Dockal
> Assignee: Ondrej Dockal
> Labels: central-ci, jenkins
> Attachments: error.log
>
>
> Sometimes it happens that devstudio got stuck while run on rhel slave in our central CI.
> Error log suggests this:
> {code}
> !ENTRY org.eclipse.osgi 4 0 2017-08-18 11:06:50.627
> !MESSAGE Application error
> !STACK 1
> org.eclipse.swt.SWTError: No more handles [gtk_init_check() failed]
> at org.eclipse.swt.SWT.error(SWT.java:4559)
> at org.eclipse.swt.widgets.Display.createDisplay(Display.java:948)
> at org.eclipse.swt.widgets.Display.create(Display.java:935)
> at org.eclipse.swt.graphics.Device.<init>(Device.java:174)
> at org.eclipse.swt.widgets.Display.<init>(Display.java:559)
> at org.eclipse.swt.widgets.Display.<init>(Display.java:550)
> at org.eclipse.ui.internal.Workbench.createDisplay(Workbench.java:781)
> at org.eclipse.ui.PlatformUI.createDisplay(PlatformUI.java:160)
> at org.eclipse.ui.internal.ide.application.IDEApplication.createDisplay(IDEApplication.java:181)
> at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:124)
> at org.eclipse.tycho.surefire.osgibooter.UITestApplication.runApplication(UITestApplication.java:31)
> at org.eclipse.tycho.surefire.osgibooter.AbstractUITestApplication.run(AbstractUITestApplication.java:120)
> at org.eclipse.tycho.surefire.osgibooter.UITestApplication.start(UITestApplication.java:37)
> 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:653)
> at org.eclipse.equinox.launcher.Main.basicRun(Main.java:590)
> at org.eclipse.equinox.launcher.Main.run(Main.java:1499)
> at org.eclipse.equinox.launcher.Main.main(Main.java:1472)
> {code}
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 7 months
[JBoss JIRA] (JBIDE-24878) Sometimes devstudio got stuck on Central CI rhel slave
by Ondrej Dockal (JIRA)
[ https://issues.jboss.org/browse/JBIDE-24878?page=com.atlassian.jira.plugi... ]
Ondrej Dockal updated JBIDE-24878:
----------------------------------
Sprint: devex #136 August 2017
> Sometimes devstudio got stuck on Central CI rhel slave
> ------------------------------------------------------
>
> Key: JBIDE-24878
> URL: https://issues.jboss.org/browse/JBIDE-24878
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: integration-tests, qa
> Affects Versions: 4.5.1.AM1
> Environment: rhel
> Reporter: Ondrej Dockal
> Assignee: Ondrej Dockal
> Labels: central-ci, jenkins
> Attachments: error.log
>
>
> Sometimes it happens that devstudio got stuck while run on rhel slave in our central CI.
> Error log suggests this:
> {code}
> !ENTRY org.eclipse.osgi 4 0 2017-08-18 11:06:50.627
> !MESSAGE Application error
> !STACK 1
> org.eclipse.swt.SWTError: No more handles [gtk_init_check() failed]
> at org.eclipse.swt.SWT.error(SWT.java:4559)
> at org.eclipse.swt.widgets.Display.createDisplay(Display.java:948)
> at org.eclipse.swt.widgets.Display.create(Display.java:935)
> at org.eclipse.swt.graphics.Device.<init>(Device.java:174)
> at org.eclipse.swt.widgets.Display.<init>(Display.java:559)
> at org.eclipse.swt.widgets.Display.<init>(Display.java:550)
> at org.eclipse.ui.internal.Workbench.createDisplay(Workbench.java:781)
> at org.eclipse.ui.PlatformUI.createDisplay(PlatformUI.java:160)
> at org.eclipse.ui.internal.ide.application.IDEApplication.createDisplay(IDEApplication.java:181)
> at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:124)
> at org.eclipse.tycho.surefire.osgibooter.UITestApplication.runApplication(UITestApplication.java:31)
> at org.eclipse.tycho.surefire.osgibooter.AbstractUITestApplication.run(AbstractUITestApplication.java:120)
> at org.eclipse.tycho.surefire.osgibooter.UITestApplication.start(UITestApplication.java:37)
> 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:653)
> at org.eclipse.equinox.launcher.Main.basicRun(Main.java:590)
> at org.eclipse.equinox.launcher.Main.run(Main.java:1499)
> at org.eclipse.equinox.launcher.Main.main(Main.java:1472)
> {code}
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 7 months
[JBoss JIRA] (JBIDE-24878) Sometimes devstudio got stuck on Central CI rhel slave
by Ondrej Dockal (JIRA)
Ondrej Dockal created JBIDE-24878:
-------------------------------------
Summary: Sometimes devstudio got stuck on Central CI rhel slave
Key: JBIDE-24878
URL: https://issues.jboss.org/browse/JBIDE-24878
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: integration-tests, qa
Affects Versions: 4.5.1.AM1
Environment: rhel
Reporter: Ondrej Dockal
Attachments: error.log
Sometimes it happens that devstudio got stuck while run on rhel slave in our central CI.
Error log suggests this:
{code}
!ENTRY org.eclipse.osgi 4 0 2017-08-18 11:06:50.627
!MESSAGE Application error
!STACK 1
org.eclipse.swt.SWTError: No more handles [gtk_init_check() failed]
at org.eclipse.swt.SWT.error(SWT.java:4559)
at org.eclipse.swt.widgets.Display.createDisplay(Display.java:948)
at org.eclipse.swt.widgets.Display.create(Display.java:935)
at org.eclipse.swt.graphics.Device.<init>(Device.java:174)
at org.eclipse.swt.widgets.Display.<init>(Display.java:559)
at org.eclipse.swt.widgets.Display.<init>(Display.java:550)
at org.eclipse.ui.internal.Workbench.createDisplay(Workbench.java:781)
at org.eclipse.ui.PlatformUI.createDisplay(PlatformUI.java:160)
at org.eclipse.ui.internal.ide.application.IDEApplication.createDisplay(IDEApplication.java:181)
at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:124)
at org.eclipse.tycho.surefire.osgibooter.UITestApplication.runApplication(UITestApplication.java:31)
at org.eclipse.tycho.surefire.osgibooter.AbstractUITestApplication.run(AbstractUITestApplication.java:120)
at org.eclipse.tycho.surefire.osgibooter.UITestApplication.start(UITestApplication.java:37)
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:653)
at org.eclipse.equinox.launcher.Main.basicRun(Main.java:590)
at org.eclipse.equinox.launcher.Main.run(Main.java:1499)
at org.eclipse.equinox.launcher.Main.main(Main.java:1472)
{code}
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 7 months