May 2016 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-21177) [CLONE]Livereload doesn't work stable with CordovaSim / BrowserSim

by Pavol Srna (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21177?page=com.atlassian.jira.plugi... ] Pavol Srna closed JBIDE-21177. ------------------------------ Verified in JBT 4.4.0.Alpha1 > [CLONE]Livereload doesn't work stable with CordovaSim / BrowserSim > ------------------------------------------------------------------ > > Key: JBIDE-21177 > URL: https://issues.jboss.org/browse/JBIDE-21177 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: browsersim, cordovasim, livereload > Affects Versions: 4.3.0.CR1 > Reporter: Ilya Buziuk > Assignee: Konstantin Marmalyukov > Priority: Critical > Fix For: 4.4.0.Alpha1 > > > It seems that Livereload stopped working on simple pages like: > {code} > <!DOCTYPE html> > <html> > <head> > <title>Insert title here</title> > </head> > <body> > <h1>Hello World</h1> > </body> > </html> > {code} > But at the same time it works fine with some complex projects like jboss-as-kitchensink-html5-mobile & https://github.com/ibuziuk/cordovasim-demo -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20756) Touch events for BrowserSim are not set properly

by Pavol Srna (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20756?page=com.atlassian.jira.plugi... ] Pavol Srna closed JBIDE-20756. ------------------------------ Verified in JBT 4.4.0.Alpha1. > Touch events for BrowserSim are not set properly > ------------------------------------------------ > > Key: JBIDE-20756 > URL: https://issues.jboss.org/browse/JBIDE-20756 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: browsersim > Affects Versions: 4.3.0.CR1 > Environment: JBDS 9.0.0.CR1-v20150918-0257-B105 Fedora 22 KDE 64bit > Reporter: Vlado Pakan > Assignee: Konstantin Marmalyukov > Fix For: 4.4.0.Alpha1 > > > 1. Create HTML page with this content: > {code:html} > <!DOCTYPE html> > <html> > <head> > <title>sample</title> > <script type="text/javascript"> > function window_onload() { > document.getElementById('touchable').addEventListener('touchstart', function(ev) { > alert('touchstart')}, false); > document.getElementById('touchable').addEventListener('touchend', function(ev) { > alert('touchend')}, false); > document.getElementById('touchable').addEventListener('touchmove', function(ev) { > alert('touchmove')}, false); > } > </script> > </head> > <body onload='window_onload();'> > <div id='touchable'>This element is touchable.</div> > </body> > </html> > {code} > 2. Open this page in BrowserSim > 3. Enable touch events for BrowserSim > 4. Click somewhere within the page in BrowserSim > ERROR: > {noformat} > !JavaScript WARN: Converting `ontouchstart` property to event listener. > !JavaScript ERROR: TypeError: Unable to delete property. on line 118 for file:///.../jboss-touchevents/src/main/webapp/index.html > !JavaScript WARN: Converting `ontouchend` property to event listener. > !JavaScript ERROR: TypeError: Unable to delete property. on line 118 for file:///.../jboss-touchevents/src/main/webapp/index.html > {noformat} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22454) Application Wizard: Build configuration wizard page has redundant environment variables table

by Marián Labuda (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22454?page=com.atlassian.jira.plugi... ] Marián Labuda edited comment on JBIDE-22454 at 5/31/16 4:39 AM: ---------------------------------------------------------------- It is understandable because of different wizard pages (Build vs Deployment config). Although I haven't noticed this difference, maybe my mistake. I like the tooltips. But could we also make it more explicit by label? *Build environment variables:* and *Deployment environment variables:*? was (Author: mlabuda): It is understandable because of different wizard pages (Build vs Deployment config). Although I haven't noticed this difference, maybe my mistake. I like the tooltips. But could we also make it more explicit by label? *Build environment variables:* and "Deployment environment variables:"? > Application Wizard: Build configuration wizard page has redundant environment variables table > --------------------------------------------------------------------------------------------- > > Key: JBIDE-22454 > URL: https://issues.jboss.org/browse/JBIDE-22454 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.4.0.Alpha3 > Reporter: Marián Labuda > Assignee: Jeff Cantrill > Labels: application_wizard, openshift_v3 > Fix For: 4.4.x > > Attachments: screenshot-2.png, screenshot-3.png > > > In New OpenShift Application wizard with selected builder image, there are 2 wizard pages containing same thing - table of environment variables passed to pod. First page is Build Configuration, where the table is empty. Second page is the immediately following one Deployment configuration and Scalability, where are environment variables even correctly prepared (obtained from image metadata). The first table, on Build configuration wizard page, should be removed, its redundant there. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22454) Application Wizard: Build configuration wizard page has redundant environment variables table

by Marián Labuda (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22454?page=com.atlassian.jira.plugi... ] Marián Labuda commented on JBIDE-22454: --------------------------------------- It is understandable because of different wizard pages (Build vs Deployment config). Although I haven't noticed this difference, maybe my mistake. I like the tooltips. But could we also make it more explicit by label? *Build environment variables:* and "Deployment environment variables:"? > Application Wizard: Build configuration wizard page has redundant environment variables table > --------------------------------------------------------------------------------------------- > > Key: JBIDE-22454 > URL: https://issues.jboss.org/browse/JBIDE-22454 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.4.0.Alpha3 > Reporter: Marián Labuda > Assignee: Jeff Cantrill > Labels: application_wizard, openshift_v3 > Fix For: 4.4.x > > Attachments: screenshot-2.png, screenshot-3.png > > > In New OpenShift Application wizard with selected builder image, there are 2 wizard pages containing same thing - table of environment variables passed to pod. First page is Build Configuration, where the table is empty. Second page is the immediately following one Deployment configuration and Scalability, where are environment variables even correctly prepared (obtained from image metadata). The first table, on Build configuration wizard page, should be removed, its redundant there. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20674) Write automated tests to check consistency of Jetty between JBT & Eclipse

by Pavol Srna (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20674?page=com.atlassian.jira.plugi... ] Pavol Srna closed JBIDE-20674. ------------------------------ > Write automated tests to check consistency of Jetty between JBT & Eclipse > ------------------------------------------------------------------------- > > Key: JBIDE-20674 > URL: https://issues.jboss.org/browse/JBIDE-20674 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: browsersim, livereload, target-platform > Reporter: Mickael Istria > Assignee: Konstantin Marmalyukov > Fix For: 4.4.0.Alpha1 > > > Since it appears Jetty is somehow a "weak" component (ie APIs are often broken and versions are not well managed), we often have to enforce a specific version of Jetty for our JBoss Tools bundles. However, it happens that the version used by JBoss Tools component isn't the same as the one shipped by some other Eclipse components. > We need to make sure that enforcing a version of Jetty doesn't break those Eclipse components. The best way to achieve that is to write a test trying to validate the correct work of any Eclipse component we're aware it's using Jetty, as part of the same test plugin that validates the JBoss Tools components. > The list of identified Eclipse component using Jetty so far: > * Equinox (but I don't know how it uses Jetty, so neither how to make sure it's working well) > * Eclipse Help (test coulod load the help and make sure it shows content and not a 302 or 500 HTTP error) -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3916) Update devstudio URLs to reflect new file names

by Jan Richter (JIRA)

Jan Richter created JBDS-3916: --------------------------------- Summary: Update devstudio URLs to reflect new file names Key: JBDS-3916 URL: https://issues.jboss.org/browse/JBDS-3916 Project: Red Hat Developer Studio (DevStudio) Issue Type: Task Components: platform-installer Affects Versions: 10.0.0.Alpha2 Reporter: Jan Richter Assignee: Jan Richter Priority: Blocker Fix For: 10.0.0.Alpha3 Devstudio installer file was renamed from jboss-devstudio-... to devstudio-... so the requirement URLs are no longer valid. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22350) Fix BrowserSim/Livereload - Neon M7 bundles jetty 9.3.6

by Pavol Srna (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22350?page=com.atlassian.jira.plugi... ] Pavol Srna closed JBIDE-22350. ------------------------------ Verified in JBT 4.4.0.Alpha2. > Fix BrowserSim/Livereload - Neon M7 bundles jetty 9.3.6 > ------------------------------------------------------- > > Key: JBIDE-22350 > URL: https://issues.jboss.org/browse/JBIDE-22350 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: browsersim, livereload > Affects Versions: 4.4.0.Alpha2 > Reporter: Pavol Srna > Fix For: 4.4.0.Alpha2 > > > BrowserSim is already fixed, but livereload still not -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22437) Double click on a folder in browsed workspace for resource creation causes NPE

by Marián Labuda (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22437?page=com.atlassian.jira.plugi... ] Marián Labuda commented on JBIDE-22437: --------------------------------------- I did more digging, found real cause of the issue, updated steps to reproduce. > Double click on a folder in browsed workspace for resource creation causes NPE > ------------------------------------------------------------------------------ > > Key: JBIDE-22437 > URL: https://issues.jboss.org/browse/JBIDE-22437 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.4.0.Alpha2 > Reporter: Marián Labuda > Assignee: Dmitry Bocharov > Labels: openshift_v3 > Fix For: 4.4.0.Alpha3 > > > When I double click on a folder which is empty in Select OpenShift resource shell, which is opened by click on Browse Workspace button in New OpenShift resource wizard, NPE is thrown. If I click on arrow next to a folder, arrow disappear, because there are no files in the folder, but double click, which is supposed to expand a folder throws NPE with following stack trace: > {code} > Unhandled event loop exception > java.lang.NullPointerException > at org.jboss.tools.openshift.internal.common.ui.utils.UIUtils$7.select(UIUtils.java:488) > at org.eclipse.jface.viewers.ViewerFilter.filter(ViewerFilter.java:56) > at org.eclipse.jface.viewers.StructuredViewer.getFilteredChildren(StructuredViewer.java:911) > at org.eclipse.jface.viewers.AbstractTreeViewer.getSortedChildren(AbstractTreeViewer.java:621) > at org.eclipse.jface.viewers.AbstractTreeViewer.lambda$0(AbstractTreeViewer.java:817) > at org.eclipse.swt.custom.BusyIndicator.showWhile(BusyIndicator.java:70) > at org.eclipse.jface.viewers.AbstractTreeViewer.createChildren(AbstractTreeViewer.java:795) > at org.eclipse.jface.viewers.TreeViewer.createChildren(TreeViewer.java:596) > at org.eclipse.jface.viewers.AbstractTreeViewer.createChildren(AbstractTreeViewer.java:766) > at org.eclipse.jface.viewers.AbstractTreeViewer.handleTreeExpand(AbstractTreeViewer.java:1493) > at org.eclipse.jface.viewers.TreeViewer.handleTreeExpand(TreeViewer.java:882) > at org.eclipse.jface.viewers.AbstractTreeViewer$3.treeExpanded(AbstractTreeViewer.java:1505) > at org.eclipse.swt.widgets.TypedListener.handleEvent(TypedListener.java:133) > at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84) > at org.eclipse.swt.widgets.Display.sendEvent(Display.java:5208) > at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1340) > at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1366) > at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1349) > at org.eclipse.swt.widgets.Tree.gtk_test_expand_row(Tree.java:2206) > at org.eclipse.swt.widgets.Widget.windowProc(Widget.java:2029) > at org.eclipse.swt.widgets.Display.windowProc(Display.java:5485) > at org.eclipse.swt.internal.gtk.OS._gtk_main_do_event(Native Method) > at org.eclipse.swt.internal.gtk.OS.gtk_main_do_event(OS.java:9545) > at org.eclipse.swt.widgets.Display.eventProc(Display.java:1275) > at org.eclipse.swt.internal.gtk.OS._g_main_context_iteration(Native Method) > at org.eclipse.swt.internal.gtk.OS.g_main_context_iteration(OS.java:2495) > at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:4130) > at org.eclipse.jface.window.Window.runEventLoop(Window.java:818) > at org.eclipse.jface.window.Window.open(Window.java:794) > at org.eclipse.ui.dialogs.ElementTreeSelectionDialog.open(ElementTreeSelectionDialog.java:236) > at org.jboss.tools.openshift.internal.ui.wizard.resource.ResourcePayloadPage$3.widgetSelected(ResourcePayloadPage.java:182) > at org.eclipse.swt.widgets.TypedListener.handleEvent(TypedListener.java:249) > at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84) > at org.eclipse.swt.widgets.Display.sendEvent(Display.java:5208) > at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1340) > at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:4542) > at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:4132) > at org.eclipse.jface.window.Window.runEventLoop(Window.java:818) > at org.eclipse.jface.window.Window.open(Window.java:794) > at org.jboss.tools.common.ui.WizardUtils.openWizardDialog(WizardUtils.java:287) > at org.jboss.tools.common.ui.WizardUtils.openWizardDialog(WizardUtils.java:270) > at org.jboss.tools.openshift.internal.ui.handler.NewResourceHandler.execute(NewResourceHandler.java:33) > at org.eclipse.ui.internal.handlers.HandlerProxy.execute(HandlerProxy.java:295) > at org.eclipse.ui.internal.handlers.E4HandlerProxy.execute(E4HandlerProxy.java:90) > at sun.reflect.GeneratedMethodAccessor79.invoke(Unknown Source) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) > at java.lang.reflect.Method.invoke(Method.java:498) > at org.eclipse.e4.core.internal.di.MethodRequestor.execute(MethodRequestor.java:54) > at org.eclipse.e4.core.internal.di.InjectorImpl.invokeUsingClass(InjectorImpl.java:282) > at org.eclipse.e4.core.internal.di.InjectorImpl.invoke(InjectorImpl.java:264) > at org.eclipse.e4.core.contexts.ContextInjectionFactory.invoke(ContextInjectionFactory.java:132) > at org.eclipse.e4.core.commands.internal.HandlerServiceHandler.execute(HandlerServiceHandler.java:152) > at org.eclipse.core.commands.Command.executeWithChecks(Command.java:494) > at org.eclipse.core.commands.ParameterizedCommand.executeWithChecks(ParameterizedCommand.java:488) > at org.eclipse.e4.core.commands.internal.HandlerServiceImpl.executeHandler(HandlerServiceImpl.java:210) > at org.eclipse.e4.ui.workbench.renderers.swt.HandledContributionItem.executeItem(HandledContributionItem.java:427) > at org.eclipse.e4.ui.workbench.renderers.swt.AbstractContributionItem.handleWidgetSelection(AbstractContributionItem.java:454) > at org.eclipse.e4.ui.workbench.renderers.swt.AbstractContributionItem$3.handleEvent(AbstractContributionItem.java:482) > at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84) > at org.eclipse.swt.widgets.Display.sendEvent(Display.java:5208) > at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1340) > at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:4542) > at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:4132) > at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$4.run(PartRenderingEngine.java:1119) > at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:336) > at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.run(PartRenderingEngine.java:1020) > at org.eclipse.e4.ui.internal.workbench.E4Workbench.createAndRunUI(E4Workbench.java:150) > at org.eclipse.ui.internal.Workbench$5.run(Workbench.java:687) > at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:336) > at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:604) > at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:148) > 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:673) > at org.eclipse.equinox.launcher.Main.basicRun(Main.java:610) > at org.eclipse.equinox.launcher.Main.run(Main.java:1519) > at org.eclipse.equinox.launcher.Main.main(Main.java:1492) > {code} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22401) javascript New and Noteworthy for 4.4.0.Alpha2

by Pavol Srna (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22401?page=com.atlassian.jira.plugi... ] Pavol Srna closed JBIDE-22401. ------------------------------ Verified in 4.4.0.Alpha2 N&N > javascript New and Noteworthy for 4.4.0.Alpha2 > ---------------------------------------------- > > Key: JBIDE-22401 > URL: https://issues.jboss.org/browse/JBIDE-22401 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: javascript, nodejs > Reporter: Alexey Kazakov > Assignee: Victor Rubezhny > Priority: Critical > Fix For: 4.4.0.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 javascript is not listed here check if there are issues that should be added and add them. > Document the ones relevant for javascript by adding to [whatsnew|https://github.com/jbosstools/jbosstools-website/tree/master/doc...] and submit a pull request. > If no news for this component please reject and close this issue. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20442) Create SWTBot integration tests for tern related features

by Pavol Srna (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20442?page=com.atlassian.jira.plugi... ] Pavol Srna closed JBIDE-20442. ------------------------------ > Create SWTBot integration tests for tern related features > --------------------------------------------------------- > > Key: JBIDE-20442 > URL: https://issues.jboss.org/browse/JBIDE-20442 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: jsp/jsf/xml/html-source-editing > Affects Versions: 4.3.0.Beta2 > Reporter: Denis Golovin > Assignee: Pavol Srna > Priority: Critical > Fix For: 4.4.0.Alpha2 > > > There should be set of SWTBot tests that would cover functionality related to tern.java and angularjs-eclipse integration. These tests would simplify migration to new tern.java and angularjs-eclipse releases. > Current process for migration to new version of tern-java/angularjs-eclipse is manual. Steps below describe current approach: > 1. Manual mirroring of latest tern-java/angularjs-eclipse versions to local filesystem; > 2. Build jbosstools-jst with local mirrors and run JUnit tests; > 3. Install latest tern-java and angularjs-eclipse form mirrors done in (1) into JBDS nightly build from master branch (it has open version range for tern features) and restart; > 4. Run manual tests; > 5. If (2) and (3) idenify no problems then local mirrors should be published to http://download.jboss.org/jbosstools/updates/requirements/tern and http://download.jboss.org/jbosstools/updates/requirements/angularjs respectively; > 6. Update jbosstools-jst with new versions for tern-java/angularjs-eclipse and push local branch to upstream > With step 4 implemented as SWT bot tests and automated mirroring for tern-java and angularjs-eclipse (see jenkins job here https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/All/job/jbosstools-...) we can fully automate the process above. > QA also can skip step (1) and just use external p2 repos: > * http://oss.opensagres.fr/tern.repository/1.0.0-SNAPSHOT/ > * http://oss.opensagres.fr/angularjs-eclipse/1.0.0-SNAPSHOT/ > in step (2) by building jbosstools-jst as: > {code}mvn clean install -Dtern.repo.url=http://oss.opensagres.fr/tern.repository/1.0.0-SNAPSHOT/ -Dhttp://oss.opensagres.fr/angularjs-eclipse/1.0.0-SNAPSHOT/{code} > and installing latest versions for step (3). -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 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 May 2016