September 2013 - jbosstools-issues

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

by Vlado Pakan (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15430?page=com.atlassian.jira.plugi... ] Vlado Pakan commented on JBIDE-15430: ------------------------------------- Please provide steps how to verify this Jira or close it > 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-14514) openshift-java-client: remove workaround for https://bugzilla.redhat.com/show_bug.cgi?id=812046

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-14514?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-14514: ------------------------------------- Fix Version/s: 4.2.0.Alpha1 (was: 4.2.x) > openshift-java-client: remove workaround for https://bugzilla.redhat.com/show_bug.cgi?id=812046 > ----------------------------------------------------------------------------------------------- > > Key: JBIDE-14514 > URL: https://issues.jboss.org/browse/JBIDE-14514 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.1.0.Beta1 > Reporter: Andre Dietisheim > Assignee: Andre Dietisheim > Fix For: 4.2.0.Alpha1 > > > In the latest implementations the OpenShift broker returns the embedded cartridges within the application as follows: > {code} > "embedded":{ > "mongodb-2.2":{ > "connection_url":"mongodb://$OPENSHIFT_MONGODB_DB_HOST:$OPENSHIFT_MONGODB_DB_PORT/", > "username":"admin", > "password":"NNxXMT1z8dVj", > "database_name":"springeap6", > "info":"Connection URL: mongodb://$OPENSHIFT_MONGODB_DB_HOST:$OPENSHIFT_MONGODB_DB_PORT/" > } > }, > {code} > Prior code was only returning the *info* property where we had to exctract the url via regex. The new broker is returning the *connection_url* which does not require any regex-treatment any more > The code in openshift-java-client marks this workaround with a TODO: > {code} > protected EmbeddedCartridgeResource(final String name, final String displayName, final String description, final CartridgeType type, String info, final Map<String, Link> links, > final Map<String, Message> messages, final ApplicationResource application) { > super(application.getService(), links, messages); > this.name = name; > this.displayName = displayName; > this.description = description; > this.type = type; > // TODO: fix this workaround once > // https://bugzilla.redhat.com/show_bug.cgi?id=812046 is fixed > this.url = extractUrl(info, messages); > this.application = application; > } > {code} -- 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 Vlado Pakan (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15147?page=com.atlassian.jira.plugi... ] Vlado Pakan edited comment on JBIDE-15147 at 9/11/13 3:10 PM: -------------------------------------------------------------- Steps to reproduce with JBT Alpha1-v20130909-0110-B392: 1. Import HTML5 project from JBoss Central 2. Run HTML5 project on server 3. Open HTML5project using Server view context menu Show in > Web Server via LiveReload Server 4. Choose Yes to inject Livereload.js script ASSERT: Live Reload Server status is [Started] 5. Update index.html file within VPE editor and save changes ASSERT: Live Reload Server status is [Started, Synchronized] 6. Stop Live Reload Server ASSERT: Live Reload Server status is [Stopped, Synchronized] 7. Repeat steps 3., 4. and 5. ERROR: Live Reload Server status is [Started, Restart] 8. Close Web Server 9. Repeat step 5. ASSERT: Live Reload Server is [Started] was (Author: vpakan): Steps to reproduce with JBT Alpha1-v20130909-0110-B392: 1. Import HTML5 project from JBoss Central 2. Run HTML5 project on server 3. Open HTML5project using Server view context menu Show in > Web Server via LiveReload Server 4. Choose Yes to inject Livereload.js script ASSERT: Live Reload Server status is [Started] 5. Update index.html file within VPE editor and save changes ASSERT: Live Reload Server status is [Started, Synchronized] 6. Stop Live Reload Server ASSERT: Live Reload Server status is [Stopped, Synchronized] 7. Repeat steps 3., 4. and 5. ERROR: Live Reload Server status is [Started, Restart] > 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] (JBDS-2761) generate content in staging/_composite_/core/{trunk, 4.1.kepler} based on new builds/staging/{JOB_NAME}/{BUILD_ID_N} and builds/staging/{JOB_NAME}/{BUILD_ID_N-1}

by Nick Boldt (JIRA)

Nick Boldt created JBDS-2761: -------------------------------- Summary: generate content in staging/_composite_/core/{trunk,4.1.kepler} based on new builds/staging/{JOB_NAME}/{BUILD_ID_N} and builds/staging/{JOB_NAME}/{BUILD_ID_N-1} Key: JBDS-2761 URL: https://issues.jboss.org/browse/JBDS-2761 Project: Developer Studio (JBoss Developer Studio) Issue Type: Sub-task Security Level: Public (Everyone can see) Components: build Affects Versions: 7.1.0.Alpha1 Reporter: Nick Boldt Assignee: Nick Boldt Fix For: 7.1.0.Alpha2 Because the content in builds/staging/\{JOB_NAME}/all/repo/ and builds/staging.previous/\{JOB_NAME}/all/repo/ is moving to builds/staging/\{JOB_NAME}/\{BUILD_ID_N} and builds/staging/\{JOB_NAME}/\{BUILD_ID_N-1}, we need to generate a list of matching build URLs for inclusion in the composite*.xml files, perhaps based on a template that's stored in github (to define which projects to include). Parameters to the generation would need to be: a) template b) number of builds per project to include (1, for stable_branch or 2, for trunk) Constraints: * Need to ensure that the generated files are always fresher than anything pulled from github via rsync, so templates should not be called "compositeContent.xml" but rather "compositeContent.template.xml" * Need to be able to run this regeneration as a Jenkins job, perhaps as the first step in https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-composite... and https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/jbosstools-composite... Worries: * What happens if the regen happens and then a jbosstools-cleanup.sh fires minutes later, wiping out that N-1 build? Does jbosstools-cleaup.sh need to regen these files 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, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-15205) OpenShift menu contribution issue

by Jakub Niedermertl (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15205?page=com.atlassian.jira.plugi... ] Jakub Niedermertl closed JBIDE-15205. ------------------------------------- Ok, closing. Version: 7.1.0.Alpha1 Build id: Alpha1-v20130909-0132-B378 > OpenShift menu contribution issue > --------------------------------- > > Key: JBIDE-15205 > URL: https://issues.jboss.org/browse/JBIDE-15205 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.1.0.CR1 > Reporter: Snjezana Peco > Assignee: Snjezana Peco > Fix For: 4.1.1.Alpha1, 4.2.0.Alpha1 > > Attachments: package-explorer-nonopenshift.png, package-explorer-openshift.png, project-explorer-nonopenshift.png, project-explorer-openshift.png > > > The OpenShift menu contribution is visible when right-clicking any Eclipse project (not only an OpenShift project). > The issue happens because the org.jboss.tools.openshift.express.ui.openshiftProjectPropertyTester property tester isn't declared correctly. > Also, its icon (marker.png) is too large for a context menu action. -- 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-2741) Replace staging & staging.previous (two builds w/ reused URLs) with uniquely timestamped build URLs and auto-regenerated composite*.xml files

by CDW Engine (JIRA)

[ https://issues.jboss.org/browse/JBDS-2741?page=com.atlassian.jira.plugin.... ] CDW Engine updated JBDS-2741: ----------------------------- CDW release: + (was: ?) > Replace staging & staging.previous (two builds w/ reused URLs) with uniquely timestamped build URLs and auto-regenerated composite*.xml files > --------------------------------------------------------------------------------------------------------------------------------------------- > > Key: JBDS-2741 > URL: https://issues.jboss.org/browse/JBDS-2741 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: build, requirements, updatesite > Affects Versions: 7.0.0.GA > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 7.1.0.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] (JBDS-2741) Replace staging & staging.previous (two builds w/ reused URLs) with uniquely timestamped build URLs and auto-regenerated composite*.xml files

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBDS-2741?page=com.atlassian.jira.plugin.... ] Nick Boldt updated JBDS-2741: ----------------------------- CDW devel_ack: + (was: ?) Status: New (was: New) > Replace staging & staging.previous (two builds w/ reused URLs) with uniquely timestamped build URLs and auto-regenerated composite*.xml files > --------------------------------------------------------------------------------------------------------------------------------------------- > > Key: JBDS-2741 > URL: https://issues.jboss.org/browse/JBDS-2741 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: build, requirements, updatesite > Affects Versions: 7.0.0.GA > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 7.1.0.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] (JBDS-2515) JBDS70_0011: [Commit] (Dev) (P3) Scan ~/jboss-runtimes automatically

by Len DiMaggio (JIRA)

[ https://issues.jboss.org/browse/JBDS-2515?page=com.atlassian.jira.plugin.... ] Len DiMaggio updated JBDS-2515: ------------------------------- CDW qa_ack: - If Burr thinks we can do without this one - we can do without it. > JBDS70_0011: [Commit] (Dev) (P3) Scan ~/jboss-runtimes automatically > -------------------------------------------------------------------- > > Key: JBDS-2515 > URL: https://issues.jboss.org/browse/JBDS-2515 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: requirements > Affects Versions: 7.0.0.GA > Reporter: Jiri Pallich > Assignee: Max Rydahl Andersen > Priority: Minor > > Usecase is to not have to setup runtimes every time you create a new workspace. Useful for demos and training sessions and those using many runtimes (e.g. EAP 5.0.1, EAP 6.0.0, EAP 6.0.1, SOA-P 5.x.y, etc) -- 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-2457) Mirror stable content on Akamai

by Len DiMaggio (JIRA)

[ https://issues.jboss.org/browse/JBDS-2457?page=com.atlassian.jira.plugin.... ] Len DiMaggio updated JBDS-2457: ------------------------------- CDW qa_ack: + > Mirror stable content on Akamai > ------------------------------- > > Key: JBDS-2457 > URL: https://issues.jboss.org/browse/JBDS-2457 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Enhancement > Security Level: Public(Everyone can see) > Components: requirements, updatesite > Reporter: Mickael Istria > Assignee: Mickael Istria > > In order to improve installation time (for both end-users and internal build/test usage), we should use Akamai on the stable folders if devstudio downloas site. -- 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-2572) JBDS70_1410: [Uncommit] (Dev) (P2) Make renaming of projects easier

by Len DiMaggio (JIRA)

[ https://issues.jboss.org/browse/JBDS-2572?page=com.atlassian.jira.plugin.... ] Len DiMaggio updated JBDS-2572: ------------------------------- CDW qa_ack: - > JBDS70_1410: [Uncommit] (Dev) (P2) Make renaming of projects easier > ------------------------------------------------------------------- > > Key: JBDS-2572 > URL: https://issues.jboss.org/browse/JBDS-2572 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Feature Request > Security Level: Public(Everyone can see) > Components: requirements > Reporter: Jiri Pallich > Assignee: Len DiMaggio > Fix For: 7.1.0.Alpha2 > > > Refactor/Rename a quickstart (project examples) and/or archetype generated project is difficult. Hibernate console error, maven pom.xml references, persistence.xml etc. > Check what issues there are and see which we can fix. -- 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