September 2013 - jbosstools-issues

[JBoss JIRA] (JBIDE-15400) openshift-java-client: Zend Studio 10 user cannot log in to OpenShift any more (WATCHER)

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15400?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-15400: ------------------------------------- Description: Zend Studio 10 is using openshift-java-client 2.0.1. With the latest update on OpenShift that added links to add/update environment variables the client library is not able to log in any more. It stumbles upon a new link parameter types. The client library is not tolerant enough. The only way they can fix this currently is by upgrading the client library to at least 2.0.3. Steps to reproduce: 1. open Zend Studio IDE 2. in the main menu, go to Window > Preferences and choose Openshift 3. add the following in the corresponding fields: Server URL: https://ec2-54-227-159-152.compute-1.amazonaws.com Domain: dev.rhcloud.com 4. click Apply, than OK (wizard should be closed) 5. click on Add new target button in down-right corner of the current Targets view (I am attaching a screenshot) 6. in the opened Add target wizard, choose Openshift and click Next button 7. in next screen, enter your credentials for your account at the Openshift (the RedHat's staging environment) 8. click on Generate button on the same screen (in order to generate new SSH Private key) 9. you will be asked if you wish to proceed creating the new private key in selected directory - click OK 10. click Finish button Expected result: Openshift target to be added successfully in targets list Actual result: I am attaching the result as well. (add openshift target failure.png) Error message is prompted to the user: {code} com.openshift.client.OpenShiftRequestException: Unknow request parameter type array {code} and only options are to go Back or to Cancel adding this target. !add-openshift-target-failure.png! was: Zend Studio 10 is using openshift-java-client 2.0.1. With the latest update on OpenShift that added links to add/update environment variables the client library is not able to log in any more. It stumbles upon a new link parameter types. The client library is not tolerant enough. The only way they can fix this currently is by upgrading the client library to at least 2.0.3. Steps to reproduce: 1. open Zend Studio IDE 2. in the main menu, go to Window > Preferences and choose Openshift 3. add the following in the corresponding fields: Server URL: https://ec2-54-227-159-152.compute-1.amazonaws.com Domain: dev.rhcloud.com 4. click Apply, than OK (wizard should be closed) 5. click on Add new target button in down-right corner of the current Targets view (I am attaching a screenshot) 6. in the opened Add target wizard, choose Openshift and click Next button 7. in next screen, enter your credentials for your account at the Openshift (the RedHat's staging environment) 8. click on Generate button on the same screen (in order to generate new SSH Private key) 9. you will be asked if you wish to proceed creating the new private key in selected directory - click OK 10. click Finish button Expected result: Openshift target to be added successfully in targets list Actual result: I am attaching the result as well. (add openshift target failure.png) Error message is prompted to the user: {quote} com.openshift.client.OpenShiftRequestException: Unknow request parameter type array {quote} and only options are to go Back or to Cancel adding this target. !add-openshift-target-failure.png! > openshift-java-client: Zend Studio 10 user cannot log in to OpenShift any more (WATCHER) > ---------------------------------------------------------------------------------------- > > Key: JBIDE-15400 > URL: https://issues.jboss.org/browse/JBIDE-15400 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: openshift > Affects Versions: 4.2.0.Alpha1 > Reporter: Andre Dietisheim > Assignee: Andre Dietisheim > Attachments: add-openshift-target-failure.png > > > Zend Studio 10 is using openshift-java-client 2.0.1. With the latest update on OpenShift that added links to add/update environment variables the client library is not able to log in any more. It stumbles upon a new link parameter types. The client library is not tolerant enough. > The only way they can fix this currently is by upgrading the client library to at least 2.0.3. > Steps to reproduce: > 1. open Zend Studio IDE > 2. in the main menu, go to Window > Preferences and choose Openshift > 3. add the following in the corresponding fields: > Server URL: https://ec2-54-227-159-152.compute-1.amazonaws.com > Domain: dev.rhcloud.com > 4. click Apply, than OK (wizard should be closed) > 5. click on Add new target button in down-right corner of the current > Targets view (I am attaching a screenshot) > 6. in the opened Add target wizard, choose Openshift and click Next button > 7. in next screen, enter your credentials for your account at the Openshift > (the RedHat's staging environment) > 8. click on Generate button on the same screen (in order to generate new SSH > Private key) > 9. you will be asked if you wish to proceed creating the new private key in > selected directory - click OK > 10. click Finish button > Expected result: > Openshift target to be added successfully in targets list > Actual result: > I am attaching the result as well. (add openshift target failure.png) > Error message is prompted to the user: > {code} > com.openshift.client.OpenShiftRequestException: Unknow request parameter > type array > {code} > and only options are to go Back or to Cancel adding this target. > !add-openshift-target-failure.png! -- 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-15400) openshift-java-client: Zend Studio 10 user cannot log in to OpenShift any more (WATCHER)

by Andre Dietisheim (JIRA)

Andre Dietisheim created JBIDE-15400: ---------------------------------------- Summary: openshift-java-client: Zend Studio 10 user cannot log in to OpenShift any more (WATCHER) Key: JBIDE-15400 URL: https://issues.jboss.org/browse/JBIDE-15400 Project: Tools (JBoss Tools) Issue Type: Bug Components: openshift Affects Versions: 4.2.0.Alpha1 Reporter: Andre Dietisheim Assignee: Andre Dietisheim Zend Studio 10 is using openshift-java-client 2.0.1. With the latest update on OpenShift that added links to add/update environment variables the client library is not able to log in any more. It stumbles upon a new link parameter types. The client library is not tolerant enough. The only way they can fix this currently is by upgrading the client library to at least 2.0.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] (JBIDE-15400) openshift-java-client: Zend Studio 10 user cannot log in to OpenShift any more (WATCHER)

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15400?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-15400: ------------------------------------- Issue Type: Task (was: Bug) > openshift-java-client: Zend Studio 10 user cannot log in to OpenShift any more (WATCHER) > ---------------------------------------------------------------------------------------- > > Key: JBIDE-15400 > URL: https://issues.jboss.org/browse/JBIDE-15400 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: openshift > Affects Versions: 4.2.0.Alpha1 > Reporter: Andre Dietisheim > Assignee: Andre Dietisheim > > Zend Studio 10 is using openshift-java-client 2.0.1. With the latest update on OpenShift that added links to add/update environment variables the client library is not able to log in any more. It stumbles upon a new link parameter types. The client library is not tolerant enough. > The only way they can fix this currently is by upgrading the client library to at least 2.0.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] (JBIDE-15335) Consider removing update site zips from jboss.org/tools

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15335?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen resolved JBIDE-15335. ----------------------------------------- Resolution: Rejected Yes, I agree and this should have been rejected sooner. not everyone has reliable network on this planet yet. Glad to have actual user usecase thus thanks for that! > Consider removing update site zips from jboss.org/tools > ------------------------------------------------------- > > Key: JBIDE-15335 > URL: https://issues.jboss.org/browse/JBIDE-15335 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: updatesite > Affects Versions: 4.0.1.Final, 4.1.0.Final > Reporter: Nick Boldt > Assignee: Max Rydahl Andersen > > Based on anecdotal evidence, it would appear that JBT 4.x is downloaded MANY MORE TIMES from Eclipse Marketplace than from jboss.org/tools: > As of 2013-08-12 12:48pm: > * Download stats from http://jboss.org/tools/download/stable/4_1 : 378 + 140 = *518 installs* (could be more if the zip's passed around w/in an org?) > * Install stats for JBT 4.1.0 from Eclipse Marketplace for 2013/08: *3,678 installs* ({color:red}*7.1x*{color} as many) > * Download stats from http://jboss.org/tools/download/stable/4_0 : 2441 + 899 = *3,340 installs* (could be more if the zip's passed around w/in an org?) > * Install stats for JBT 4.0.1 from Eclipse Marketplace for 2013/04 - 2013/08: 11280 + 10421 + 9552 + 6246 + 1635 = *39,134 installs* ({color:red}*11.7x*{color} as many) > So, is it time to stop providing a zip of the JBT update site? Seems like very few users want JBT delivered via zip. > Note too that the stats collected above include a partial month (August 2013) during which many people are on vacation. To get a real sense of the download rates we ought to check these numbers again in September and October. -- 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-15399) openshift-java-client: dont fail on unknown link-type

by Andre Dietisheim (JIRA)

Andre Dietisheim created JBIDE-15399: ---------------------------------------- Summary: openshift-java-client: dont fail on unknown link-type Key: JBIDE-15399 URL: https://issues.jboss.org/browse/JBIDE-15399 Project: Tools (JBoss Tools) Issue Type: Enhancement Components: openshift Affects Versions: 4.1.0.Final Reporter: Andre Dietisheim Assignee: Andre Dietisheim When unmarshalling responses from the server there are among other objects links that shall get created. Links look like the following: {code} "links":{ "UPDATE":{ "href":"/domains/foobar", "optional_params":[ ], "required_params":[ { "name":"id", "valid_options":[ ], "description":"Name of the domain", "type":"string" } ], "method":"PUT", "rel":"Update domain" ... {code} The unmarshalling code currently turns the "type" property into an enum. If the type that's provided is not known, then an exception is thrown: {code} public enum LinkParameterType { STRING, BOOLEAN, INTEGER, ARRAY; public static LinkParameterType valueOfIgnoreCase(String name) throws OpenShiftRequestException { if (name == null) { // no type provided (this is valid, not an error) return null; } try { return valueOf(name.toUpperCase()); } catch(IllegalArgumentException e) { throw new OpenShiftRequestException("Unknow request parameter type {0}", name); } } {code} This is not a good approach. The client library should be tolerant, it should ignore things it doesn't know to ensure it works with future responses. This is even more true as responses evolve over time even in the same protocol version: OpenShift is backporting new features (additions only) to old protocols! -- 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-15398) CDI Builder is sloooow

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15398?page=com.atlassian.jira.plugi... ] Fred Bricon updated JBIDE-15398: -------------------------------- Attachment: cdi-build-1.txt cdi-build-2.txt cdi-build-3.txt Attaching thread dumps taken over a 15 sec range. 1h43 in, build was at 98%. I killed the Validation Job, and workspace build completed faster, eventually. > CDI Builder is sloooow > ---------------------- > > Key: JBIDE-15398 > URL: https://issues.jboss.org/browse/JBIDE-15398 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: cdi > Affects Versions: 4.1.0.Final > Environment: Thinkpad T510, Windows 7-64, default JBDS 7.0.0.GA settings, jdk1.7.0_25 > Reporter: Fred Bricon > Attachments: cdi-build-1.txt, cdi-build-2.txt, cdi-build-3.txt > > > After cloning https://github.com/wildfly/wildfly, if you import all 130 projects as Maven projects, the CDI nature is automatically added via an m2e configurator. > 52 minutes after the import, the workspace is currently building at 81% and counting. Random jstack calls show most of the time is spent in the CDI Builder, as shown on the progress bar. > If I import the same projects in Luna (haven't tried on an clean KeplerEE distro yet) without CDI support (and admittedly the builk of JBT), import+build complete in ~12/13 min -- 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-165) Regression - Cannot add a file to the attachments

by Andrej Podhradsky (JIRA)

[ https://issues.jboss.org/browse/JBTIS-165?page=com.atlassian.jira.plugin.... ] Andrej Podhradsky updated JBTIS-165: ------------------------------------ Environment: JBoss ESB Tools 1.5.300.Final-v20130815-1755-B1189 > Regression - Cannot add a file to the attachments > ------------------------------------------------- > > Key: JBTIS-165 > URL: https://issues.jboss.org/browse/JBTIS-165 > Project: JBoss Tools Integration Stack > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: ESB > Affects Versions: 4.1.2 > Environment: JBoss ESB Tools 1.5.300.Final-v20130815-1755-B1189 > Reporter: Andrej Podhradsky > Priority: Blocker > Attachments: esb_attachment_bug.png, test.zip > > > Cannot add a file to the attachments from esbcontent folder. It's also impossible to add .txt file from the root but .zip file is possible to add. See the 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] (JBTIS-165) Regression - Cannot add a file to the attachments

by Andrej Podhradsky (JIRA)

[ https://issues.jboss.org/browse/JBTIS-165?page=com.atlassian.jira.plugin.... ] Andrej Podhradsky updated JBTIS-165: ------------------------------------ Attachment: esb_attachment_bug.png > Regression - Cannot add a file to the attachments > ------------------------------------------------- > > Key: JBTIS-165 > URL: https://issues.jboss.org/browse/JBTIS-165 > Project: JBoss Tools Integration Stack > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: ESB > Affects Versions: 4.1.2 > Reporter: Andrej Podhradsky > Priority: Blocker > Attachments: esb_attachment_bug.png, test.zip > > > Cannot add a file to the attachments from esbcontent folder. It's also impossible to add .txt file from the root but .zip file is possible to add. See the 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] (JBTIS-165) Regression - Cannot add a file to the attachments

by Andrej Podhradsky (JIRA)

[ https://issues.jboss.org/browse/JBTIS-165?page=com.atlassian.jira.plugin.... ] Andrej Podhradsky updated JBTIS-165: ------------------------------------ Attachment: test.zip > Regression - Cannot add a file to the attachments > ------------------------------------------------- > > Key: JBTIS-165 > URL: https://issues.jboss.org/browse/JBTIS-165 > Project: JBoss Tools Integration Stack > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: ESB > Affects Versions: 4.1.2 > Reporter: Andrej Podhradsky > Priority: Blocker > Attachments: esb_attachment_bug.png, test.zip > > > Cannot add a file to the attachments from esbcontent folder. It's also impossible to add .txt file from the root but .zip file is possible to add. See the 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] (JBTIS-165) Regression - Cannot add a file to the attachments

by Andrej Podhradsky (JIRA)

Andrej Podhradsky created JBTIS-165: --------------------------------------- Summary: Regression - Cannot add a file to the attachments Key: JBTIS-165 URL: https://issues.jboss.org/browse/JBTIS-165 Project: JBoss Tools Integration Stack Issue Type: Bug Security Level: Public (Everyone can see) Components: ESB Reporter: Andrej Podhradsky Priority: Blocker Cannot add a file to the attachments from esbcontent folder. It's also impossible to add .txt file from the root but .zip file is possible to add. See the 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

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