[JBoss JIRA] (JBIDE-13492) org.eclipse.zest (nedded for ESB) is missing in TP
by Paul Leacu (JIRA)
[ https://issues.jboss.org/browse/JBIDE-13492?page=com.atlassian.jira.plugi... ]
Paul Leacu commented on JBIDE-13492:
------------------------------------
Hi Alexy -
1. We are including zest in the JBTIS aggregate:
category.xml:<!-- esb requires zest -->
category.xml:<feature url="features/org.eclipse.zest_0.0.0.jar" id="org.eclipse.zest" version="0.0.0"/>
2. There's a new wiki which describes the JBTIS components (including the target platform - base/community)
https://community.jboss.org/wiki/IntegrationToolingReleaseProcess
e.g. here's the full community target:
https://repository.jboss.org/nexus/content/repositories/snapshots/org/jbo...
3. Any TP related JIRA in the integration stack should use this space: https://issues.jboss.org/browse/JBTIS
So please try using the new TP IS target. If there's still an issue we can reopen a new JIRA in JBTIS.
Also - please send email if you get stuck.
--paull
> org.eclipse.zest (nedded for ESB) is missing in TP
> --------------------------------------------------
>
> Key: JBIDE-13492
> URL: https://issues.jboss.org/browse/JBIDE-13492
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: esb, target-platform
> Environment: Eclipse 4.3.0.M5
> Reporter: Alexey Kazakov
> Assignee: Paul Leacu
> Priority: Blocker
> Fix For: 4.1.0.Alpha1
>
>
> {code}
> [ERROR] Cannot resolve project dependencies:
> [ERROR] Software being installed: org.jboss.tools.esb.project.ui 1.5.300.qualifier
> [ERROR] Missing requirement: org.jboss.tools.esb.project.ui 1.5.300.qualifier requires 'bundle org.eclipse.zest.core 0.0.0' but it could not be found
> [ERROR]
> [ERROR] Internal error: java.lang.RuntimeException: "No solution found because the problem is unsatisfiable.": ["Unable to satisfy dependency from org.jboss.tools.esb.project.ui 1.5.300.qualifier to bundle org.eclipse.zest.core 0.0.0.", "Unable to satisfy dependency from org.jboss.tools.esb.project.ui 1.5.300.qualifier to bundle org.eclipse.zest.layouts 0.0.0.", "No solution found because the problem is unsatisfiable."] -> [Help 1]
> org.apache.maven.InternalErrorException: Internal error: java.lang.RuntimeException: "No solution found because the problem is unsatisfiable.": ["Unable to satisfy dependency from org.jboss.tools.esb.project.ui 1.5.300.qualifier to bundle org.eclipse.zest.core 0.0.0.", "Unable to satisfy dependency from org.jboss.tools.esb.project.ui 1.5.300.qualifier to bundle org.eclipse.zest.layouts 0.0.0.", "No solution found because the problem is unsatisfiable."]
> {code}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 2 months
[JBoss JIRA] (JBIDE-13490) org.jboss.tools.jst.jsp.test.commands.KeyBindingsTest failure for Eclipse 4.3.0.M5
by Snjezana Peco (JIRA)
[ https://issues.jboss.org/browse/JBIDE-13490?page=com.atlassian.jira.plugi... ]
Snjezana Peco commented on JBIDE-13490:
---------------------------------------
i think we have to use Eclipse 4.3.0.M5a.
See https://bugs.eclipse.org/bugs/show_bug.cgi?id=399831
> org.jboss.tools.jst.jsp.test.commands.KeyBindingsTest failure for Eclipse 4.3.0.M5
> ----------------------------------------------------------------------------------
>
> Key: JBIDE-13490
> URL: https://issues.jboss.org/browse/JBIDE-13490
> Project: Tools (JBoss Tools)
> Issue Type: Sub-task
> Components: common/jst/core
> Affects Versions: 4.1.0.Alpha1
> Reporter: Alexey Kazakov
> Assignee: Victor Rubezhny
> Fix For: 4.1.0.Alpha2
>
>
> {code}
> -------------------------------------------------------------------------------
> Test set: org.jboss.tools.jst.jsp.test.JstJspAllTests
> -------------------------------------------------------------------------------
> Tests run: 21, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 66.752 sec <<< FAILURE!
> testKeyBindings(org.jboss.tools.jst.jsp.test.commands.KeyBindingsTest) Time elapsed: 1.601 sec <<< FAILURE!
> junit.framework.AssertionFailedError: Command found but cannot be executed for 'Perfect Match' keystroke CTRL+D
> at junit.framework.Assert.fail(Assert.java:50)
> at junit.framework.Assert.assertTrue(Assert.java:20)
> at junit.framework.Assert.assertNotNull(Assert.java:218)
> at org.jboss.tools.jst.jsp.test.commands.KeyBindingsTest.doTestKeyBindingsOnPage(KeyBindingsTest.java:97)
> at org.jboss.tools.jst.jsp.test.commands.KeyBindingsTest.testKeyBindings(KeyBindingsTest.java:70)
> {code}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 2 months
[JBoss JIRA] (JBIDE-13490) org.jboss.tools.jst.jsp.test.commands.KeyBindingsTest failure for Eclipse 4.3.0.M5
by Snjezana Peco (JIRA)
[ https://issues.jboss.org/browse/JBIDE-13490?page=com.atlassian.jira.plugi... ]
Snjezana Peco edited comment on JBIDE-13490 at 2/8/13 2:00 PM:
---------------------------------------------------------------
I think we have to use Eclipse 4.3.0.M5a.
See https://bugs.eclipse.org/bugs/show_bug.cgi?id=399831
was (Author: snjeza):
i think we have to use Eclipse 4.3.0.M5a.
See https://bugs.eclipse.org/bugs/show_bug.cgi?id=399831
> org.jboss.tools.jst.jsp.test.commands.KeyBindingsTest failure for Eclipse 4.3.0.M5
> ----------------------------------------------------------------------------------
>
> Key: JBIDE-13490
> URL: https://issues.jboss.org/browse/JBIDE-13490
> Project: Tools (JBoss Tools)
> Issue Type: Sub-task
> Components: common/jst/core
> Affects Versions: 4.1.0.Alpha1
> Reporter: Alexey Kazakov
> Assignee: Victor Rubezhny
> Fix For: 4.1.0.Alpha2
>
>
> {code}
> -------------------------------------------------------------------------------
> Test set: org.jboss.tools.jst.jsp.test.JstJspAllTests
> -------------------------------------------------------------------------------
> Tests run: 21, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 66.752 sec <<< FAILURE!
> testKeyBindings(org.jboss.tools.jst.jsp.test.commands.KeyBindingsTest) Time elapsed: 1.601 sec <<< FAILURE!
> junit.framework.AssertionFailedError: Command found but cannot be executed for 'Perfect Match' keystroke CTRL+D
> at junit.framework.Assert.fail(Assert.java:50)
> at junit.framework.Assert.assertTrue(Assert.java:20)
> at junit.framework.Assert.assertNotNull(Assert.java:218)
> at org.jboss.tools.jst.jsp.test.commands.KeyBindingsTest.doTestKeyBindingsOnPage(KeyBindingsTest.java:97)
> at org.jboss.tools.jst.jsp.test.commands.KeyBindingsTest.testKeyBindings(KeyBindingsTest.java:70)
> {code}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 2 months
[JBoss JIRA] (JBIDE-13480) BrowserSim: simulator is closing unexpectedly while changing skin
by Denis Golovin (JIRA)
[ https://issues.jboss.org/browse/JBIDE-13480?page=com.atlassian.jira.plugi... ]
Denis Golovin updated JBIDE-13480:
----------------------------------
Fix Version/s: 4.0.1.Final
(was: 4.0.x)
> BrowserSim: simulator is closing unexpectedly while changing skin
> -----------------------------------------------------------------
>
> Key: JBIDE-13480
> URL: https://issues.jboss.org/browse/JBIDE-13480
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: Visual Page Editor core
> Affects Versions: 4.0.0.CR1
> Environment: Windows 7
> Reporter: Yahor Radtsevich
> Assignee: Konstantin Marmalyukov
> Priority: Critical
> Fix For: 4.0.1.Final
>
>
> On some web pages BrowserSim is closing with the following stack trace while changing skin (see steps to reproduce):
> {code}
> Exception in thread "main" org.eclipse.swt.SWTException: Widget is disposed
> at org.eclipse.swt.SWT.error(SWT.java:4361)
> at org.eclipse.swt.SWT.error(SWT.java:4276)
> at org.eclipse.swt.SWT.error(SWT.java:4247)
> at org.eclipse.swt.widgets.Widget.error(Widget.java:468)
> at org.eclipse.swt.widgets.Widget.checkWidget(Widget.java:340)
> at org.eclipse.swt.widgets.Control.setVisible(Control.java:3725)
> at org.jboss.tools.vpe.browsersim.ui.skin.ios.AppleIPhone3ResizableSkin.
> progressChanged(AppleIPhone3ResizableSkin.java:247)
> at org.jboss.tools.vpe.browsersim.ui.BrowserSim$3.changed(BrowserSim.jav
> a:251)
> at org.eclipse.swt.browser.WebResourceLoadDelegate.identifierForInitialR
> equest(WebResourceLoadDelegate.java:225)
> at org.eclipse.swt.browser.WebResourceLoadDelegate$1.method3(WebResource
> LoadDelegate.java:45)
> at org.eclipse.swt.internal.ole.win32.COMObject.callback3(COMObject.java
> :92)
> at org.eclipse.swt.internal.win32.OS.SetFocus(Native Method)
> at org.eclipse.swt.browser.WebKit$4.handleEvent(WebKit.java:650)
> at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84)
> at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1053)
> at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1077)
> at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1058)
> at org.eclipse.swt.widgets.Control.sendFocusEvent(Control.java:2822)
> at org.eclipse.swt.widgets.Widget.wmSetFocus(Widget.java:2417)
> at org.eclipse.swt.widgets.Control.WM_SETFOCUS(Control.java:5152)
> at org.eclipse.swt.widgets.Control.windowProc(Control.java:4598)
> at org.eclipse.swt.widgets.Display.windowProc(Display.java:4976)
> at org.eclipse.swt.internal.win32.OS.VtblCall(Native Method)
> at org.eclipse.swt.internal.webkit.IWebView.setHostWindow(IWebView.java:
> 76)
> at org.eclipse.swt.browser.WebKit.onDispose(WebKit.java:1064)
> at org.eclipse.swt.browser.WebKit$4.handleEvent(WebKit.java:646)
> at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84)
> at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1053)
> at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1077)
> at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1058)
> at org.eclipse.swt.widgets.Widget.release(Widget.java:808)
> at org.eclipse.swt.widgets.Composite.releaseChildren(Composite.java:873)
> at org.eclipse.swt.widgets.Widget.release(Widget.java:811)
> at org.eclipse.swt.widgets.Composite.releaseChildren(Composite.java:873)
> at org.eclipse.swt.widgets.Widget.release(Widget.java:811)
> at org.eclipse.swt.widgets.Composite.releaseChildren(Composite.java:873)
> at org.eclipse.swt.widgets.Widget.release(Widget.java:811)
> at org.eclipse.swt.widgets.Composite.releaseChildren(Composite.java:873)
> at org.eclipse.swt.widgets.Widget.release(Widget.java:811)
> at org.eclipse.swt.widgets.Composite.releaseChildren(Composite.java:873)
> at org.eclipse.swt.widgets.Canvas.releaseChildren(Canvas.java:167)
> at org.eclipse.swt.widgets.Decorations.releaseChildren(Decorations.java:
> 790)
> at org.eclipse.swt.widgets.Shell.releaseChildren(Shell.java:1290)
> at org.eclipse.swt.widgets.Widget.release(Widget.java:811)
> at org.eclipse.swt.widgets.Widget.dispose(Widget.java:446)
> at org.eclipse.swt.widgets.Decorations.dispose(Decorations.java:448)
> at org.eclipse.swt.widgets.Shell.dispose(Shell.java:715)
> at org.jboss.tools.vpe.browsersim.ui.BrowserSim.setSelectedDevice(Browse
> rSim.java:673)
> at org.jboss.tools.vpe.browsersim.ui.BrowserSim$11$1.update(BrowserSim.j
> ava:433)
> at java.util.Observable.notifyObservers(Unknown Source)
> at java.util.Observable.notifyObservers(Unknown Source)
> at org.jboss.tools.vpe.browsersim.ui.BrowserSim$22.widgetSelected(Browse
> rSim.java:651)
> 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.Widget.sendEvent(Widget.java:1053)
> at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:4169)
> at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3758)
> at org.jboss.tools.vpe.browsersim.ui.BrowserSim.main(BrowserSim.java:156
> )
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
> at java.lang.reflect.Method.invoke(Unknown Source)
> at org.swtjar.SWTLoader.main(SWTLoader.java:38)
> {code}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 2 months
[JBoss JIRA] (JBIDE-13490) org.jboss.tools.jst.jsp.test.commands.KeyBindingsTest failure for Eclipse 4.3.0.M5
by Victor Rubezhny (JIRA)
[ https://issues.jboss.org/browse/JBIDE-13490?page=com.atlassian.jira.plugi... ]
Victor Rubezhny commented on JBIDE-13490:
-----------------------------------------
BugZilla issue is created: [Bug 400354|https://bugs.eclipse.org/bugs/show_bug.cgi?id=400354]
The key combination doesn't work in WTP's WebPageEditor too. It seems that its a common problem for WTP Multipage Editors.
> org.jboss.tools.jst.jsp.test.commands.KeyBindingsTest failure for Eclipse 4.3.0.M5
> ----------------------------------------------------------------------------------
>
> Key: JBIDE-13490
> URL: https://issues.jboss.org/browse/JBIDE-13490
> Project: Tools (JBoss Tools)
> Issue Type: Sub-task
> Components: common/jst/core
> Affects Versions: 4.1.0.Alpha1
> Reporter: Alexey Kazakov
> Assignee: Victor Rubezhny
> Fix For: 4.1.0.Alpha2
>
>
> {code}
> -------------------------------------------------------------------------------
> Test set: org.jboss.tools.jst.jsp.test.JstJspAllTests
> -------------------------------------------------------------------------------
> Tests run: 21, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 66.752 sec <<< FAILURE!
> testKeyBindings(org.jboss.tools.jst.jsp.test.commands.KeyBindingsTest) Time elapsed: 1.601 sec <<< FAILURE!
> junit.framework.AssertionFailedError: Command found but cannot be executed for 'Perfect Match' keystroke CTRL+D
> at junit.framework.Assert.fail(Assert.java:50)
> at junit.framework.Assert.assertTrue(Assert.java:20)
> at junit.framework.Assert.assertNotNull(Assert.java:218)
> at org.jboss.tools.jst.jsp.test.commands.KeyBindingsTest.doTestKeyBindingsOnPage(KeyBindingsTest.java:97)
> at org.jboss.tools.jst.jsp.test.commands.KeyBindingsTest.testKeyBindings(KeyBindingsTest.java:70)
> {code}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
13 years, 2 months