December 2013 - jbosstools-issues

[JBoss JIRA] (JBDS-2859) Include information on EAP version in installer

by Michelle Murray (JIRA)

[ https://issues.jboss.org/browse/JBDS-2859?page=com.atlassian.jira.plugin.... ] Michelle Murray commented on JBDS-2859: --------------------------------------- +1 > Include information on EAP version in installer > ----------------------------------------------- > > Key: JBDS-2859 > URL: https://issues.jboss.org/browse/JBDS-2859 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: installer > Affects Versions: 7.1.0.CR1 > Reporter: Martin Malina > Attachments: step-6.png > > > I find it hard for users to find out which version of EAP they are installing with JBDS. The installer has no mention of it. At least in the installer summary (Step 6 of 9) we could include this information. > !step-6.png! -- 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, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-15168) Disable outline view in FreeMarker IDE

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15168?page=com.atlassian.jira.plugi... ] Denis Golovin updated JBIDE-15168: ---------------------------------- Fix Version/s: 4.2.0.Alpha2 (was: 4.2.0.Alpha1) > Disable outline view in FreeMarker IDE > -------------------------------------- > > Key: JBIDE-15168 > URL: https://issues.jboss.org/browse/JBIDE-15168 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: freemarker > Affects Versions: 4.1.0.Final > Reporter: Daniel Dekany > Fix For: 4.2.0.Alpha2 > > > In the "FreeMarker IDE" Eclipse plugin, you should disable the outline view for now, as it's too broken to be useful, while it often slows template editing to crawl and is constantly flashing/redrawing as you type into the template, or even sometimes if you just move the cursor. > Regarding why it's broken: > * You show all the statements in it, which is way too much details and so it quickly becomes useless for overview and navigation. (Imagine if the Java outline did that, showing all if-s and for-s and assignments.) If should just list the macro and function declarations. > * It treats FreeMarker tags that don't end with {{/>}} as element openings, and then puts everything after that inside that element. But FreeMarker tags that start with {{#}} and can't have a body are implicitly closed. They are like {{img}} in HTML; {{<img ...>}} is the same as {{<img .../>}}. Similarly, {{<#assign x = 1>}} is the same as {{<#assign x = 1 />}}. > * It redraws the whole tree way to often. It slows things down, and the flashing it causes is annoying. -- 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, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-16271) Support jquery mobile 1.4

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-16271?page=com.atlassian.jira.plugi... ] Alexey Kazakov commented on JBIDE-16271: ---------------------------------------- Right now we have the following JQM features: 1. JQM content assist 2. JQM tab in Properties View 3. JQM Palette It's not a big problem to support #1 (content assist), and #2 (properties view) for both JQM versions 1.3 and 1.4. We just implement these features for 1.4 reusing 1.3 where possible and the corresponding version will be used depending on [version] in JQM JS link: jquery.mobile-[version].*.js declared in the page. If there is no version number (e.g. there is some local custom build JS lib) we could use the default (the latest) one. It's not so easy for #3 (Palette). We may have no jquery.mobile-[version].*.js link in the page at all. But we could add a new tag lib group to the palette: *JQuery Mobile 1.4* and rename the existing one *JQuery Mobile* to *JQuery Mobile 1.3*. If there is no JQM lib link in the page we can expand the group with the latest version. If there is a link with particular version then we could expand the corresponding JQM group in Palette View and fold the other (rest of them if we have more than 2 groups) of JQM groups. Another option we could use is a some kind of project (page) preference which user have to set to let JBT know what version of JQM he is going to use. Max, WDYT? > Support jquery mobile 1.4 > ------------------------- > > Key: JBIDE-16271 > URL: https://issues.jboss.org/browse/JBIDE-16271 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: jsp/jsf/xml/html source editing > Affects Versions: 4.1.1.Final > Reporter: Max Rydahl Andersen > Assignee: Alexey Kazakov > Fix For: 4.1.2.Final, 4.2.0.Alpha2 > > > jquery mobile 1.4 is coming out and apparently have performance fixes making it better suited for cordova development. > Noets from Vineet: > "I wouldn't say 1.4 is more compatible. It's a case of jQM 1.4 being more suitable > for Cordova apps. jQM 1.4 is more performant and thus Cordova apps are less sluggish. > The release notes allude to this: http://jquerymobile.com/blog/2013/09/24/announcing-jquery-mobile-1-4-beta/ > I've got no hard numbers here, but this slides in this talk - http://www.slideshare.net/AlexanderSchmitz/austin-26252266 > gives a better overview of what's in 1.4. Slide 22 is most relevant - > jQM 1.4 ships with a better default theme that improves performance, > among various other changes discussed in other slides." > Need to find out what issues jquery mobile palette and others might have with supporting jquery mobile for both 1.3 and 1.4...will be relevant with future new versions too. -- 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, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-15258) Move performance tests in separate github repository from jbosstools-base/tests

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15258?page=com.atlassian.jira.plugi... ] Denis Golovin closed JBIDE-15258. --------------------------------- tests removed in master, but still available from other branches. > Move performance tests in separate github repository from jbosstools-base/tests > ------------------------------------------------------------------------------- > > Key: JBIDE-15258 > URL: https://issues.jboss.org/browse/JBIDE-15258 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: common/jst/core, qa > Affects Versions: 4.1.0.CR1 > Reporter: Denis Golovin > Assignee: Denis Golovin > Fix For: 4.2.0.Alpha2 > > -- 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, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-15258) Move performance tests in separate github repository from jbosstools-base/tests

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15258?page=com.atlassian.jira.plugi... ] Denis Golovin resolved JBIDE-15258. ----------------------------------- Resolution: Done > Move performance tests in separate github repository from jbosstools-base/tests > ------------------------------------------------------------------------------- > > Key: JBIDE-15258 > URL: https://issues.jboss.org/browse/JBIDE-15258 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: common/jst/core, qa > Affects Versions: 4.1.0.CR1 > Reporter: Denis Golovin > Assignee: Denis Golovin > Fix For: 4.2.0.Alpha2 > > -- 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, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-15258) Move performance tests in separate github repository from jbosstools-base/tests

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15258?page=com.atlassian.jira.plugi... ] Denis Golovin reassigned JBIDE-15258: ------------------------------------- Assignee: Denis Golovin > Move performance tests in separate github repository from jbosstools-base/tests > ------------------------------------------------------------------------------- > > Key: JBIDE-15258 > URL: https://issues.jboss.org/browse/JBIDE-15258 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: common/jst/core, qa > Affects Versions: 4.1.0.CR1 > Reporter: Denis Golovin > Assignee: Denis Golovin > Fix For: 4.2.0.Alpha2 > > -- 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, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-16271) Support jquery mobile 1.4

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-16271?page=com.atlassian.jira.plugi... ] Alexey Kazakov reassigned JBIDE-16271: -------------------------------------- Assignee: Alexey Kazakov > Support jquery mobile 1.4 > ------------------------- > > Key: JBIDE-16271 > URL: https://issues.jboss.org/browse/JBIDE-16271 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: jsp/jsf/xml/html source editing > Affects Versions: 4.1.1.Final > Reporter: Max Rydahl Andersen > Assignee: Alexey Kazakov > Fix For: 4.1.2.Final, 4.2.0.Alpha2 > > > jquery mobile 1.4 is coming out and apparently have performance fixes making it better suited for cordova development. > Noets from Vineet: > "I wouldn't say 1.4 is more compatible. It's a case of jQM 1.4 being more suitable > for Cordova apps. jQM 1.4 is more performant and thus Cordova apps are less sluggish. > The release notes allude to this: http://jquerymobile.com/blog/2013/09/24/announcing-jquery-mobile-1-4-beta/ > I've got no hard numbers here, but this slides in this talk - http://www.slideshare.net/AlexanderSchmitz/austin-26252266 > gives a better overview of what's in 1.4. Slide 22 is most relevant - > jQM 1.4 ships with a better default theme that improves performance, > among various other changes discussed in other slides." > Need to find out what issues jquery mobile palette and others might have with supporting jquery mobile for both 1.3 and 1.4...will be relevant with future new versions too. -- 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, 4 months

1
0
0 / 0

[JBoss JIRA] (JBDS-2260) Installation of JBoss Developer Studio hangs if accented characters in TMP folder (Windows only)

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBDS-2260?page=com.atlassian.jira.plugin.... ] Denis Golovin updated JBDS-2260: -------------------------------- Fix Version/s: 8.0.0.Alpha2 (was: 8.0.0.Alpha1) > Installation of JBoss Developer Studio hangs if accented characters in TMP folder (Windows only) > ------------------------------------------------------------------------------------------------ > > Key: JBDS-2260 > URL: https://issues.jboss.org/browse/JBDS-2260 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: installer > Affects Versions: 5.0.0.GA > Reporter: Isaac Rooskov > Assignee: Denis Golovin > Labels: respin-b > Fix For: 8.0.0.Alpha2 > > Attachments: JavaVersionReader.java.patch > > > *From customer in Bugzilla* > Bugzilla link: https://bugzilla.redhat.com/show_bug.cgi?id=850793 > Description of issue from customer: > Description of problem: > Installation of JBoss Developer Studion 5.0.0 stops at Installation Step 7 of 9 Overall Installation Progress 1/4 > Version-Release number of selected component (if applicable): > JBOSS Developer Studio 5.0.0.GA > How reproducible: > Start installation using > java - jar jbdevstudio-product-universal-5.0.0.v20120615-1714-H213-GA.jar > Actual results: > Installation is not passing at step 7 of 9, progress 1 of 4. > Expected results: > Additional info: -- 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, 4 months

1
0
0 / 0

[JBoss JIRA] (TOOLSDOC-428) Update JBDS 7.1 docs for fixed bugs that changed UI look or behavior

by Michelle Murray (JIRA)

[ https://issues.jboss.org/browse/TOOLSDOC-428?page=com.atlassian.jira.plug... ] Michelle Murray commented on TOOLSDOC-428: ------------------------------------------ User guide checked and updated as part of TOOLSDOC-384 (Tech review of user guide) > Update JBDS 7.1 docs for fixed bugs that changed UI look or behavior > -------------------------------------------------------------------- > > Key: TOOLSDOC-428 > URL: https://issues.jboss.org/browse/TOOLSDOC-428 > Project: Documentation for JBoss Tools and Developer Studio > Issue Type: Task > Security Level: Public(Everyone can see) > Components: General documentation issues > Affects Versions: 4.1.1 > Reporter: Michelle Murray > Assignee: Michelle Murray > Fix For: 4.1.1 > > > This JIRA holds information about fixed JIRAs that have changed the UI look or behavior and require docs to be modified. > * Correct icons (OpenShift, JBIDE-15797) > * Correct bad and missing icons in explorer context menu (OpenShift, JBIDE-15801) > * Users should be warned when WFK maven repo is missing (JBIDE-14909) > * Add blank icon to align JBoss Welcome screen columns (JBIDE-15718) > * Rename EAP 6.1 server type to 6.1+, ensure runtime detection is accurate (JBIDE-15614) > * Replace domain icon with a globe (currently a library) (OpenShift, JBIDE-15681) -- 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, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-16276) Native Project Export Error

by Burr Sutter (JIRA)

[ https://issues.jboss.org/browse/JBIDE-16276?page=com.atlassian.jira.plugi... ] Burr Sutter updated JBIDE-16276: -------------------------------- Description: Dialog comes up with a blank message http://screencast.com/t/7zbjLnpN Details says No Android Targets were found, please create target http://screencast.com/t/lpxWh4IRp4r the problem with this message is...what is the end-user supposed to do? I suspect this error occurs because I have not yet set the location of my Android SDKs was: Dialog comes up with a blank message http://screencast.com/t/7zbjLnpN Details says No Android Targets were found, please create target http://screencast.com/t/lpxWh4IRp4r the problem with this message is...what is the end-user supposed to do? > Native Project Export Error > --------------------------- > > Key: JBIDE-16276 > URL: https://issues.jboss.org/browse/JBIDE-16276 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: aerogear-hybrid > Reporter: Burr Sutter > > Dialog comes up with a blank message > http://screencast.com/t/7zbjLnpN > Details says > No Android Targets were found, please create target > http://screencast.com/t/lpxWh4IRp4r > the problem with this message is...what is the end-user supposed to do? > I suspect this error occurs because I have not yet set the location of my Android SDKs -- 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, 4 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 December 2013