September 2013 - jbosstools-issues

[JBoss JIRA] (JBIDE-14366) openshift-java-client: add method overloads that allow users to provide specific timeouts to specific operations

by Marián Labuda (JIRA)

[ https://issues.jboss.org/browse/JBIDE-14366?page=com.atlassian.jira.plugi... ] Marián Labuda closed JBIDE-14366. --------------------------------- > openshift-java-client: add method overloads that allow users to provide specific timeouts to specific operations > ---------------------------------------------------------------------------------------------------------------- > > Key: JBIDE-14366 > URL: https://issues.jboss.org/browse/JBIDE-14366 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: openshift > Affects Versions: 4.1.0.Beta1 > Reporter: Andre Dietisheim > Assignee: Andre Dietisheim > Fix For: 4.1.1.Alpha1, 4.2.0.Alpha1 > > > We need to have means for users to provide specific timeouts for specific operations. Ex. to create an application we'd call > {code} > domain.createApplication(name, cartridge, scale, gear) > {code} > If we want to increase timeouts for this specific operation, we cannot. We have to increase the url connection timeouts via the system properties. We should therefore offer > {code} > domain.createApplication(name, cartridge, scale, gear, TIMEOUT) > {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-15197) Wizard for exporting mobile application out of a Hybrid Mobile project

by Vlado Pakan (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15197?page=com.atlassian.jira.plugi... ] Vlado Pakan closed JBIDE-15197. ------------------------------- Verified with JBT Alpha1-v20130909-0110-B392 > Wizard for exporting mobile application out of a Hybrid Mobile project > ---------------------------------------------------------------------- > > Key: JBIDE-15197 > URL: https://issues.jboss.org/browse/JBIDE-15197 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: aerogear-hybrid > Reporter: Gorkem Ercan > Assignee: Gorkem Ercan > Priority: Minor > Fix For: 4.1.1.Alpha1 > > Original Estimate: 0 minutes > Remaining Estimate: 0 minutes > > Implement an export wizard that can create native platform's mobile application binary format. The wizard should do a "RELEASE" build to create the binaries. > We may try to support code signing as well, however on some platforms it may actually be easier to run the native tools to complete the signing. Prototype code signing and create a separate task for it if it should be pursued further. -- 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-13651) Export Native target platform project

by Vlado Pakan (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13651?page=com.atlassian.jira.plugi... ] Vlado Pakan commented on JBIDE-13651: ------------------------------------- Sorry my installation was messed up. Now I see dialog for mobile application export. > Export Native target platform project > ------------------------------------- > > Key: JBIDE-13651 > URL: https://issues.jboss.org/browse/JBIDE-13651 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: aerogear-hybrid > Reporter: Gorkem Ercan > Assignee: Gorkem Ercan > Priority: Minor > Fix For: 4.1.1.Alpha1 > > Original Estimate: 0 minutes > Remaining Estimate: 0 minutes > > Create a wizard to export native projects to supported target platforms. For iOS it will be Xcode project and for Android it will be ADT. Once exported projects will have no relation with our tools and it is expected that they will continue their life on their respected tool sets. -- 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] no problem, and thanks for confirming it's resolved ;-) > 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-15197) Wizard for exporting mobile application out of a Hybrid Mobile project

by Vlado Pakan (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15197?page=com.atlassian.jira.plugi... ] Vlado Pakan commented on JBIDE-15197: ------------------------------------- Sorry my installation was messed up. Now I see dialog for mobile application export. > Wizard for exporting mobile application out of a Hybrid Mobile project > ---------------------------------------------------------------------- > > Key: JBIDE-15197 > URL: https://issues.jboss.org/browse/JBIDE-15197 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: aerogear-hybrid > Reporter: Gorkem Ercan > Assignee: Gorkem Ercan > Priority: Minor > Fix For: 4.1.1.Alpha1 > > Original Estimate: 0 minutes > Remaining Estimate: 0 minutes > > Implement an export wizard that can create native platform's mobile application binary format. The wizard should do a "RELEASE" build to create the binaries. > We may try to support code signing as well, however on some platforms it may actually be easier to run the native tools to complete the signing. Prototype code signing and create a separate task for it if it should be pursued further. -- 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-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 closed JBIDE-15430. ------------------------------- Verified with JBT Alpha1-v20130909-0110-B392 > 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-15317) LiveReload script injection corrupted html encoding

by Vlado Pakan (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15317?page=com.atlassian.jira.plugi... ] Vlado Pakan resolved JBIDE-15317. --------------------------------- Resolution: Done Sorry for confusion. My JBT installation was messed up. Works fine with JBT Alpha1-v20130909-0110-B392 > 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 Vlado Pakan (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15317?page=com.atlassian.jira.plugi... ] Vlado Pakan closed JBIDE-15317. ------------------------------- > 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-15368) jbosstools-server has API Compatibility problem

by Jakub Niedermertl (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15368?page=com.atlassian.jira.plugi... ] Jakub Niedermertl commented on JBIDE-15368: ------------------------------------------- I've tried to verify this issue and I'm a bit confused: The Description says: "Latest version from jbosstools-server/jbosstools-4.1.x branch ..." however Steps to reproduce field mentions only two *stable* products: Eclipse Java EE IDE and 'JBoss Server Adapter Features from 4.1.0.Final stable update site'. Can you please provide more detailed steps to reproduce? > jbosstools-server has API Compatibility problem > ----------------------------------------------- > > Key: JBIDE-15368 > URL: https://issues.jboss.org/browse/JBIDE-15368 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: server > Affects Versions: 4.1.1.Alpha1 > Reporter: Denis Golovin > Assignee: Rob Stryker > Priority: Blocker > Labels: api-compatibility > Fix For: 4.1.1.Alpha1 > > > Latest version from jbosstools-server/jbosstools-4.1.x branch has API Compatibility problem: > "The field org.jboss.ide.eclipse.as.core.util.IJBossToolingConstants.WILDFLY8_MANAGEMENT_PORT_DEFAULT_PORT in an interface that is intended to be implemented or extended has been added". > According to http://wiki.eclipse.org/Evolving_Java-based_APIs_2 > || Interface change || Conditions || Compatibility || > |Add API field|If interface not implementable by Clients | Binary compatible| > |Add API field|If interface implementable by Clients| Breaks compatibility (2)| > (2) Adding an API field to an API interface that is implemented by Clients (e.g., a callback, listener, or visitor interface) breaks binary compatibility in a different way. A field added to a superinterface of C may hide an instance field inherited from a superclass of C, causing linking errors to be detected. Because of this fact, it is important to distinguish between API interfaces that Clients should implement from those that Clients should merely use. API interfaces that Clients should implement should not include fields. -- 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 Paul Leacu (JIRA)

[ https://issues.jboss.org/browse/JBTIS-171?page=com.atlassian.jira.plugin.... ] Paul Leacu updated JBTIS-171: ----------------------------- Assignee: Paul Leacu > 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 > Assignee: Paul Leacu > > 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

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