September 2015 - jbosstools-issues

[JBoss JIRA] (JBIDE-20760) docker feature not included in Marketplace entry for JBoss Tools

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20760?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-20760: ------------------------------- Fix Version/s: 4.3.0.Final > docker feature not included in Marketplace entry for JBoss Tools > ---------------------------------------------------------------- > > Key: JBIDE-20760 > URL: https://issues.jboss.org/browse/JBIDE-20760 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: marketplace > Affects Versions: 4.3.0.CR1 > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 4.3.0.Final > > > Because we removed the docker feature and replaced it with the docker plugins in order to avoid the odious problem of a disabled update site appearing in Eclipse's list of Available Update Sites, we no longer have a way to provide the docker tooling via our Marketplace entry. > Solution: > Stop caring if there's an extra *disabled* update site in Eclipse when we install JBT (there's a disabled Mylyn one there too, plus 4 enabled ones for Mars, Mylyn, Eclipse, and WTP, so what's one more?), and just use the feature in JBT's CoreTools category & on the Marketplace entry. > Then, for JBDS, we continue to just use the plugins and include them in the com.jboss.devstudio.core.feature so they're installed OOTB via the BYOE / Core feature (and also via Marketplace). > Sound good? -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20760) docker feature not included in Marketplace entry for JBoss Tools

by Nick Boldt (JIRA)

Nick Boldt created JBIDE-20760: ---------------------------------- Summary: docker feature not included in Marketplace entry for JBoss Tools Key: JBIDE-20760 URL: https://issues.jboss.org/browse/JBIDE-20760 Project: Tools (JBoss Tools) Issue Type: Bug Components: marketplace Affects Versions: 4.3.0.CR1 Reporter: Nick Boldt Because we removed the docker feature and replaced it with the docker plugins in order to avoid the odious problem of a disabled update site appearing in Eclipse's list of Available Update Sites, we no longer have a way to provide the docker tooling via our Marketplace entry. Solution: Stop caring if there's an extra *disabled* update site in Eclipse when we install JBT (there's a disabled Mylyn one there too, plus 4 enabled ones for Mars, Mylyn, Eclipse, and WTP, so what's one more?), and just use the feature in JBT's CoreTools category & on the Marketplace entry. Then, for JBDS, we continue to just use the plugins and include them in the com.jboss.devstudio.core.feature so they're installed OOTB via the BYOE / Core feature (and also via Marketplace). Sound good? -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20760) docker feature not included in Marketplace entry for JBoss Tools

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20760?page=com.atlassian.jira.plugi... ] Nick Boldt reassigned JBIDE-20760: ---------------------------------- Assignee: Nick Boldt > docker feature not included in Marketplace entry for JBoss Tools > ---------------------------------------------------------------- > > Key: JBIDE-20760 > URL: https://issues.jboss.org/browse/JBIDE-20760 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: marketplace > Affects Versions: 4.3.0.CR1 > Reporter: Nick Boldt > Assignee: Nick Boldt > > Because we removed the docker feature and replaced it with the docker plugins in order to avoid the odious problem of a disabled update site appearing in Eclipse's list of Available Update Sites, we no longer have a way to provide the docker tooling via our Marketplace entry. > Solution: > Stop caring if there's an extra *disabled* update site in Eclipse when we install JBT (there's a disabled Mylyn one there too, plus 4 enabled ones for Mars, Mylyn, Eclipse, and WTP, so what's one more?), and just use the feature in JBT's CoreTools category & on the Marketplace entry. > Then, for JBDS, we continue to just use the plugins and include them in the com.jboss.devstudio.core.feature so they're installed OOTB via the BYOE / Core feature (and also via Marketplace). > Sound good? -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20759) Add project name validation

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20759?page=com.atlassian.jira.plugi... ] Fred Bricon edited comment on JBIDE-20759 at 9/22/15 1:12 PM: -------------------------------------------------------------- Fix applied in master PR to apply on 4.3.x: https://github.com/jbosstools/jbosstools-openshift/pull/781 was (Author: fbricon): PR to apply on 4.3.x: https://github.com/jbosstools/jbosstools-openshift/pull/781 > Add project name validation > --------------------------- > > Key: JBIDE-20759 > URL: https://issues.jboss.org/browse/JBIDE-20759 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: openshift > Affects Versions: 4.3.0.CR1 > Reporter: Marián Labuda > Assignee: Fred Bricon > Priority: Critical > Fix For: 4.3.1.Final > > > We have validation of a project name just for its length which is supposed to be between 2 and 63 characters. But we have no validation on the form of a project name which has to be matching regex [a-z0-9]([-a-z0-9]*[a-z0-9]. Currently it is possible to type name e.g. "myProject" and there is no validation although it is not a valid name and creation fails. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20759) Add project name validation

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20759?page=com.atlassian.jira.plugi... ] Fred Bricon reassigned JBIDE-20759: ----------------------------------- Assignee: Fred Bricon > Add project name validation > --------------------------- > > Key: JBIDE-20759 > URL: https://issues.jboss.org/browse/JBIDE-20759 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: openshift > Affects Versions: 4.3.0.CR1 > Reporter: Marián Labuda > Assignee: Fred Bricon > Priority: Critical > Fix For: 4.3.1.Final > > > We have validation of a project name just for its length which is supposed to be between 2 and 63 characters. But we have no validation on the form of a project name which has to be matching regex [a-z0-9]([-a-z0-9]*[a-z0-9]. Currently it is possible to type name e.g. "myProject" and there is no validation although it is not a valid name and creation fails. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20747) install-grinder returns a blue ball but fails to install 5 plugins due to missing capability &/or package

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20747?page=com.atlassian.jira.plugi... ] Denis Golovin commented on JBIDE-20747: --------------------------------------- [~ldimaggio] even manual test is not 100% reliable: * Step (3): it should involve all JBT packages not only categorized ones; * Step (4): How can you say what source exactly (p2repository/discovery) was used and confirm it is what is going to be published? > install-grinder returns a blue ball but fails to install 5 plugins due to missing capability &/or package > --------------------------------------------------------------------------------------------------------- > > Key: JBIDE-20747 > URL: https://issues.jboss.org/browse/JBIDE-20747 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build > Affects Versions: 4.3.0.CR1 > Reporter: Nick Boldt > Assignee: Nick Boldt > Priority: Critical > Fix For: 4.3.1.Final > > > This happened in http://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevSt... > {code} > org.osgi.framework.BundleException: Could not resolve module: org.jboss.tools.browsersim.eclipse [1120] > Unresolved requirement: Require-Bundle: org.jboss.tools.browsersim.ui; bundle-version="3.7.0" > -> Bundle-SymbolicName: org.jboss.tools.browsersim.ui; bundle-version="3.7.0.CR1-v20150901-2111-B229"; singleton:="true" > org.jboss.tools.browsersim.ui [1122] > Unresolved requirement: Require-Bundle: org.eclipse.jetty.websocket.server; bundle-version="[9.0.0,10.0.0)" > -> Bundle-SymbolicName: org.eclipse.jetty.websocket.server; bundle-version="9.2.13.v20150730" > org.eclipse.jetty.websocket.server [555] > Unresolved requirement: Require-Capability: osgi.extender; filter:="(osgi.extender=osgi.serviceloader.registrar)" > Unresolved requirement: Import-Package: org.eclipse.jetty.websocket.servlet; version="[9.0.0,10.0.0)" > -> Export-Package: org.eclipse.jetty.websocket.servlet; bundle-symbolic-name="org.eclipse.jetty.websocket.servlet"; bundle-version="9.2.13.v20150730"; version="9.2.13" > org.eclipse.jetty.websocket.servlet [556] > Unresolved requirement: Require-Capability: osgi.serviceloader; filter:="(osgi.serviceloader=org.eclipse.jetty.websocket.servlet.WebSocketServletFactory)"; cardinality:="multiple" > -> Provide-Capability: osgi.serviceloader; osgi.serviceloader="org.eclipse.jetty.websocket.servlet.WebSocketServletFactory" > {code} > -- http://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevSt... > Similar problems for other IUs: > {code} > org.osgi.framework.BundleException: Could not resolve module: org.jboss.tools.cordovasim.eclipse [1163] > org.osgi.framework.BundleException: Could not resolve module: org.jboss.tools.feedhenry.ui [1166] > org.osgi.framework.BundleException: Could not resolve module: org.jboss.tools.livereload.core [1221] > org.osgi.framework.BundleException: Could not resolve module: org.jboss.tools.livereload.ui [1222] > {code} > But the job was successful! > http://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevSt... -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 7 months

1
0
0 / 0

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

by Konstantin Marmalyukov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20756?page=com.atlassian.jira.plugi... ] Konstantin Marmalyukov commented on JBIDE-20756: ------------------------------------------------ We have actually two issues here: 1. If browser engine is SWT.WebKit touch events will not work and produce error which is mentioned it description Reproducile: both on small and heavyweight pages, *only on Linux* It happens because SWT.WebKit gives error on line "delete finger.target[onEventName];" - it is actually null. With old versions of webkitgtk everything was fine. Nullcheck is simple workaround. 2. If browser engine is JavaFx, touch events will not work on small examples. Reproducible: on every platform, example of html file is in description It happens because we load touch events script on DomContentLoaded event. Also easy to fix > 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.3.x > > > 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)

10 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20757) Livereload does not work with CordovaSim on default THYM project

by Ilya Buziuk (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20757?page=com.atlassian.jira.plugi... ] Ilya Buziuk commented on JBIDE-20757: ------------------------------------- PR for FAQ - https://github.com/jbosstools/jbosstools-website/pull/487 > Livereload does not work with CordovaSim on default THYM project > ---------------------------------------------------------------- > > Key: JBIDE-20757 > URL: https://issues.jboss.org/browse/JBIDE-20757 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: aerogear-hybrid, cordovasim, livereload, upstream > Affects Versions: 4.3.0.CR1 > Reporter: Ilya Buziuk > Assignee: Ilya Buziuk > Fix For: 4.3.1.Final > > > Steps to reproduce: > 1) create default THYM project > 2) enable Livereload server > 3) run THYM project on CordovaSim > 4) edit index.html and save changes > ERROR: refresh is not happening on Cordovasim > In order to make it work one nee to remove the following meta tag from index.html: > {code} > <meta http-equiv="Content-Security-Policy" content="default-src 'self' data: gap: https://ssl.gstatic.com 'unsafe-eval'; style-src 'self' 'unsafe-inline'; media-src *"> > {code} > Livereload doesn't work with new THYM projects due to new cordova-white-list plugin security policy - https://github.com/apache/cordova-plugin-whitelist/blob/master/README.md#... . The following error prevent script loading > {code} > Refused to load the script 'http://localhost:35729/livereload.js' because it violates the following Content Security Policy directive: "default-src 'self' data: gap: https://ssl.gstatic.com 'unsafe-eval'". Note that 'script-src' was not explicitly set, so 'default-src' is used as a fallback. > {code} > BTW, We are not the only one affected by this changes - http://forum.ionicframework.com/t/solution-for-livereload-problems-with-n... -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20759) Add project name validation

by Marián Labuda (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20759?page=com.atlassian.jira.plugi... ] Marián Labuda commented on JBIDE-20759: --------------------------------------- >From response after sending an invalid project name. E.g. try to create a project with name "myProject" and there is error dialog showing how project name is supposed to look like. > Add project name validation > --------------------------- > > Key: JBIDE-20759 > URL: https://issues.jboss.org/browse/JBIDE-20759 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: openshift > Affects Versions: 4.3.0.CR1 > Reporter: Marián Labuda > Priority: Critical > Fix For: 4.3.1.Final > > > We have validation of a project name just for its length which is supposed to be between 2 and 63 characters. But we have no validation on the form of a project name which has to be matching regex [a-z0-9]([-a-z0-9]*[a-z0-9]. Currently it is possible to type name e.g. "myProject" and there is no validation although it is not a valid name and creation fails. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBTIS-501) stable URLs used for Integration Stack installs/updates via Central should not contain a version number

by Paul Leacu (JIRA)

[ https://issues.jboss.org/browse/JBTIS-501?page=com.atlassian.jira.plugin.... ] Paul Leacu reassigned JBTIS-501: -------------------------------- Assignee: Paul Leacu > stable URLs used for Integration Stack installs/updates via Central should not contain a version number > ------------------------------------------------------------------------------------------------------- > > Key: JBTIS-501 > URL: https://issues.jboss.org/browse/JBTIS-501 > Project: JBoss Tools Integration Stack > Issue Type: Bug > Components: distribution > Affects Versions: 4.2.3.Final , 4.3.0.Alpha1 > Reporter: Nick Boldt > Assignee: Paul Leacu > > Stable URLs used for Integration Stack installs/updates via Central should not contain a version number, so that users only see ONE URL, which is updated to contain new, fresh content. > This allows new users to see the latest updates, existing users to see newer updates (Help > Check for updates), and existing users to seek new updates in Central, too. > So... > {code:title=https://github.com/jbosstools/jbosstools-download.jboss.org/blob/master/jbosstools/configuration/ide-config.properties#L82} > jboss.discovery.site.integration-stack.url|jbosstools|4.2=http://download... > Needs to change to > {code} > jboss.discovery.site.integration-stack.url|jbosstools|4.2=http://download... > {code} > And http://download.jboss.org/jbosstools/discovery/stable/integration-stack/ needs to be a composite of http://download.jboss.org/jbosstools/discovery/stable/integration-stack/4... -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 7 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 2015