September 2015 - jbosstools-issues

[JBoss JIRA] (JBTIS-505) Update category.xml for JBT core CR1a updates

by Paul Leacu (JIRA)

[ https://issues.jboss.org/browse/JBTIS-505?page=com.atlassian.jira.plugin.... ] Paul Leacu reassigned JBTIS-505: -------------------------------- Assignee: Paul Leacu > Update category.xml for JBT core CR1a updates > --------------------------------------------- > > Key: JBTIS-505 > URL: https://issues.jboss.org/browse/JBTIS-505 > Project: JBoss Tools Integration Stack > Issue Type: Task > Reporter: Paul Leacu > Assignee: Paul Leacu > -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBTIS-505) Update category.xml for JBT core CR1a updates

by Paul Leacu (JIRA)

Paul Leacu created JBTIS-505: -------------------------------- Summary: Update category.xml for JBT core CR1a updates Key: JBTIS-505 URL: https://issues.jboss.org/browse/JBTIS-505 Project: JBoss Tools Integration Stack Issue Type: Task Reporter: Paul Leacu -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20655) server New and Noteworthy for 4.3.0.CR1

by Martin Malina (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20655?page=com.atlassian.jira.plugi... ] Martin Malina closed JBIDE-20655. --------------------------------- Verified at http://tools.jboss.org/documentation/whatsnew/jbosstools/4.3.0.CR1.html > server New and Noteworthy for 4.3.0.CR1 > --------------------------------------- > > Key: JBIDE-20655 > URL: https://issues.jboss.org/browse/JBIDE-20655 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: archives, jmx, server > Reporter: Max Rydahl Andersen > Assignee: Rob Stryker > Priority: Critical > Fix For: 4.3.0.CR1 > > > 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 server is not listed here check if there are issues that should be added and add them. > Document the ones relevant for server by adding to [whatsnew|https://github.com/jbosstools/jbosstools-website/tree/master/doc...] and submit a pullrequest. > If no news for this component please reject and close this issue. -- 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 commented on JBIDE-20759: ------------------------------------- Where did you get that regex from? > 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

2
1
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 updated JBIDE-20759: -------------------------------- Fix Version/s: 4.3.1.Final (was: 4.3.x) > 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] (JBIDE-19853) GTK3 (only): Erroneous labels in application wizard tree

by Snjezana Peco (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19853?page=com.atlassian.jira.plugi... ] Snjezana Peco edited comment on JBIDE-19853 at 9/22/15 10:13 AM: ----------------------------------------------------------------- I have created a workaround that is limited to GTK3 because it disables styled cell label provider (ApplicationTemplateViewLabelProvider). We would need to remove it after applying the fix for https://bugs.eclipse.org/bugs/show_bug.cgi?id=466499. was (Author: snjeza): I have created a workaround that is limited to GTK3 because it disables styled cell label provider (ApplicationTemplateViewLabelProvider). We would need to remove it after apply the fix for https://bugs.eclipse.org/bugs/show_bug.cgi?id=466499. > GTK3 (only): Erroneous labels in application wizard tree > -------------------------------------------------------- > > Key: JBIDE-19853 > URL: https://issues.jboss.org/browse/JBIDE-19853 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift, upstream > Affects Versions: 4.3.0.Beta1 > Reporter: Andre Dietisheim > Assignee: Andre Dietisheim > Priority: Blocker > Labels: application_wizard > Fix For: 4.3.0.Beta1 > > Attachments: gtk2-new-app-wizard-1.png, gtk2-new-app-wizard-2.png, gtk3-new-app-wizard-1.png, gtk3-new-app-wizard-2.png, gtk3-quickstarts-cartridges.png > > > When run in GTK3 the tree in the v2 application wizard is showing completely erroneous labels. The labels even switch content when the tree items are unfolded. > When running Eclipse using (export SWT_GTK3=0) the tree in the application wizard looks in the following correct way: > !gtk2-new-app-wizard-1.png! > unfolding the "Basic Cartridges" produces the following: > !gtk2-new-app-wizard-2.png! > Without the above env variable, which makes Eclipse use GTK3, the application wizard looks as follows: > !gtk3-new-app-wizard-1.png! > ... and when unfolding "Basic Cartridges" the labels for the 3 main cathegories and all the children change to display the same: > !gtk3-new-app-wizard-2.png! -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20678) Eclipse UI is frozen after starting/stopping Forge

by Pavol Srna (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20678?page=com.atlassian.jira.plugi... ] Pavol Srna updated JBIDE-20678: ------------------------------- Labels: regression respin-a (was: respin-a) > Eclipse UI is frozen after starting/stopping Forge > -------------------------------------------------- > > Key: JBIDE-20678 > URL: https://issues.jboss.org/browse/JBIDE-20678 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: forge > Affects Versions: 4.3.0.CR1 > Environment: Linux GTK3 x86_64 > Max OS X x86_64 > Reporter: Denis Golovin > Assignee: George Gastaldi > Priority: Blocker > Labels: regression, respin-a > Fix For: 4.3.0.CR1 > > Attachments: stacktrace.txt, stacktrace3.txt, stactrace-mac.txt > > > See steps to replicate for exact steps and attached [^stacktrace.txt] for stacktrace -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20678) Eclipse UI is frozen after starting/stopping Forge

by Pavol Srna (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20678?page=com.atlassian.jira.plugi... ] Pavol Srna closed JBIDE-20678. ------------------------------ Verified in JBDS 9.0.0.CR1a build. > Eclipse UI is frozen after starting/stopping Forge > -------------------------------------------------- > > Key: JBIDE-20678 > URL: https://issues.jboss.org/browse/JBIDE-20678 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: forge > Affects Versions: 4.3.0.CR1 > Environment: Linux GTK3 x86_64 > Max OS X x86_64 > Reporter: Denis Golovin > Assignee: George Gastaldi > Priority: Blocker > Labels: regression, respin-a > Fix For: 4.3.0.CR1 > > Attachments: stacktrace.txt, stacktrace3.txt, stactrace-mac.txt > > > See steps to replicate for exact steps and attached [^stacktrace.txt] for stacktrace -- 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: ------------------------------------------------ In case of your example yes, but if you thy some heavyweight example(i.e. goodfil.ms) it will work perfect. Looks like there is the same problem for small files like we have for livereload > 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] (JBDS-3160) JSR-352: Java EE 7 Batch

by Lucia Jelinkova (JIRA)

[ https://issues.jboss.org/browse/JBDS-3160?page=com.atlassian.jira.plugin.... ] Lucia Jelinkova closed JBDS-3160. --------------------------------- I tried https://github.com/jboss-developer/jboss-eap-quickstarts/tree/7.0.x-devel... quickstart and it worked fine except for a small issue with application URL that will be solved in separate issue. I am closing the issue. > JSR-352: Java EE 7 Batch > ------------------------ > > Key: JBDS-3160 > URL: https://issues.jboss.org/browse/JBDS-3160 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Feature Request > Components: requirements > Reporter: Burr Sutter > Assignee: Alexey Kazakov > Priority: Critical > Fix For: 9.0.0.CR1 > > Attachments: BatchEditor.png > > > Custom XML Editor for the Batch configuration XML > Example > https://github.com/javaee-samples/javaee7-samples/blob/master/batch/chunk... > JSR-352: Batch > I, the Java EE application developer, wish to create new and maintain Batch (JSR-352) applications in Eclipse. I need XML editing support, content-assist where appropriate and a Maven-based quickstart to help with getting started. > The quickstart should be easily importable into JBDS and allow for editing so that I, the Java EE app dev, can "make it my own" by changing its project name, group, artifact id and version, plus modifying the XML file, adding/removing classes, etc. > This effort should primarily be focused on the XML editing experience. The normal New Java Class wizard should support the batch related super classes (extends). Run As Run on Server should work as well. > Examples of the XML: > https://github.com/javaee-samples/javaee7-samples/blob/master/batch/batch... > https://github.com/javaee-samples/javaee7-samples/blob/master/batch/batch... -- 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