September 2013 - jbosstools-issues

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

by Xavier Coulon (JIRA)

Xavier Coulon created JBIDE-15430: ------------------------------------- Summary: 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: Xavier Coulon 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] (JBDS-2753) Merge "Google Plugin + Web Toolkit" + "Google Web Toolkit Designer"

by CDW Engine (JIRA)

[ https://issues.jboss.org/browse/JBDS-2753?page=com.atlassian.jira.plugin.... ] CDW Engine updated JBDS-2753: ----------------------------- CDW pm_ack: ? CDW release: ? > Merge "Google Plugin + Web Toolkit" + "Google Web Toolkit Designer" > ------------------------------------------------------------------- > > Key: JBDS-2753 > URL: https://issues.jboss.org/browse/JBDS-2753 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Reporter: Burr Sutter > > See screenshot. > Do we need to keep the two Google Web Toolkit options separate? They were separated because they came in at different intervals, now it is unclear to me if they need to remain separate. -- 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-2753) Merge "Google Plugin + Web Toolkit" + "Google Web Toolkit Designer"

by Burr Sutter (JIRA)

Burr Sutter created JBDS-2753: --------------------------------- Summary: Merge "Google Plugin + Web Toolkit" + "Google Web Toolkit Designer" Key: JBDS-2753 URL: https://issues.jboss.org/browse/JBDS-2753 Project: Developer Studio (JBoss Developer Studio) Issue Type: Feature Request Security Level: Public (Everyone can see) Reporter: Burr Sutter See screenshot. Do we need to keep the two Google Web Toolkit options separate? They were separated because they came in at different intervals, now it is unclear to me if they need to remain separate. -- 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-2736) Split Web and Mobile Development into 2 categories in JBT & JBDS Central

by Burr Sutter (JIRA)

[ https://issues.jboss.org/browse/JBDS-2736?page=com.atlassian.jira.plugin.... ] Burr Sutter commented on JBDS-2736: ----------------------------------- The new Web Category would be: Web Development Additional plugins to support web development Mobile Development Plugins to support HTML5 Mobile Hybrid application development > Split Web and Mobile Development into 2 categories in JBT & JBDS Central > ------------------------------------------------------------------------ > > Key: JBDS-2736 > URL: https://issues.jboss.org/browse/JBDS-2736 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: discovery > Reporter: Burr Sutter > > http://screencast.com/t/7vsajdz9o > Now that Cordova tools have been proposed, we need to split Web & Mobile into there own categories on the Software/Update tab. -- 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-15147) Livereload server shows restart status when it is used by BrowserSim

by Xavier Coulon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15147?page=com.atlassian.jira.plugi... ] Xavier Coulon commented on JBIDE-15147: --------------------------------------- [~kmarmaliykov], thanks for the feedback. Don't hesitate to reopen this issue if it still happens. > Livereload server shows restart status when it is used by BrowserSim > -------------------------------------------------------------------- > > Key: JBIDE-15147 > URL: https://issues.jboss.org/browse/JBIDE-15147 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: livereload > Affects Versions: 4.1.0.CR1 > Environment: Win7 64, Eclipse + JBT > Reporter: Konstantin Marmalyukov > Assignee: Xavier Coulon > Priority: Minor > Fix For: 4.1.1.Alpha1 > > Attachments: livereload_bug.png > > > I was testing browsersim working on CR1a and notice that livereload server shows Started, Restart status. But works fine. -- 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-15147) Livereload server shows restart status when it is used by BrowserSim

by Xavier Coulon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15147?page=com.atlassian.jira.plugi... ] Xavier Coulon resolved JBIDE-15147. ----------------------------------- Assignee: Xavier Coulon Release Notes Text: Marking as not reproducible for now. Fix Version/s: 4.1.1.Alpha1 (was: 4.1.x) Resolution: Cannot Reproduce Bug > Livereload server shows restart status when it is used by BrowserSim > -------------------------------------------------------------------- > > Key: JBIDE-15147 > URL: https://issues.jboss.org/browse/JBIDE-15147 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: livereload > Affects Versions: 4.1.0.CR1 > Environment: Win7 64, Eclipse + JBT > Reporter: Konstantin Marmalyukov > Assignee: Xavier Coulon > Priority: Minor > Fix For: 4.1.1.Alpha1 > > Attachments: livereload_bug.png > > > I was testing browsersim working on CR1a and notice that livereload server shows Started, Restart status. But works fine. -- 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-15147) Livereload server shows restart status when it is used by BrowserSim

by Konstantin Marmalyukov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15147?page=com.atlassian.jira.plugi... ] Konstantin Marmalyukov commented on JBIDE-15147: ------------------------------------------------ I cannot reproduce it once again on Devstudio GA. Hope it is fixed magically:) > Livereload server shows restart status when it is used by BrowserSim > -------------------------------------------------------------------- > > Key: JBIDE-15147 > URL: https://issues.jboss.org/browse/JBIDE-15147 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: livereload > Affects Versions: 4.1.0.CR1 > Environment: Win7 64, Eclipse + JBT > Reporter: Konstantin Marmalyukov > Priority: Minor > Fix For: 4.1.x > > Attachments: livereload_bug.png > > > I was testing browsersim working on CR1a and notice that livereload server shows Started, Restart status. But works fine. -- 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] (JBTIS-161) Should the JBTIS 4.1 target platform include SpringIDE 3.3 instead of 3.2?

by Paul Leacu (JIRA)

[ https://issues.jboss.org/browse/JBTIS-161?page=com.atlassian.jira.plugin.... ] Paul Leacu closed JBTIS-161. ---------------------------- Resolution: Done see Lars comment > Should the JBTIS 4.1 target platform include SpringIDE 3.3 instead of 3.2? > -------------------------------------------------------------------------- > > Key: JBTIS-161 > URL: https://issues.jboss.org/browse/JBTIS-161 > Project: JBoss Tools Integration Stack > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: target-platform > Affects Versions: 4.1.2 > Reporter: Nick Boldt > > The version of SpringIDE vetted by QE to be included in JBDS 7 Central is Spring IDE 3.3 [1]. > [1] http://download.jboss.org/jbosstools/updates/requirements/springide/3.3.0... > However, as reported in http://fusesource.com/issues/browse/ECLIPSE-955 Fuse currently depends on Spring IDE 3.2 [2] > [2] https://github.com/jbosstools/jbosstools-integration-stack/blob/master/ta... > This disconnect may cause problems when co-installing SpringIDE 3.3 from JBDS Central and Fuse (which will bring in SpringIDE 3.2 jars). > Therefore, should Central, JBTIS TP 4.1, and Fuse all use the same version of Spring IDE, namely 3.3 instead of 3.2 and 3.3? -- 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] (JBTIS-121) Failed to read artifact descriptor for org.jboss.sp when creating a Jboss app via JBoss Tool

by Paul Leacu (JIRA)

[ https://issues.jboss.org/browse/JBTIS-121?page=com.atlassian.jira.plugin.... ] Paul Leacu closed JBTIS-121. ---------------------------- Fix Version/s: (was: 4.1.0.Final) Resolution: Rejected This Jira is misplaced - it has nothing to do with an Integration Stack component. > Failed to read artifact descriptor for org.jboss.sp when creating a Jboss app via JBoss Tool > -------------------------------------------------------------------------------------------- > > Key: JBTIS-121 > URL: https://issues.jboss.org/browse/JBTIS-121 > Project: JBoss Tools Integration Stack > Issue Type: Bug > Security Level: Public(Everyone can see) > Affects Versions: 4.1.0.Final > Environment: Window7(Windows7_x64.qcow2) Git-1.8.3-preview2013.6.1 jdk-7u25-windows-x64 > Reporter: nan wei > Priority: Trivial > Attachments: pom.xml.PNG > > > Title：Failed to read artifact descriptor for org.jboss.sp when creating a Jboss app via JBoss Tool. > Description of problem: > When creating a Jboss app via JBoss Tool on Windows, the app will be created successfully, but a cross mark is appearing on the pom.xml in the project and return the error: > ArtifactDescriptorException:Failed to read artifact descriptor for org.jboss.sp(Click for details) > This issue does not happened on Fedora18, if a Jboss app is created in Jboss Tools on Fedroa18 , there is no such error presentation, it is created successfully. > Version: > JBossTools-4.1.0.final > Eclipse Standard 4.3 > OpenShift Enterprise 1.2.1/2013-07-29.3 > Window7 > How reproducible: > always > Steps to Reproduce: > 1. Create a jboss app via JBoss Tools > Type: jbosseap-6.0 or jbossews-1.0 or jbossews-2.0 > Actual results: > Cross mark is appearing on the pom.xml in the project and return the error > ArtifactDescriptorException:Failed to read artifact descriptor for org.jboss.sp(Click for details) > Expected results: > There is no such error description. > 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, 7 months

1
0
0 / 0

[JBoss JIRA] (JBTIS-163) Failed to resolve target definition

by Paul Leacu (JIRA)

[ https://issues.jboss.org/browse/JBTIS-163?page=com.atlassian.jira.plugin.... ] Paul Leacu resolved JBTIS-163. ------------------------------ Assignee: Paul Leacu Fix Version/s: 4.1.2 Resolution: Done Fixed by Nick - problem w/ Locus. https://github.com/jbosstools/jbosstools-integration-stack/commit/69e8ef4... > Failed to resolve target definition > ----------------------------------- > > Key: JBTIS-163 > URL: https://issues.jboss.org/browse/JBTIS-163 > Project: JBoss Tools Integration Stack > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: target-platform > Affects Versions: 4.1.2, 4.1.3 > Reporter: Andrej Podhradsky > Assignee: Paul Leacu > Priority: Blocker > Fix For: 4.1.2 > > > During building with target platform 4.1.2-SNAPSHOT / 4.1.2.Final (the same for 4.1.3) I'm getting the following error: > [ERROR] Internal error: java.lang.RuntimeException: Failed to resolve target definition /home/apodhrad/.m2/repository/org/jboss/tools/integration-stack/target-platform/4.1.2-SNAPSHOT/target-platform-4.1.2-SNAPSHOT-base.target: Could not find "org.jboss.tools.locus.jcip.annotations/1.0.0.Final-v20130729-2113-B39" in the repositories of the current location -> [Help 1] -- 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