September 2013 - jbosstools-issues

[JBoss JIRA] (JBIDE-13151) Editing deployed archive doesn't reflect on server

by Jakub Niedermertl (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13151?page=com.atlassian.jira.plugi... ] Jakub Niedermertl closed JBIDE-13151. ------------------------------------- Ok, closing Version: 7.1.0.Alpha1 Build id: Alpha1-v20130909-0132-B378 > Editing deployed archive doesn't reflect on server > -------------------------------------------------- > > Key: JBIDE-13151 > URL: https://issues.jboss.org/browse/JBIDE-13151 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: archives > Affects Versions: 4.0.0.CR1 > Reporter: Jaroslav Jankovič > Assignee: Rob Stryker > Fix For: 4.1.1.Alpha1 > > Attachments: JBIDE-13151.jpg > > -- 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-13482) View is not activated if it's already open

by Radoslav Rábara (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13482?page=com.atlassian.jira.plugi... ] Radoslav Rábara closed JBIDE-13482. ----------------------------------- Verified with JBDS 7.1.0 Alpha1-v20130909-0132-B378 > View is not activated if it's already open > ------------------------------------------ > > Key: JBIDE-13482 > URL: https://issues.jboss.org/browse/JBIDE-13482 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: server, upstream > Affects Versions: 4.0.0.Final > Reporter: Radim Hopp > Assignee: Rob Stryker > Fix For: 4.1.0.Final > > > "Show in -> <some view>" does not activate the view if it's already open. -- 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-171) dont override other connectors in discovery.xml

by Max Rydahl Andersen (JIRA)

Max Rydahl Andersen created JBTIS-171: ----------------------------------------- Summary: dont override other connectors in discovery.xml Key: JBTIS-171 URL: https://issues.jboss.org/browse/JBTIS-171 Project: JBoss Tools Integration Stack Issue Type: Bug Security Level: Public (Everyone can see) Components: distribution Reporter: Max Rydahl Andersen Currently this is in discovery plugin: siteUrl="${jboss.discovery.site.url:https://devstudio.jboss.com/updates/7.0-development/central/integration-stack/}" And instructions to test it says: -vmargs -Djboss.discovery.directory.url=http://www.qa.jboss.com/binaries/RHDS/discovery/integration/integration-stack/7.0.0.Beta1/devstudio-integration-stack-directory.xml -Djboss.discovery.site.url=http://www.qa.jboss.com/binaries/RHDS/discovery/integration/integration-stack/7.0.0.Beta1 This is all great but it disables all other connectors in JBDS/eclipse thus it makes it hard to get together. I suggest you use your own specific site url instead, something like: siteUrl="${jboss.discovery.integration-stack.site.url:https://devstudio.jboss.com/updates/7.0-development/central/integration-stack/}" Then the base connectors will still work. We might even consider using recursive properties to allow for a global override, this would need changing in both IS And core discovery.xml to the tune of: in core: siteUrl="${jboss.global.discovery.site.url,jboss.discovery.site.url:https://devstudio.jboss.com/updates/7.0-development/central/core}" in stack: siteUrl="${jboss.global.discovery.site.url,jboss.discovery.integration-stack.site.url:https://devstudio.jboss.com/updates/7.0-development/central/integration-stack/}" -- 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 Martin Malina (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15482?page=com.atlassian.jira.plugi... ] Martin Malina commented on JBIDE-15482: --------------------------------------- [~nickboldt] what will be the impact for our publishing of RedDeer? https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevS... publishes to http://download.jboss.org/jbosstools/builds/staging/RedDeer_master/all/repo/ So now it will be staging/CI/RedDeer_master/{BUILD_ID}/all/repo/ ? Will there be some static url pointing to the latest? Also, in the last I used (and plan to use in the future) https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/DevStudio/view/DevS... to generate e.g. http://download.jboss.org/jbosstools/updates/stable/juno/core/reddeer/0.2.0/ Will it still work the same way? > 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-14648) Portal Examples - JPP/GateIn requirement is fulfilled after adding EAP runtime

by Radoslav Rábara (JIRA)

[ https://issues.jboss.org/browse/JBIDE-14648?page=com.atlassian.jira.plugi... ] Radoslav Rábara closed JBIDE-14648. ----------------------------------- Verified with JBDS 7.1.0 Alpha1-v20130909-0132-B378 and EAP 6.1.0 > Portal Examples - JPP/GateIn requirement is fulfilled after adding EAP runtime > ------------------------------------------------------------------------------ > > Key: JBIDE-14648 > URL: https://issues.jboss.org/browse/JBIDE-14648 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: project-examples > Affects Versions: 4.1.0.Beta1 > Reporter: Rastislav Wagner > Assignee: Peter Palaga > Priority: Critical > Fix For: 4.1.0.Final > > > All portal examples (enterprise and community ones) have requirement to GateIn or JPP runtime. After adding EAP runtime, GateIn/JPP runtime is fulfilled which is wrong. -- 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-14764) Update VJET in Central

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-14764?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen commented on JBIDE-14764: --------------------------------------------- not urgent for alpha1. > Update VJET in Central > ---------------------- > > Key: JBIDE-14764 > URL: https://issues.jboss.org/browse/JBIDE-14764 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: central > Affects Versions: 4.1.0.Beta1 > Reporter: Victor Rubezhny > Assignee: Victor Rubezhny > Fix For: 4.1.1.Alpha2 > > Attachments: JBIDE14764.png > > > As VJET fixes issues in their 0.10 release (see JBIDE-14122), we should pull a newer version for Beta2 or CR1. -- 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: --------------------------------------- [~vpakan], thanks for providing me with the steps ! > 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.Alpha2 > > 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 updated JBIDE-15147: ---------------------------------- Fix Version/s: 4.1.1.Alpha2 (was: 4.1.1.Alpha1) > 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.Alpha2 > > 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-15317) LiveReload script injection corrupted html encoding

by Xavier Coulon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15317?page=com.atlassian.jira.plugi... ] Xavier Coulon commented on JBIDE-15317: --------------------------------------- [~vpakan], There is no combo in the LiveReload Configuration Editor anymore. You should simply set the Charset on the file itself in the file properties in Eclipse (in File>Properties>Resource, then set "UTF-8" in the "Text File Encoding" group). > LiveReload script injection corrupted html encoding > --------------------------------------------------- > > Key: JBIDE-15317 > URL: https://issues.jboss.org/browse/JBIDE-15317 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: livereload > Affects Versions: 4.1.0.Final > Reporter: Pei-Tang Huang > Assignee: Xavier Coulon > Priority: Critical > Labels: encoding, livereload > Fix For: 4.1.1.Alpha1, 4.2.0.Alpha1 > > Attachments: chinese.html > > Original Estimate: 1 day > Remaining Estimate: 1 day > > LiveReload script injection dissmisses the encoding of the original HTML content, my page contains CJK character in UTF-8 all became "?" character. -- 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-15317) LiveReload script injection corrupted html encoding

by Xavier Coulon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15317?page=com.atlassian.jira.plugi... ] Xavier Coulon edited comment on JBIDE-15317 at 9/12/13 3:12 AM: ---------------------------------------------------------------- Hello [~tangtheone], first, thanks for your feedback and thanks for reporting the invalid content-length header value that I was returning in my code ! I pushed an update of the PR in which the return content uses the same charset as the one given in the request, or it falls back the "Default Charset" that can be configured at the server level. Thus, if you set "UTF-8" at the LiveReload server level (this is the default value anyway), you should have the expected content in response. Let me know if this works for you. Thanks. Best regards, was (Author: xcoulon): Hello [~tangtheone], first, thanks for your feedback and thanks for reporting the invalid content-length header value that I returning in my code ! I pushed an update of the PR in which the return content uses the same charset as the one given in the request, or it falls back the "Default Charset" that can be configured at the server level. Thus, if you set "UTF-8" at the LiveReload server level (this is the default value anyway), you should have the expected content in response. Let me know if this works for you. Thanks. Best regards, > LiveReload script injection corrupted html encoding > --------------------------------------------------- > > Key: JBIDE-15317 > URL: https://issues.jboss.org/browse/JBIDE-15317 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: livereload > Affects Versions: 4.1.0.Final > Reporter: Pei-Tang Huang > Assignee: Xavier Coulon > Priority: Critical > Labels: encoding, livereload > Fix For: 4.1.1.Alpha1, 4.2.0.Alpha1 > > Attachments: chinese.html > > Original Estimate: 1 day > Remaining Estimate: 1 day > > LiveReload script injection dissmisses the encoding of the original HTML content, my page contains CJK character in UTF-8 all became "?" character. -- 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