[JBoss JIRA] (JBIDE-12467) Unable to Run Browsersim in Windows7 64b + JRE7 32b
by Vlado Pakan (JIRA)
[ https://issues.jboss.org/browse/JBIDE-12467?page=com.atlassian.jira.plugi... ]
Vlado Pakan closed JBIDE-12467.
-------------------------------
Verified with JBT Alpha1-v20130909-0110-B392
> Unable to Run Browsersim in Windows7 64b + JRE7 32b
> ---------------------------------------------------
>
> Key: JBIDE-12467
> URL: https://issues.jboss.org/browse/JBIDE-12467
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: browsersim
> Affects Versions: 3.3.0.Final
> Environment: windows 7 64bits
> jdk 7_06 32bits
> JBDS 5.0.0.GA
> *** System properties:
> awt.toolkit=sun.awt.windows.WToolkit
> eclipse.application=org.eclipse.ui.ide.workbench
> eclipse.commands=-os
> win32
> -ws
> win32
> -arch
> x86
> -showsplash
> -launcher
> D:\jbdevstudio-5.0.0.GA-32b\.\studio\jbdevstudio.exe
> -name
> Jbdevstudio
> --launcher.library
> D:\jbdevstudio-5.0.0.GA-32b\.\studio\plugins\org.eclipse.equinox.launcher.win32.win32.x86_1.1.100.v20110502\eclipse_1406.dll
> -startup
> D:\jbdevstudio-5.0.0.GA-32b\.\studio\plugins\org.eclipse.equinox.launcher_1.2.0.v20110502.jar
> --launcher.overrideVmargs
> -exitdata
> 1bb0_74
> -product
> com.jboss.jbds.product.product
> -vm
> D:\Dev\Java\32b\jdk1.7.0_06\bin\javaw.exe
> eclipse.home.location=file:/D:/jbdevstudio-5.0.0.GA-32b/studio/
> eclipse.launcher=D:\jbdevstudio-5.0.0.GA-32b\.\studio\jbdevstudio.exe
> eclipse.launcher.name=Jbdevstudio
> eclipse.p2.data.area=@config.dir/../p2/
> eclipse.p2.profile=jbds
> eclipse.product=com.jboss.jbds.product.product
> eclipse.startTime=1345707935333
> eclipse.vm=D:\Dev\Java\32b\jdk1.7.0_06\bin\javaw.exe
> eclipse.vmargs=-Xms512m
> -Xmx1024m
> -Djboss.discovery.directory.url=https://devstudio.jboss.com/updates/5.0/devstudio-directory.xml
> -Dosgi.instance.area.default=(a)user.home/workspace
> -XX:MaxPermSize=256m
> -jar
> D:\jbdevstudio-5.0.0.GA-32b\.\studio\plugins\org.eclipse.equinox.launcher_1.2.0.v20110502.jar
> equinox.use.ds=true
> Reporter: Fred Bricon
> Assignee: Yahor Radtsevich
> Priority: Blocker
> Labels: upstream
> Fix For: 4.1.0.Final
>
> Attachments: JBIDE12467.patch, jbosstools-diagnostics-20120823094000.zip, new-message-screenshot.png
>
>
> I run into the same problem as reported in https://community.jboss.org/message/755274
> From what I read in https://community.jboss.org/wiki/BrowserSimFAQ, I have iTunes and quicktime installed and yet I get
> !https://community.jboss.org/servlet/JiveServlet/download/755274-64810/browsersim_error.png!
> *Update:*
> This is an upstream issue: https://bugs.eclipse.org/388469
--
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
12 years, 7 months
[JBoss JIRA] (JBDS-2623) Create target platform for mirrored parts of Central / 3rd Party Extras
by Max Rydahl Andersen (JIRA)
[ https://issues.jboss.org/browse/JBDS-2623?page=com.atlassian.jira.plugin.... ]
Max Rydahl Andersen commented on JBDS-2623:
-------------------------------------------
noticed: https://github.com/jbosstools/jbosstools-discovery/pull/36/files
something smells when orbit versions needs rolling back...any idea why that is needed ?
> Create target platform for mirrored parts of Central / 3rd Party Extras
> -----------------------------------------------------------------------
>
> Key: JBDS-2623
> URL: https://issues.jboss.org/browse/JBDS-2623
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Feature Request
> Security Level: Public(Everyone can see)
> Components: 3rd-party-certification, 3rd-party-dependencies, central, requirements, updatesite, upstream
> Affects Versions: 7.0.0.Beta1
> Reporter: Nick Boldt
> Assignee: Nick Boldt
> Fix For: 7.1.x
>
> Attachments: 2623-manual-hack.png, 2623-p2browser-shows-datanucleus-missing.png, 2623-remove-and-regen.png
>
>
> As discussed in JBDS-2486 ( https://issues.jboss.org/browse/JBDS-2486?focusedCommentId=12770186&page=... ) we need to produce a target file for use with Central.
> Goal here would be to build the Extras site (used by Central) as a TP update site rather than a composite of mirrors, which would provide us with a manifest of exactly which versions of these duped IUs were to be contained in the Extras site. If something bad happens, we can add duplicate versions of IUs to the TP and know exactly why we include both Jetty 8.1.3 and 8.1.9 (for example) or two different spins of WindowBuilder. This would mean it wouldn't matter if we filtered content out of the mirrors, because we'd be handling the filtering in a single place (extras.target) rather than multiple build.xml files.
> In future, we would:
> * mirror the individual upstream projects into /updates/requirements/<project> [on dl.jb.org]
> * mirror the individual upstream projects into /updates/requirements/<project> [on www.qa]
> * produce an aggregate of the stuff that Central needs, and publish that instead of the composite [on dl.jb.org]
> * produce an aggregate of the stuff that Central needs, and publish that instead of the composite [on www.qa]
> * produce an aggregate of the stuff that Central needs, and publish that instead of the composite [on ds.jb.com]
> * add a whole new aggregate for old + new content
--
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
12 years, 7 months
[JBoss JIRA] (JBIDE-15494) Software/Update page - Cannot create temporary directory
by Max Rydahl Andersen (JIRA)
[ https://issues.jboss.org/browse/JBIDE-15494?page=com.atlassian.jira.plugi... ]
Max Rydahl Andersen updated JBIDE-15494:
----------------------------------------
Workaround Description: jdk_1.7.0_40 has a bug in tmp file creation. Use 1.7.0_25 or earlier works fine until we find a way to patch it.
Workaround: Workaround Exists
> Software/Update page - Cannot create temporary directory
> --------------------------------------------------------
>
> Key: JBIDE-15494
> URL: https://issues.jboss.org/browse/JBIDE-15494
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: central
> Affects Versions: 4.1.0.Final, 4.1.1.Alpha1
> Reporter: Radim Hopp
> Assignee: Fred Bricon
> Priority: Blocker
> Fix For: 4.1.1.Alpha2
>
>
> Recently, Software/Update page of JBoss Central stopped working (No Connectors Found).
> Error log:
> {noformat}
> Cannot download bundle at http://download.jboss.org/jbosstools/updates/development/kepler/plugins/o...: Unable to create temporary file
> {noformat}
> {noformat}
> a.io.IOException: Unable to create temporary file
> at java.io.File$TempDirectory.generateFile(File.java:1891)
> at java.io.File.createTempFile(File.java:1979)
> at org.jboss.tools.project.examples.internal.discovery.xpl.RemoteExternalBundleDiscoveryStrategy$DownloadBundleJob.call(RemoteExternalBundleDiscoveryStrategy.java:217)
> at org.jboss.tools.project.examples.internal.discovery.xpl.RemoteExternalBundleDiscoveryStrategy$DownloadBundleJob.call(RemoteExternalBundleDiscoveryStrategy.java:1)
> at java.util.concurrent.FutureTask.run(FutureTask.java:262)
> at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
> at java.lang.Thread.run(Thread.java:724)
> {noformat}
> This issue affects both JBDS and JBT, both not only in 7.1.0 (4.1.1) but also in 7.0.0.Final (4.1.0.Final), thus it's marked as blocker.
--
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
12 years, 7 months
[JBoss JIRA] (JBTIS-171) Don't override other connectors in discovery.xml
by Max Rydahl Andersen (JIRA)
[ https://issues.jboss.org/browse/JBTIS-171?page=com.atlassian.jira.plugin.... ]
Max Rydahl Andersen commented on JBTIS-171:
-------------------------------------------
If JBDS-IS site now 'merges' in a specific version of JBDS(in this case JBDS 7.0.0.GA) how do I test JBDS-IS with JBDS 7.1.0.GA ? Do we then now need to rebuild JBDS-IS even for this ?
I'm not following why we insist on having JBDS-IS sites be basically a new repackaging of JBDS since then we are truly *locking* the releases together even harder than before :/
> Don't override other connectors in discovery.xml
> ------------------------------------------------
>
> Key: JBTIS-171
> URL: https://issues.jboss.org/browse/JBTIS-171
> Project: JBoss Tools Integration Stack
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: distribution
> Reporter: Max Rydahl Andersen
> Assignee: Paul Leacu
>
> Currently this is in discovery plugin:
> siteUrl="$\{jboss.discovery.site.url:https://devstudio.jboss.com/updates/7.0-development/central/integration-stack/}"
>
> And instructions to test it says:
> -vmargs -Djboss.discovery.directory.url=http://www.qa.jboss.com/binaries/RHDS/discovery/integration/integration-stack/7.0.0.Beta1/devstudio-integration-stack-directory.xml -Djboss.discovery.site.url=http://www.qa.jboss.com/binaries/RHDS/discovery/integration/integration-stack/7.0.0.Beta1
> This is all great but it disables all other connectors in JBDS/eclipse thus it makes it hard to get together.
> I suggest you use your own specific site url instead, something like:
> siteUrl="$\{jboss.discovery.integration-stack.site.url:https://devstudio.jboss.com/updates/7.0-development/central/integration-stack/}"
> Then the base connectors will still work.
> We might even consider using recursive properties to allow for a global override, this would need changing in both IS And core discovery.xml to the tune of:
> in core: siteUrl="$\{jboss.global.discovery.site.url,jboss.discovery.site.url:https://devstudio.jboss.com/updates/7.0-development/central/core}"
> in stack:
> siteUrl="$\{jboss.global.discovery.site.url,jboss.discovery.integration-stack.site.url:https://devstudio.jboss.com/updates/7.0-development/central/integration-stack/}"
--
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
12 years, 7 months
[JBoss JIRA] (JBIDE-14973) Blocked recursive attempt to activate part
by Vlado Pakan (JIRA)
[ https://issues.jboss.org/browse/JBIDE-14973?page=com.atlassian.jira.plugi... ]
Vlado Pakan closed JBIDE-14973.
-------------------------------
> Blocked recursive attempt to activate part
> ------------------------------------------
>
> Key: JBIDE-14973
> URL: https://issues.jboss.org/browse/JBIDE-14973
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: visual-page-editor-core
> Affects Versions: 4.1.0.CR1
> Reporter: Alexey Kazakov
> Assignee: Konstantin Marmalyukov
> Labels: upstream
> Fix For: 4.1.0.Final
>
>
> I just opened an HTML5 file with JBoss HTML Editor (Source tab)
> And then I opened an XHTML file from another project (Source tab).
> When I switch between editors I get the following warning in Error log:
> {code}
> eclipse.buildId=unknown
> java.version=1.7.0_09
> java.vendor=Oracle Corporation
> BootLoader constants: OS=linux, ARCH=x86_64, WS=gtk, NL=en_US
> Framework arguments: -product org.eclipse.platform.ide
> Command-line arguments: -product org.eclipse.platform.ide -data /home/igels/Java/eclipse-4.3/workspace/runtime/runtime-JBT -dev file:/home/igels/Java/eclipse-4.3/workspace/designtime/contribution/.metadata/.plugins/org.eclipse.pde.core/JBT/dev.properties -os linux -ws gtk -arch x86_64 -consoleLog
> Warning
> Fri Jun 21 16:25:51 PDT 2013
> Blocked recursive attempt to activate part
> java.lang.IllegalStateException
> at org.eclipse.e4.ui.workbench.renderers.swt.ContributedPartRenderer$2.setFocus(ContributedPartRenderer.java:119)
> at org.eclipse.swt.custom.CTabItem.setFocus(CTabItem.java:329)
> at org.eclipse.swt.custom.CTabFolder.setFocus(CTabFolder.java:2509)
> at org.eclipse.swt.widgets.Control.fixFocus(Control.java:206)
> at org.eclipse.swt.widgets.Control.setVisible(Control.java:4791)
> at org.eclipse.swt.custom.CTabFolder.setSelection(CTabFolder.java:3049)
> at org.eclipse.swt.custom.CTabFolder.setSelection(CTabFolder.java:3006)
> at org.eclipse.e4.ui.workbench.renderers.swt.StackRenderer.showTab(StackRenderer.java:1101)
> at org.eclipse.e4.ui.workbench.renderers.swt.LazyStackRenderer$1.handleEvent(LazyStackRenderer.java:66)
> at org.eclipse.e4.ui.services.internal.events.UIEventHandler$1.run(UIEventHandler.java:41)
> at org.eclipse.swt.widgets.Synchronizer.syncExec(Synchronizer.java:180)
> at org.eclipse.ui.internal.UISynchronizer.syncExec(UISynchronizer.java:150)
> at org.eclipse.swt.widgets.Display.syncExec(Display.java:4491)
> at org.eclipse.e4.ui.internal.workbench.swt.E4Application$1.syncExec(E4Application.java:205)
> at org.eclipse.e4.ui.services.internal.events.UIEventHandler.handleEvent(UIEventHandler.java:38)
> at org.eclipse.equinox.internal.event.EventHandlerWrapper.handleEvent(EventHandlerWrapper.java:197)
> at org.eclipse.equinox.internal.event.EventHandlerTracker.dispatchEvent(EventHandlerTracker.java:197)
> at org.eclipse.equinox.internal.event.EventHandlerTracker.dispatchEvent(EventHandlerTracker.java:1)
> at org.eclipse.osgi.framework.eventmgr.EventManager.dispatchEvent(EventManager.java:230)
> at org.eclipse.osgi.framework.eventmgr.ListenerQueue.dispatchEventSynchronous(ListenerQueue.java:148)
> at org.eclipse.equinox.internal.event.EventAdminImpl.dispatchEvent(EventAdminImpl.java:135)
> at org.eclipse.equinox.internal.event.EventAdminImpl.sendEvent(EventAdminImpl.java:78)
> at org.eclipse.equinox.internal.event.EventComponent.sendEvent(EventComponent.java:39)
> at org.eclipse.e4.ui.services.internal.events.EventBroker.send(EventBroker.java:80)
> at org.eclipse.e4.ui.internal.workbench.UIEventPublisher.notifyChanged(UIEventPublisher.java:58)
> at org.eclipse.emf.common.notify.impl.BasicNotifierImpl.eNotify(BasicNotifierImpl.java:374)
> at org.eclipse.e4.ui.model.application.ui.impl.ElementContainerImpl.setSelectedElement(ElementContainerImpl.java:171)
> at org.eclipse.e4.ui.internal.workbench.ModelServiceImpl.showElementInWindow(ModelServiceImpl.java:576)
> at org.eclipse.e4.ui.internal.workbench.ModelServiceImpl.bringToTop(ModelServiceImpl.java:543)
> at org.eclipse.e4.ui.internal.workbench.PartServiceImpl.delegateBringToTop(PartServiceImpl.java:605)
> at org.eclipse.e4.ui.internal.workbench.PartServiceImpl.activate(PartServiceImpl.java:585)
> at org.eclipse.e4.ui.internal.workbench.PartServiceImpl.setPart(PartServiceImpl.java:158)
> at sun.reflect.GeneratedMethodAccessor30.invoke(Unknown Source)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:601)
> at org.eclipse.e4.core.internal.di.MethodRequestor.execute(MethodRequestor.java:56)
> at org.eclipse.e4.core.internal.contexts.ContextObjectSupplier$ContextInjectionListener.update(ContextObjectSupplier.java:88)
> at org.eclipse.e4.core.internal.contexts.TrackableComputationExt.update(TrackableComputationExt.java:107)
> at org.eclipse.e4.core.internal.contexts.EclipseContext.processScheduled(EclipseContext.java:328)
> at org.eclipse.e4.core.internal.contexts.EclipseContext.set(EclipseContext.java:342)
> at org.eclipse.e4.core.internal.contexts.EclipseContext.activate(EclipseContext.java:625)
> at org.eclipse.e4.core.internal.contexts.EclipseContext.activateBranch(EclipseContext.java:630)
> at org.eclipse.e4.ui.internal.workbench.PartActivationHistory.activate(PartActivationHistory.java:52)
> at org.eclipse.e4.ui.internal.workbench.PartServiceImpl.activate(PartServiceImpl.java:588)
> at org.eclipse.e4.ui.internal.workbench.PartServiceImpl.activate(PartServiceImpl.java:539)
> at org.eclipse.e4.ui.internal.workbench.swt.AbstractPartRenderer.activate(AbstractPartRenderer.java:104)
> at org.eclipse.e4.ui.workbench.renderers.swt.ContributedPartRenderer$1.handleEvent(ContributedPartRenderer.java:59)
> at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84)
> at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1392)
> at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1416)
> at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1401)
> at org.eclipse.swt.widgets.Shell.setActiveControl(Shell.java:1675)
> at org.eclipse.swt.widgets.Shell.setActiveControl(Shell.java:1638)
> at org.eclipse.swt.widgets.Control.sendFocusEvent(Control.java:3851)
> at org.eclipse.swt.widgets.Control.gtk_event_after(Control.java:3119)
> at org.eclipse.swt.widgets.Widget.windowProc(Widget.java:2085)
> at org.eclipse.swt.widgets.Control.windowProc(Control.java:5467)
> at org.eclipse.swt.widgets.Display.windowProc(Display.java:4569)
> at org.eclipse.swt.internal.gtk.OS._gtk_widget_grab_focus(Native Method)
> at org.eclipse.swt.internal.gtk.OS.gtk_widget_grab_focus(OS.java:13721)
> at org.eclipse.swt.widgets.Control.forceFocus(Control.java:2438)
> at org.eclipse.swt.widgets.Composite.forceFocus(Composite.java:546)
> at org.eclipse.swt.widgets.Control.forceFocus(Control.java:2431)
> at org.eclipse.swt.widgets.Control.setFocus(Control.java:4284)
> at org.eclipse.swt.widgets.Composite.setFocus(Composite.java:1410)
> at org.jboss.tools.vpe.xulrunner.browser.XulRunnerBrowser.setFocus(XulRunnerBrowser.java:163)
> at org.jboss.tools.vpe.editor.mozilla.MozillaEditor.setFocus(MozillaEditor.java:795)
> at org.jboss.tools.vpe.editor.VpeEditorPart.setFocus(VpeEditorPart.java:869)
> at org.jboss.tools.jst.jsp.jspeditor.JSPMultiPageEditorPart.setFocus(JSPMultiPageEditorPart.java:186)
> at org.jboss.tools.jst.jsp.jspeditor.JSPMultiPageEditorPart.setFocus(JSPMultiPageEditorPart.java:171)
> at org.eclipse.ui.internal.e4.compatibility.CompatibilityPart.delegateSetFocus(CompatibilityPart.java:192)
> at sun.reflect.GeneratedMethodAccessor47.invoke(Unknown Source)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:601)
> at org.eclipse.e4.core.internal.di.MethodRequestor.execute(MethodRequestor.java:56)
> at org.eclipse.e4.core.internal.di.InjectorImpl.invokeUsingClass(InjectorImpl.java:243)
> at org.eclipse.e4.core.internal.di.InjectorImpl.invokeUsingClass(InjectorImpl.java:249)
> at org.eclipse.e4.core.internal.di.InjectorImpl.invoke(InjectorImpl.java:220)
> at org.eclipse.e4.core.contexts.ContextInjectionFactory.invoke(ContextInjectionFactory.java:107)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.focusGui(PartRenderingEngine.java:763)
> at org.eclipse.e4.ui.workbench.renderers.swt.ContributedPartRenderer$2.setFocus(ContributedPartRenderer.java:102)
> at org.eclipse.swt.custom.CTabItem.setFocus(CTabItem.java:329)
> at org.eclipse.swt.custom.CTabFolder.setFocus(CTabFolder.java:2509)
> at org.eclipse.swt.widgets.Control.fixFocus(Control.java:206)
> at org.eclipse.swt.widgets.Control.setVisible(Control.java:4791)
> at org.eclipse.swt.custom.CTabFolder.setSelection(CTabFolder.java:3049)
> at org.eclipse.swt.custom.CTabFolder.setSelection(CTabFolder.java:3057)
> at org.eclipse.swt.custom.CTabFolder.onMouse(CTabFolder.java:1753)
> at org.eclipse.swt.custom.CTabFolder$1.handleEvent(CTabFolder.java:278)
> at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84)
> at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1392)
> at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3742)
> at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3363)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$9.run(PartRenderingEngine.java:1113)
> at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.run(PartRenderingEngine.java:997)
> at org.eclipse.e4.ui.internal.workbench.E4Workbench.createAndRunUI(E4Workbench.java:138)
> at org.eclipse.ui.internal.Workbench$5.run(Workbench.java:610)
> at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332)
> at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:567)
> at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:150)
> at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:124)
> at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:196)
> at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:110)
> at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:79)
> at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:354)
> at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:181)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:601)
> at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:636)
> at org.eclipse.equinox.launcher.Main.basicRun(Main.java:591)
> at org.eclipse.equinox.launcher.Main.run(Main.java:1450)
> at org.eclipse.equinox.launcher.Main.main(Main.java:1426)
> {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
12 years, 7 months
[JBoss JIRA] (JBIDE-15141) Closing synchronized BrowserSim is hiding original BrowserSim window bellow other app window
by Vlado Pakan (JIRA)
[ https://issues.jboss.org/browse/JBIDE-15141?page=com.atlassian.jira.plugi... ]
Vlado Pakan closed JBIDE-15141.
-------------------------------
> Closing synchronized BrowserSim is hiding original BrowserSim window bellow other app window
> --------------------------------------------------------------------------------------------
>
> Key: JBIDE-15141
> URL: https://issues.jboss.org/browse/JBIDE-15141
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: browsersim
> Affects Versions: 4.1.0.CR1
> Environment: Fedora 14 32 bit Gnome JBT 4.1.0.CR1-v20130701-1919-B372
> Reporter: Vlado Pakan
> Assignee: Konstantin Marmalyukov
> Priority: Minor
> Fix For: 4.1.0.Final
>
> Attachments: browsersimhiden.ogv
>
>
> 1. Open BrowserSim and at least one synchronized BrowserSim
> 2. Activate JBT window (not maximized) in the position when it's covering/hiding original BrowserSim window and synchronized BrowserSim window is visible
> 3. Click on synchronized BrowserSim window
> ASSERT: Both BrowserSims are visible
> 4. Close synchronized BrowserSim window
> ERROR: Original BrowserSim window is moved to background hidden bellow JBT window. It should stay visible on top of JBT window
> See attached screencast browsersimhiden.ogv
--
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
12 years, 7 months