September 2013 - jbosstools-issues

[JBoss JIRA] (JBIDE-15430) Chrome regression because of invalid content-lenght returned with special characters

by Xavier Coulon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15430?page=com.atlassian.jira.plugi... ] Xavier Coulon commented on JBIDE-15430: --------------------------------------- [~vpakan], You can try with the following steps: - have an HTML file that contains some Chinese characters (eg: https://raw.github.com/xcoulon/jbosstools-livereload/master/tests/org.jbo...) in your project - this file should be encoded in UTF-8 in the Eclipse workspace. Open this file via LiveReload using Chrome. Without the fix, Chrome displays an empty page (and errors appears in the Chrome DevTools). With the fix, it displays the Chinese characters, as expected. Please, let me know if those steps to reproduce work for you. > Chrome regression because of invalid content-lenght returned with special characters > ------------------------------------------------------------------------------------- > > Key: JBIDE-15430 > URL: https://issues.jboss.org/browse/JBIDE-15430 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: livereload > Affects Versions: 4.1.0.Final > Reporter: Xavier Coulon > Assignee: Max Rydahl Andersen > Fix For: 4.1.1.Alpha1 > > > When the HTML entity in the HTTP response contains special characters and the livereload script is injected in that entity, the computed content-lenght header is invalid, which causes Chrome to not render the returned HTML page *at all*. -- 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, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-15019) Will you allow Red Hat Inc. Dialog issue

by Radim Hopp (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15019?page=com.atlassian.jira.plugi... ] Radim Hopp closed JBIDE-15019. ------------------------------ Closing as it is a duplicate issue. > Will you allow Red Hat Inc. Dialog issue > ----------------------------------------- > > Key: JBIDE-15019 > URL: https://issues.jboss.org/browse/JBIDE-15019 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: usage > Reporter: Burr Sutter > Fix For: 4.1.1.Alpha1 > > > The Info link wraps - see screenshot -- 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, 7 months

1
0
0 / 0

[JBoss JIRA] (JBDS-2081) Anonymous Usage Dialog

by Radim Hopp (JIRA)

[ https://issues.jboss.org/browse/JBDS-2081?page=com.atlassian.jira.plugin.... ] Radim Hopp closed JBDS-2081. ---------------------------- Closing as it is a duplicate issue. > Anonymous Usage Dialog > ---------------------- > > Key: JBDS-2081 > URL: https://issues.jboss.org/browse/JBDS-2081 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: usage > Environment: Win 7 32-bit JVM - 1920x1080 (1080P HD) > Reporter: Burr Sutter > Assignee: Andre Dietisheim > Attachments: usage_info.png > > > The text in the dialog does not wrap correctly. ")?" shows up on its own line. -- 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, 7 months

1
0
0 / 0

[JBoss JIRA] (JBDS-2762) jbdevstudio links to nonexistant folder

by CDW Engine (JIRA)

[ https://issues.jboss.org/browse/JBDS-2762?page=com.atlassian.jira.plugin.... ] CDW Engine updated JBDS-2762: ----------------------------- CDW pm_ack: ? CDW release: ? Target Release: 3.0.2.GA > jbdevstudio links to nonexistant folder > --------------------------------------- > > Key: JBDS-2762 > URL: https://issues.jboss.org/browse/JBDS-2762 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: installer > Affects Versions: 7.1.0.Alpha1 > Environment: OSX > Reporter: Max Rydahl Andersen > Priority: Critical > > After install on OSX there is a symoblic link in the studio folder: > jbdevstudio@ -> jbdevstudio.app/Contents/MacOS/jbdevstudio > This shortcut is very useful when wanting to actually run eclipse/jbdevstudio with command line arguments, but the symbolic link is broken. > The actual path for the executable is: > ./JBoss Developer Studio.app/Contents/MacOS/jbdevstudio -- 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, 7 months

1
0
0 / 0

[JBoss JIRA] (JBDS-2762) jbdevstudio links to nonexistant folder

by Max Rydahl Andersen (JIRA)

Max Rydahl Andersen created JBDS-2762: ----------------------------------------- Summary: jbdevstudio links to nonexistant folder Key: JBDS-2762 URL: https://issues.jboss.org/browse/JBDS-2762 Project: Developer Studio (JBoss Developer Studio) Issue Type: Bug Security Level: Public (Everyone can see) Components: installer Affects Versions: 7.1.0.Alpha1 Environment: OSX Reporter: Max Rydahl Andersen Priority: Critical After install on OSX there is a symoblic link in the studio folder: jbdevstudio@ -> jbdevstudio.app/Contents/MacOS/jbdevstudio This shortcut is very useful when wanting to actually run eclipse/jbdevstudio with command line arguments, but the symbolic link is broken. The actual path for the executable is: ./JBoss Developer Studio.app/Contents/MacOS/jbdevstudio -- 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, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-15482) Replace staging & staging.previous (two builds w/ reused URLs) with uniquely timestamped build URLs and auto-regenerated composite*.xml files

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15482?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen updated JBIDE-15482: ---------------------------------------- Fix Version/s: 4.1.1.Alpha2 > Replace staging & staging.previous (two builds w/ reused URLs) with uniquely timestamped build URLs and auto-regenerated composite*.xml files > --------------------------------------------------------------------------------------------------------------------------------------------- > > Key: JBIDE-15482 > URL: https://issues.jboss.org/browse/JBIDE-15482 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: build, updatesite > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 4.1.1.Alpha2 > > > Be it proposed: > {quote} > that instead of an in-place move which reuses > generic folder names like "staging" and "staging.previous", we > composite build output using unique names like > 2013-08-09_05-05-26-B7222/ or 2013-08-13_10-05-28-B7255 > {quote} > We therefore need: > a) to regenerate the composite site each time there's a new build > published, in order to remove the oldest and add the newest (keeping > only the Nth and N-1rst builds) > (I have a script that might already work for this, or would need > tweaking.) > b) heuristics to determine when an older (N-2, N-3, ... N-z) build is > no longer needed, perhaps simply by assuming no one needs it after > 24hrs? > 24 hours should be more that enough. > c) a cleanup script which can purge all but the builds which are no > more than 1 day old, keeping at all times at least two builds (N and > N-1) > (I have a script that already does this for folders like > http://download.jboss.org/jbosstools/builds/nightly/core/trunk/ but > might need to be tweaked to work for a new pattern of > staging/\$\{JOB_NAME}/<BUILD_ID>/ .) > {quote} -- 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, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-15482) Replace staging & staging.previous (two builds w/ reused URLs) with uniquely timestamped build URLs and auto-regenerated composite*.xml files

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15482?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen commented on JBIDE-15482: --------------------------------------------- moved to jbide since not specific to jbds. > Replace staging & staging.previous (two builds w/ reused URLs) with uniquely timestamped build URLs and auto-regenerated composite*.xml files > --------------------------------------------------------------------------------------------------------------------------------------------- > > Key: JBIDE-15482 > URL: https://issues.jboss.org/browse/JBIDE-15482 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: build, updatesite > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 4.1.1.Alpha2 > > > Be it proposed: > {quote} > that instead of an in-place move which reuses > generic folder names like "staging" and "staging.previous", we > composite build output using unique names like > 2013-08-09_05-05-26-B7222/ or 2013-08-13_10-05-28-B7255 > {quote} > We therefore need: > a) to regenerate the composite site each time there's a new build > published, in order to remove the oldest and add the newest (keeping > only the Nth and N-1rst builds) > (I have a script that might already work for this, or would need > tweaking.) > b) heuristics to determine when an older (N-2, N-3, ... N-z) build is > no longer needed, perhaps simply by assuming no one needs it after > 24hrs? > 24 hours should be more that enough. > c) a cleanup script which can purge all but the builds which are no > more than 1 day old, keeping at all times at least two builds (N and > N-1) > (I have a script that already does this for folders like > http://download.jboss.org/jbosstools/builds/nightly/core/trunk/ but > might need to be tweaked to work for a new pattern of > staging/\$\{JOB_NAME}/<BUILD_ID>/ .) > {quote} -- 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, 7 months

1
0
0 / 0

[JBoss JIRA] (TOOLSDOC-388) Update explicit 7.0 text references in docs to 7.1

by Michelle Murray (JIRA)

[ https://issues.jboss.org/browse/TOOLSDOC-388?page=com.atlassian.jira.plug... ] Michelle Murray updated TOOLSDOC-388: ------------------------------------- Component/s: General documentation issues > Update explicit 7.0 text references in docs to 7.1 > -------------------------------------------------- > > Key: TOOLSDOC-388 > URL: https://issues.jboss.org/browse/TOOLSDOC-388 > Project: Documentation for JBoss Tools and Developer Studio > Issue Type: Task > Components: General documentation issues > Affects Versions: 4.1.0 > Reporter: Michelle Murray > Assignee: Michelle Murray > Fix For: 4.2.0 > > > Section that need updating > *Installation Guide* > * 2.2. Supported Operating Systems and Architectures > * 2.3. Computer Memory > * 2.4. Compatible Java Developer Kits > * 3.2. Install JBoss Developer Studio > * 3.3. Install JBoss Developer Studio BYOE > * 5.2. Upgrade JBoss Developer Studio > * 5.3. Upgrade JBoss Developer Studio BYOE > *Migration Guide* (2.2 and 2.3 shared with Installation Guide) > * 2.2. Upgrade JBoss Developer Studio > * 2.3. Upgrade JBoss Developer Studio BYOE > * 3.1. Change the Version of Eclipse Being Used with JBoss Developer Studio BYOE > *Getting Started Guide* (3.2 shared with Installation Guide) > * 2.1. About Getting Started > * 3.1. Installation Assumptions > * 3.2. Install JBoss Developer Studio > * 4.3. Tutorial Assumptions > *User Guide* > * None -- 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, 7 months

1
0
0 / 0

[JBoss JIRA] (TOOLSDOC-261) Add in documentation for Seam Servlet Module support through tooling

by Michelle Murray (JIRA)

[ https://issues.jboss.org/browse/TOOLSDOC-261?page=com.atlassian.jira.plug... ] Michelle Murray updated TOOLSDOC-261: ------------------------------------- Fix Version/s: Future (was: 3.3.0.Final) > Add in documentation for Seam Servlet Module support through tooling > -------------------------------------------------------------------- > > Key: TOOLSDOC-261 > URL: https://issues.jboss.org/browse/TOOLSDOC-261 > Project: Documentation for JBoss Tools and Developer Studio > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: User Guide - Seam Tools > Affects Versions: 3.3.0.Final > Reporter: Isaac Rooskov > Assignee: Michelle Murray > Fix For: Future > > > See these links for more information: > https://issues.jboss.org/browse/JBIDE-9388 > http://docs.jboss.org/seam/3/servlet/latest/reference/en-US/html/index.html -- 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, 7 months

1
0
0 / 0

[JBoss JIRA] (TOOLSDOC-316) The JBDS Getting Started Guide for JBDS 6.x needs updating from JBDS 5

by Michelle Murray (JIRA)

[ https://issues.jboss.org/browse/TOOLSDOC-316?page=com.atlassian.jira.plug... ] Michelle Murray updated TOOLSDOC-316: ------------------------------------- Fix Version/s: 4.0.0.Final > The JBDS Getting Started Guide for JBDS 6.x needs updating from JBDS 5 > ---------------------------------------------------------------------- > > Key: TOOLSDOC-316 > URL: https://issues.jboss.org/browse/TOOLSDOC-316 > Project: Documentation for JBoss Tools and Developer Studio > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: Getting Started Guide > Affects Versions: 4.0.0.Final > Reporter: Vineet Reynolds > Assignee: Michelle Murray > Fix For: 4.0.0.Final > > > Chapter 9 - "Example of developing a Java EE6, HTML5, Maven application for mobile devices" uses screen captures from JBDS 5. This needs to be updated for JBDS 6, since the location of the 'Target runtime' drop-down field has been moved. > The Target runtime is now prompted for, in the first dialog, instead of the second. The chapter notes also need updating. > The relevant section of the document is [linked|https://access.redhat.com/site/documentation//en-US/JBoss_Develope...]. Figures 9.3, 9.8 and 9.9 are the ones out of date, and so is the penultimate paragraph. -- 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, 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 2013