September 2013 - jbosstools-issues

[JBoss JIRA] (JBIDE-15421) Usage Analytics New and Noteworthy for 4.1.1.Alpha1

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15421?page=com.atlassian.jira.plugi... ] Denis Golovin closed JBIDE-15421. --------------------------------- Resolution: Done > Usage Analytics New and Noteworthy for 4.1.1.Alpha1 > --------------------------------------------------- > > Key: JBIDE-15421 > URL: https://issues.jboss.org/browse/JBIDE-15421 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: usage > Reporter: Max Rydahl Andersen > Priority: Critical > Fix For: 4.1.1.Alpha1 > > > This [query|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+an...] contains the search for the specific component(s), to see all, use this [query|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+an...]. > If Usage Analytics is not listed here check if there are issues that should be added and add them. > Document the ones relevant for Usage Analytics by adding to [whatsnew|https://github.com/jbosstools/jbosstools-documentation/tree/mast...] and submit a pullrequest. > If no news for this component please reject and close this issue. -- 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, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-15418) GWT New and Noteworthy for 4.1.1.Alpha1

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15418?page=com.atlassian.jira.plugi... ] Denis Golovin closed JBIDE-15418. --------------------------------- Resolution: Rejected > GWT New and Noteworthy for 4.1.1.Alpha1 > --------------------------------------- > > Key: JBIDE-15418 > URL: https://issues.jboss.org/browse/JBIDE-15418 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: gwt > Reporter: Max Rydahl Andersen > Priority: Critical > Fix For: 4.1.1.Alpha1 > > > This [query|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+an...] contains the search for the specific component(s), to see all, use this [query|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+an...]. > If GWT is not listed here check if there are issues that should be added and add them. > Document the ones relevant for GWT by adding to [whatsnew|https://github.com/jbosstools/jbosstools-documentation/tree/mast...] and submit a pullrequest. > If no news for this component please reject and close this issue. -- 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, 6 months

1
0
0 / 0

[JBoss JIRA] (JBDS-2717) .FeatureNotFoundException after importing petclinic WFK Spring example

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBDS-2717?page=com.atlassian.jira.plugin.... ] Fred Bricon updated JBDS-2717: ------------------------------ Fix Version/s: 7.1.0.Beta1 (was: 7.1.0.Alpha2) > .FeatureNotFoundException after importing petclinic WFK Spring example > ---------------------------------------------------------------------- > > Key: JBDS-2717 > URL: https://issues.jboss.org/browse/JBDS-2717 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: 3rd-party-certification, upstream > Affects Versions: 7.0.0.GA > Environment: JBDS 7.0.0.GA, L64, Spring IDE 2.3 installed from JBoss Central > Reporter: Jiri Peterka > Assignee: Fred Bricon > Fix For: 7.1.0.Beta1 > > > After importing petclinic project I get: > {code} > org.eclipse.emf.ecore.resource.impl.ResourceSetImpl$1DiagnosticWrappedException: org.eclipse.emf.ecore.xmi.FeatureNotFoundException: Feature 'filter-name' not found. (platform:/resource/petclinic/target/m2e-wtp/web-resources/WEB-INF/web.xml, 132, 16) > at org.eclipse.emf.ecore.resource.impl.ResourceSetImpl.handleDemandLoadException(ResourceSetImpl.java:319) > at org.eclipse.emf.ecore.resource.impl.ResourceSetImpl.demandLoadHelper(ResourceSetImpl.java:278) > at org.eclipse.jem.internal.util.emf.workbench.ProjectResourceSetImpl.getResource(ProjectResourceSetImpl.java:1064) > at org.eclipse.jst.jee.model.internal.JEE5ModelProvider.getModelResource(JEE5ModelProvider.java:169) > at org.eclipse.jst.jee.model.internal.Web25ModelProvider.getModelObject(Web25ModelProvider.java:44) > at org.eclipse.jst.jee.model.internal.JEE5ModelProvider.getModelObject(JEE5ModelProvider.java:215) > at org.eclipse.jst.jee.model.internal.common.AbstractMergedModelProvider.getLastModificationTimeOfDDFile(AbstractMergedModelProvider.java:235) > at org.eclipse.jst.jee.model.internal.common.AbstractMergedModelProvider.hasToReloadModel(AbstractMergedModelProvider.java:229) > at org.eclipse.jst.jee.model.internal.common.AbstractMergedModelProvider.getMergedModel(AbstractMergedModelProvider.java:218) > at org.eclipse.jst.jee.model.internal.common.AbstractMergedModelProvider.getModelObject(AbstractMergedModelProvider.java:139) > at org.eclipse.jst.jee.ui.internal.navigator.JEE5ContentProvider.getCachedContentProvider(JEE5ContentProvider.java:98) > at org.eclipse.jst.jee.ui.internal.navigator.Web25ContentProvider.getChildren(Web25ContentProvider.java:35) > at org.eclipse.ui.internal.navigator.extensions.SafeDelegateTreeContentProvider.getChildren(SafeDelegateTreeContentProvider.java:96) > at org.eclipse.ui.internal.navigator.extensions.SafeDelegateTreeContentProvider.getChildren(SafeDelegateTreeContentProvider.java:275) > at org.eclipse.ui.internal.navigator.extensions.SafeDelegateTreeContentProvider.getChildren(SafeDelegateTreeContentProvider.java:94) > at org.eclipse.ui.internal.navigator.NavigatorContentServiceContentProvider$1.run(NavigatorContentServiceContentProvider.java:152) > at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42) > at org.eclipse.ui.internal.navigator.NavigatorContentServiceContentProvider.internalGetChildren(NavigatorContentServiceContentProvider.java:139) > at org.eclipse.ui.internal.navigator.NavigatorContentServiceContentProvider.getChildren(NavigatorContentServiceContentProvider.java:125) > at org.eclipse.jface.viewers.AbstractTreeViewer.getRawChildren(AbstractTreeViewer.java:1367) > at org.eclipse.jface.viewers.TreeViewer.getRawChildren(TreeViewer.java:391) > at org.eclipse.jface.viewers.StructuredViewer.getFilteredChildren(StructuredViewer.java:917) > at org.eclipse.jface.viewers.AbstractTreeViewer.getSortedChildren(AbstractTreeViewer.java:620) > at org.eclipse.jface.viewers.AbstractTreeViewer.updateChildren(AbstractTreeViewer.java:2643) > at org.eclipse.jface.viewers.AbstractTreeViewer.internalRefreshStruct(AbstractTreeViewer.java:1923) > at org.eclipse.jface.viewers.TreeViewer.internalRefreshStruct(TreeViewer.java:721) > at org.eclipse.jface.viewers.AbstractTreeViewer.internalRefreshStruct(AbstractTreeViewer.java:1930) > at org.eclipse.jface.viewers.TreeViewer.internalRefreshStruct(TreeViewer.java:721) > at org.eclipse.jface.viewers.AbstractTreeViewer.internalRefresh(AbstractTreeViewer.java:1898) > at org.eclipse.jface.viewers.AbstractTreeViewer.internalRefresh(AbstractTreeViewer.java:1855) > at org.eclipse.ui.navigator.CommonViewer.internalRefresh(CommonViewer.java:561) > at org.eclipse.jface.viewers.StructuredViewer$8.run(StructuredViewer.java:1535) > at org.eclipse.jface.viewers.StructuredViewer.preservingSelection(StructuredViewer.java:1443) > at org.eclipse.jface.viewers.TreeViewer.preservingSelection(TreeViewer.java:403) > at org.eclipse.jface.viewers.StructuredViewer.preservingSelection(StructuredViewer.java:1404) > at org.eclipse.jface.viewers.StructuredViewer.refresh(StructuredViewer.java:1533) > at org.eclipse.jface.viewers.ColumnViewer.refresh(ColumnViewer.java:555) > at org.eclipse.ui.navigator.CommonViewer.refresh(CommonViewer.java:353) > at org.eclipse.ui.navigator.CommonViewer.refresh(CommonViewer.java:510) > at org.eclipse.ui.internal.navigator.resources.workbench.ResourceExtensionContentProvider$3.run(ResourceExtensionContentProvider.java:294) > at org.eclipse.ui.internal.navigator.resources.workbench.ResourceExtensionContentProvider.runUpdates(ResourceExtensionContentProvider.java:306) > at org.eclipse.ui.internal.navigator.resources.workbench.ResourceExtensionContentProvider.access$1(ResourceExtensionContentProvider.java:303) > at org.eclipse.ui.internal.navigator.resources.workbench.ResourceExtensionContentProvider$1.run(ResourceExtensionContentProvider.java:129) > at org.eclipse.swt.widgets.RunnableLock.run(RunnableLock.java:35) > at org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchronizer.java:135) > at org.eclipse.swt.widgets.Display.runAsyncMessages(Display.java:3717) > at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3366) > 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:39) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) > at java.lang.reflect.Method.invoke(Method.java:597) > 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) > Caused by: org.eclipse.emf.ecore.xmi.FeatureNotFoundException: Feature 'filter-name' not found. (platform:/resource/petclinic/target/m2e-wtp/web-resources/WEB-INF/web.xml, 132, 16) > at org.eclipse.emf.ecore.xmi.impl.XMLHandler.reportUnknownFeature(XMLHandler.java:1998) > at org.eclipse.emf.ecore.xmi.impl.XMLHandler.handleUnknownFeature(XMLHandler.java:1962) > at org.eclipse.emf.ecore.xmi.impl.XMIHandler.handleUnknownFeature(XMIHandler.java:145) > at org.eclipse.emf.ecore.xmi.impl.XMLHandler.handleFeature(XMLHandler.java:1906) > at org.eclipse.emf.ecore.xmi.impl.XMLHandler.processElement(XMLHandler.java:1030) > at org.eclipse.emf.ecore.xmi.impl.XMIHandler.processElement(XMIHandler.java:81) > at org.eclipse.emf.ecore.xmi.impl.XMLHandler.startElement(XMLHandler.java:1008) > at org.eclipse.emf.ecore.xmi.impl.XMLHandler.startElement(XMLHandler.java:719) > at org.eclipse.emf.ecore.xmi.impl.XMIHandler.startElement(XMIHandler.java:163) > at com.sun.org.apache.xerces.internal.parsers.AbstractSAXParser.startElement(AbstractSAXParser.java:501) > at com.sun.org.apache.xerces.internal.impl.XMLNSDocumentScannerImpl.scanStartElement(XMLNSDocumentScannerImpl.java:400) > at com.sun.org.apache.xerces.internal.impl.XMLDocumentFragmentScannerImpl$FragmentContentDriver.next(XMLDocumentFragmentScannerImpl.java:2756) > at com.sun.org.apache.xerces.internal.impl.XMLDocumentScannerImpl.next(XMLDocumentScannerImpl.java:647) > at com.sun.org.apache.xerces.internal.impl.XMLNSDocumentScannerImpl.next(XMLNSDocumentScannerImpl.java:140) > at com.sun.org.apache.xerces.internal.impl.XMLDocumentFragmentScannerImpl.scanDocument(XMLDocumentFragmentScannerImpl.java:511) > at com.sun.org.apache.xerces.internal.parsers.XML11Configuration.parse(XML11Configuration.java:808) > at com.sun.org.apache.xerces.internal.parsers.XML11Configuration.parse(XML11Configuration.java:737) > at com.sun.org.apache.xerces.internal.parsers.XMLParser.parse(XMLParser.java:119) > at com.sun.org.apache.xerces.internal.parsers.AbstractSAXParser.parse(AbstractSAXParser.java:1205) > at com.sun.org.apache.xerces.internal.jaxp.SAXParserImpl$JAXPSAXParser.parse(SAXParserImpl.java:522) > at javax.xml.parsers.SAXParser.parse(SAXParser.java:395) > at org.eclipse.emf.ecore.xmi.impl.XMLLoadImpl.load(XMLLoadImpl.java:175) > at org.eclipse.emf.ecore.xmi.impl.XMLResourceImpl.doLoad(XMLResourceImpl.java:253) > at org.eclipse.emf.ecore.resource.impl.ResourceImpl.load(ResourceImpl.java:1518) > at org.eclipse.emf.ecore.resource.impl.ResourceImpl.load(ResourceImpl.java:1297) > at org.eclipse.emf.ecore.resource.impl.ResourceSetImpl.demandLoad(ResourceSetImpl.java:259) > at org.eclipse.jem.internal.util.emf.workbench.ProjectResourceSetImpl.demandLoad(ProjectResourceSetImpl.java:811) > at org.eclipse.emf.ecore.resource.impl.ResourceSetImpl.demandLoadHelper(ResourceSetImpl.java:274) > ... 67 more > {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, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-15364) CLONE - Import Maven Archetype Project Example ignores JBoss Maven Integration preferences

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15364?page=com.atlassian.jira.plugi... ] Fred Bricon updated JBIDE-15364: -------------------------------- Fix Version/s: 4.1.1.Alpha1 (was: 4.1.1.Final) > CLONE - Import Maven Archetype Project Example ignores JBoss Maven Integration preferences > ------------------------------------------------------------------------------------------ > > Key: JBIDE-15364 > URL: https://issues.jboss.org/browse/JBIDE-15364 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: maven, project-examples > Affects Versions: 4.1.0.Beta2 > Reporter: Fred Bricon > Assignee: Fred Bricon > Priority: Critical > Fix For: 4.1.1.Alpha1 > > > Creating projects out of JBoss Central doesn't enable JBoss Tools features like CDI. > This bug is regression of JBIDE-14807 where mandatory execution [Maven->Update Project...] was replaced to update only for projects with "out of date" markers. ArchetypeExamplesWizardPage.finishPage() method disable all configurators before importing projects into workspace and with fix of JBIDE-14807 it leads to new problem when configurators are never being called. -- 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, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-15364) CLONE - Import Maven Archetype Project Example ignores JBoss Maven Integration preferences

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15364?page=com.atlassian.jira.plugi... ] Fred Bricon resolved JBIDE-15364. --------------------------------- Resolution: Done Already fixed in 4.1.1.alpha1 > CLONE - Import Maven Archetype Project Example ignores JBoss Maven Integration preferences > ------------------------------------------------------------------------------------------ > > Key: JBIDE-15364 > URL: https://issues.jboss.org/browse/JBIDE-15364 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: maven, project-examples > Affects Versions: 4.1.0.Beta2 > Reporter: Fred Bricon > Assignee: Fred Bricon > Priority: Critical > Fix For: 4.1.1.Alpha1 > > > Creating projects out of JBoss Central doesn't enable JBoss Tools features like CDI. > This bug is regression of JBIDE-14807 where mandatory execution [Maven->Update Project...] was replaced to update only for projects with "out of date" markers. ArchetypeExamplesWizardPage.finishPage() method disable all configurators before importing projects into workspace and with fix of JBIDE-14807 it leads to new problem when configurators are never being called. -- 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, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-15575) Creation of foundation.ui to hold TaskWizard framework

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15575?page=com.atlassian.jira.plugi... ] Denis Golovin edited comment on JBIDE-15575 at 9/27/13 2:07 PM: ---------------------------------------------------------------- [~rob.stryker] did you see [~adietish] comment on your pull request? Care to answer or comment why foundation plugins need to have code that converts generic Exception into false? How do you expect devs to find out why wizard fragment is not showing up in case of exception? was (Author: dgolovin): [~rob.stryker] did you see [~adietish] comment on your pull request? Care to answer or comment why foundation plugins need to have code that converts generic Exception into false. How do you expect devs to find out why wizard fragment is not showing up in case of exception? > Creation of foundation.ui to hold TaskWizard framework > ------------------------------------------------------ > > Key: JBIDE-15575 > URL: https://issues.jboss.org/browse/JBIDE-15575 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: common/jst/core > Affects Versions: 4.2.0.Alpha1 > Reporter: Rob Stryker > Assignee: Rob Stryker > Fix For: 4.2.0.Alpha1 > > > Creation of a foundation.ui is required for a few reasons: > 1) runtimes should not depend on common. A foundation.ui is needed for that > 2) Hold taskwizard, a framework from wtp internals which is very very useful and many have expressed interest in using. Runtimes will be using this framework very soon and others will convert in the future. -- 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, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-15499) Support drag'n'drop of links to "connectors" similar to marketplace to central for auto install

by Snjezana Peco (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15499?page=com.atlassian.jira.plugi... ] Snjezana Peco commented on JBIDE-15499: --------------------------------------- I have created https://bugs.eclipse.org/bugs/show_bug.cgi?id=418196 > Support drag'n'drop of links to "connectors" similar to marketplace to central for auto install > ----------------------------------------------------------------------------------------------- > > Key: JBIDE-15499 > URL: https://issues.jboss.org/browse/JBIDE-15499 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: central > Reporter: Max Rydahl Andersen > Assignee: Snjezana Peco > Priority: Blocker > Fix For: 4.1.1.Beta1 > > > usecase is that you can have a link to a connector, such as JBDS-IS could be installed by drag'n'drop to jboss tools or jbds. > Similar to eclipse marketplace for marketplace urls something like: > * https://devstudio.jboss.com/central/install?connector=com.jbds.integratio... or > * http://download.jboss.org/jbosstools/central/install?CID=com.jbds.integra... > would install the two connectors named "com.jbds.integration-stack.bpel" and "org.eclipse.m2e" > This would allow drag'n'drop install from html docs. > Consider also supporting this from any clipboard object (eg., dragged from an Acrobat Reader PDF or Microsoft Office doc). Would need to ensure we do lots of platform testing. -- 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, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-15572) OpenShift New and Noteworthy for 4.1.1.Alpha2

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15572?page=com.atlassian.jira.plugi... ] Andre Dietisheim reassigned JBIDE-15572: ---------------------------------------- Assignee: Fred Bricon (was: Andre Dietisheim) plz review and merge > OpenShift New and Noteworthy for 4.1.1.Alpha2 > --------------------------------------------- > > Key: JBIDE-15572 > URL: https://issues.jboss.org/browse/JBIDE-15572 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: openshift > Reporter: Denis Golovin > Assignee: Fred Bricon > Priority: Critical > Fix For: 4.1.1.Alpha2 > > > This [query|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+an...] contains the search for the specific component(s), to see all, use this [query|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+an...]. > If OpenShift is not listed here check if there are issues that should be added and add them. > Document the ones relevant for OpenShift by adding to [whatsnew|https://github.com/jbosstools/jbosstools-documentation/tree/mast...] and submit a pullrequest. > If no news for this component please reject and close this issue. -- 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, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-15578) BrowserSim Screen Capture Fail

by Burr Sutter (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15578?page=com.atlassian.jira.plugi... ] Burr Sutter updated JBIDE-15578: -------------------------------- Attachment: 2013-09-27_1132.png It should look more like this one > BrowserSim Screen Capture Fail > ------------------------------ > > Key: JBIDE-15578 > URL: https://issues.jboss.org/browse/JBIDE-15578 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: browsersim > Reporter: Burr Sutter > Attachments: 2013-09-27_1132.png, browsersim_2013-09-27-113159.png > > > This URL > http://mobile.walmart.com/m/phoenix;jsessionid=612BD65031620D8B8FFFBF9D3A... > See attached image for the screenshot captured - it loses the images in the page. -- 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, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-15578) BrowserSim Screen Capture Fail

by Burr Sutter (JIRA)

Burr Sutter created JBIDE-15578: ----------------------------------- Summary: BrowserSim Screen Capture Fail Key: JBIDE-15578 URL: https://issues.jboss.org/browse/JBIDE-15578 Project: Tools (JBoss Tools) Issue Type: Bug Components: browsersim Reporter: Burr Sutter Attachments: 2013-09-27_1132.png, browsersim_2013-09-27-113159.png This URL http://mobile.walmart.com/m/phoenix;jsessionid=612BD65031620D8B8FFFBF9D3A... See attached image for the screenshot captured - it loses the images in the page. -- 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, 6 months

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jbosstools-issues September 2013