October 2013 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-15611) openshift-java-client: should be lenient to unknown http methods in links, should not fail

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15611?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-15611: ------------------------------------- Description: the openshift-java-client is currently failing when there are unknown http methods in the server responses. This is bad, it should not fail, should be lenient since such failing inhibits communications completely. The exact reason is a {code} HttpMethod.valueOf(httpMethod) {code} in the link constructor: {code:title=Link} protected Link(final String rel, final String href, final String httpMethod, final List<LinkParameter> requiredParams, final List<LinkParameter> optionalParams) { this(rel, href, HttpMethod.valueOf(httpMethod), requiredParams, optionalParams); } {code} was: the openshift-java-client is currently failing when there are unknown http methods in the server responses. This is bad, it should not fail, should be lenient since such failing inhibits communications completely. The exact reason is a {code} HttpMethod.valueOf(httpMethod) {code} in the link constructor: {code:Link} protected Link(final String rel, final String href, final String httpMethod, final List<LinkParameter> requiredParams, final List<LinkParameter> optionalParams) { this(rel, href, HttpMethod.valueOf(httpMethod), requiredParams, optionalParams); } {code} > openshift-java-client: should be lenient to unknown http methods in links, should not fail > ------------------------------------------------------------------------------------------ > > Key: JBIDE-15611 > URL: https://issues.jboss.org/browse/JBIDE-15611 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.2.0.Alpha1 > Reporter: Andre Dietisheim > Assignee: Andre Dietisheim > Fix For: 4.2.x > > > the openshift-java-client is currently failing when there are unknown http methods in the server responses. This is bad, it should not fail, should be lenient since such failing inhibits communications completely. > The exact reason is a > {code} > HttpMethod.valueOf(httpMethod) > {code} > in the link constructor: > {code:title=Link} > protected Link(final String rel, final String href, final String httpMethod, > final List<LinkParameter> requiredParams, final List<LinkParameter> optionalParams) { > this(rel, href, HttpMethod.valueOf(httpMethod), requiredParams, optionalParams); > } > {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, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-15611) openshift-java-client: should be lenient to unknown http methods in links, should not fail

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15611?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-15611: ------------------------------------- Description: the openshift-java-client is currently failing when there are unknown http methods in the server responses. This is bad, it should not fail, should be lenient since such failing inhibits communications completely. The exact reason is a {code} HttpMethod.valueOf(httpMethod) {code} in the Link constructor: {code:title=Link} protected Link(final String rel, final String href, final String httpMethod, final List<LinkParameter> requiredParams, final List<LinkParameter> optionalParams) { this(rel, href, HttpMethod.valueOf(httpMethod), requiredParams, optionalParams); } {code} was: the openshift-java-client is currently failing when there are unknown http methods in the server responses. This is bad, it should not fail, should be lenient since such failing inhibits communications completely. The exact reason is a {code} HttpMethod.valueOf(httpMethod) {code} in the link constructor: {code:title=Link} protected Link(final String rel, final String href, final String httpMethod, final List<LinkParameter> requiredParams, final List<LinkParameter> optionalParams) { this(rel, href, HttpMethod.valueOf(httpMethod), requiredParams, optionalParams); } {code} > openshift-java-client: should be lenient to unknown http methods in links, should not fail > ------------------------------------------------------------------------------------------ > > Key: JBIDE-15611 > URL: https://issues.jboss.org/browse/JBIDE-15611 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.2.0.Alpha1 > Reporter: Andre Dietisheim > Assignee: Andre Dietisheim > Fix For: 4.2.x > > > the openshift-java-client is currently failing when there are unknown http methods in the server responses. This is bad, it should not fail, should be lenient since such failing inhibits communications completely. > The exact reason is a > {code} > HttpMethod.valueOf(httpMethod) > {code} > in the Link constructor: > {code:title=Link} > protected Link(final String rel, final String href, final String httpMethod, > final List<LinkParameter> requiredParams, final List<LinkParameter> optionalParams) { > this(rel, href, HttpMethod.valueOf(httpMethod), requiredParams, optionalParams); > } > {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, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-15597) Environmental Variables UI

by Martes Wigglesworth (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15597?page=com.atlassian.jira.plugi... ] Martes Wigglesworth commented on JBIDE-15597: --------------------------------------------- For current updates on this effort, please reference the following: https://github.com/mwigglesworth-redhat/jbosstools-openshift > Environmental Variables UI > -------------------------- > > Key: JBIDE-15597 > URL: https://issues.jboss.org/browse/JBIDE-15597 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.2.0.Alpha1 > Reporter: Martes Wigglesworth > Priority: Blocker > Attachments: Environmental Variables UI WorkFlow.bmml, Environmental Variables UI WorkFlow.bmml, Environmental Variables UI WorkFlow.bmml, Environmental Variables UI WorkFlow.bmml, Environmental Variables UI WorkFlow.png, manage-keys.png > > > GUI development tasking for creating the workflow for inserting environmental variable artifacts into the application being created via the JBDT OpenShift plugin. -- 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, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-15597) Environmental Variables UI

by Martes Wigglesworth (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15597?page=com.atlassian.jira.plugi... ] Martes Wigglesworth edited comment on JBIDE-15597 at 10/3/13 2:37 PM: ---------------------------------------------------------------------- I was really going for isolation of the workflow, since I had trouble with the mockup tools. (first time I used it.) was (Author: mwigglesworth-redhat): This is due to not being able to find such an artifact in the mockup tool. I am going to upload the full set of screenshots which depict what I am intending, when I get started again, this morning. I was a bit disappointed that I couldn't easily find a simple table view with n-many columns to display. The screenshots are associated with the CDT configuration tab for environmental variables, and depict the appropriate view that I wish to build from. However, I think the flow is what I was also attempting to show, which I am not able to do with simple screenshots. > Environmental Variables UI > -------------------------- > > Key: JBIDE-15597 > URL: https://issues.jboss.org/browse/JBIDE-15597 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.2.0.Alpha1 > Reporter: Martes Wigglesworth > Priority: Blocker > Attachments: Environmental Variables UI WorkFlow.bmml, Environmental Variables UI WorkFlow.bmml, Environmental Variables UI WorkFlow.bmml, Environmental Variables UI WorkFlow.bmml, Environmental Variables UI WorkFlow.png, manage-keys.png > > > GUI development tasking for creating the workflow for inserting environmental variable artifacts into the application being created via the JBDT OpenShift plugin. -- 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, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-15597) Environmental Variables UI

by Martes Wigglesworth (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15597?page=com.atlassian.jira.plugi... ] Martes Wigglesworth edited comment on JBIDE-15597 at 10/3/13 2:36 PM: ---------------------------------------------------------------------- I was unable to adiquately depict the same view that I am intending, hence the lack of some features within the mockup. was (Author: mwigglesworth-redhat): I was going to remove the mockup since they don't do what I want, and are pretty much irrelivant, since they have created questions that don't need to be asked, due to confusion. However, there does not seem to be a way to do so, in Jira, so I will leave them for now. Please reference the screenshots for indication of the actual view's intended appearance. I will simply use screenshots and indicate their use. I don't have time to figure out how to make this simplistic tool do what I need. > Environmental Variables UI > -------------------------- > > Key: JBIDE-15597 > URL: https://issues.jboss.org/browse/JBIDE-15597 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.2.0.Alpha1 > Reporter: Martes Wigglesworth > Priority: Blocker > Attachments: Environmental Variables UI WorkFlow.bmml, Environmental Variables UI WorkFlow.bmml, Environmental Variables UI WorkFlow.bmml, Environmental Variables UI WorkFlow.bmml, Environmental Variables UI WorkFlow.png, manage-keys.png > > > GUI development tasking for creating the workflow for inserting environmental variable artifacts into the application being created via the JBDT OpenShift plugin. -- 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, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-15597) Environmental Variables UI

by Martes Wigglesworth (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15597?page=com.atlassian.jira.plugi... ] Martes Wigglesworth edited comment on JBIDE-15597 at 10/3/13 2:34 PM: ---------------------------------------------------------------------- Thanks for the update. Also, for the comments about the standards associated with indicating a pop-up menu. (Restricted to jira-users group) was (Author: mwigglesworth-redhat): Thanks for the update. Also, for the comments about the standards associated with indicating a pop-up menu. I mention the inconvenience because I looked through quite a few screens and topics and did not isolate what you have done in probably a few seconds. I just don't have time to learn SWT, the plugin, and some other tool that is really irrelevant to what I am doing, at this time. (But I will definitely take time to figure it out once the view is done, and I have some more time.) > Environmental Variables UI > -------------------------- > > Key: JBIDE-15597 > URL: https://issues.jboss.org/browse/JBIDE-15597 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.2.0.Alpha1 > Reporter: Martes Wigglesworth > Priority: Blocker > Attachments: Environmental Variables UI WorkFlow.bmml, Environmental Variables UI WorkFlow.bmml, Environmental Variables UI WorkFlow.bmml, Environmental Variables UI WorkFlow.bmml, Environmental Variables UI WorkFlow.png, manage-keys.png > > > GUI development tasking for creating the workflow for inserting environmental variable artifacts into the application being created via the JBDT OpenShift plugin. -- 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, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-15597) Environmental Variables UI

by Martes Wigglesworth (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15597?page=com.atlassian.jira.plugi... ] Martes Wigglesworth commented on JBIDE-15597: --------------------------------------------- As of 02-OCT-2013, I have created the view(s), and model(s) skeletons for the following activities: 1) Add 2) Remove 3) Edit 4)Import 5) Export The skeleton for the generic wizard view that will be the kickstart for all the components has also been constructed. > Environmental Variables UI > -------------------------- > > Key: JBIDE-15597 > URL: https://issues.jboss.org/browse/JBIDE-15597 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.2.0.Alpha1 > Reporter: Martes Wigglesworth > Priority: Blocker > Attachments: Environmental Variables UI WorkFlow.bmml, Environmental Variables UI WorkFlow.bmml, Environmental Variables UI WorkFlow.bmml, Environmental Variables UI WorkFlow.bmml, Environmental Variables UI WorkFlow.png, manage-keys.png > > > GUI development tasking for creating the workflow for inserting environmental variable artifacts into the application being created via the JBDT OpenShift plugin. -- 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, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-15610) since one forge plugin has bumped, so should all of them in 4.1.x

by Nick Boldt (JIRA)

Nick Boldt created JBIDE-15610: ---------------------------------- Summary: since one forge plugin has bumped, so should all of them in 4.1.x Key: JBIDE-15610 URL: https://issues.jboss.org/browse/JBIDE-15610 Project: Tools (JBoss Tools) Issue Type: Bug Components: forge Affects Versions: 4.1.1.Alpha2 Reporter: Nick Boldt Assignee: Koen Aers Fix For: 4.1.1.Beta1 [~maxandersen] would prefer that since a single forge plugin (forge.runtime) has bumped from 1.3.3 to 1.4.1, that all the forge plugins (and their containing features) also bump at least their service (micro) increment. Thus: 1.2.0 -> 1.2.1 1.0.0 -> 1.0.1 2.0.0 -> 2.0.1 And in master branch [1], I'm guessing this is wrong: {code}org.jboss.tools.forge2.runtime_2.0.1.Alpha1-v20130927-1755-B403.jar{code} Shouldn't that be at version 2.1.0 or 2.0.100, not 2.0.1? [1] http://download.jboss.org/jbosstools/builds/staging/jbosstools-forge_mast... -- 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, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-15610) since one forge plugin has bumped, so should all of them in 4.1.x

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15610?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-15610: ------------------------------- Priority: Blocker (was: Major) > since one forge plugin has bumped, so should all of them in 4.1.x > ----------------------------------------------------------------- > > Key: JBIDE-15610 > URL: https://issues.jboss.org/browse/JBIDE-15610 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: forge > Affects Versions: 4.1.1.Alpha2 > Reporter: Nick Boldt > Assignee: Koen Aers > Priority: Blocker > Fix For: 4.1.1.Beta1 > > > [~maxandersen] would prefer that since a single forge plugin (forge.runtime) has bumped from 1.3.3 to 1.4.1, that all the forge plugins (and their containing features) also bump at least their service (micro) increment. > Thus: > 1.2.0 -> 1.2.1 > 1.0.0 -> 1.0.1 > 2.0.0 -> 2.0.1 > And in master branch [1], I'm guessing this is wrong: > {code}org.jboss.tools.forge2.runtime_2.0.1.Alpha1-v20130927-1755-B403.jar{code} > Shouldn't that be at version 2.1.0 or 2.0.100, not 2.0.1? > [1] http://download.jboss.org/jbosstools/builds/staging/jbosstools-forge_mast... -- 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, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-15610) For 4.1.1.Beta1: since one forge plugin has bumped, so should they all

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15610?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-15610: ------------------------------- Summary: For 4.1.1.Beta1: since one forge plugin has bumped, so should they all (was: since one forge plugin has bumped, so should all of them in 4.1.x) > For 4.1.1.Beta1: since one forge plugin has bumped, so should they all > ---------------------------------------------------------------------- > > Key: JBIDE-15610 > URL: https://issues.jboss.org/browse/JBIDE-15610 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: forge > Affects Versions: 4.1.1.Alpha2 > Reporter: Nick Boldt > Assignee: Koen Aers > Priority: Blocker > Fix For: 4.1.1.Beta1 > > > [~maxandersen] would prefer that since a single forge plugin (forge.runtime) has bumped from 1.3.3 to 1.4.1, that all the forge plugins (and their containing features) also bump at least their service (micro) increment. > Thus: > 1.2.0 -> 1.2.1 > 1.0.0 -> 1.0.1 > 2.0.0 -> 2.0.1 > And in master branch [1], I'm guessing this is wrong: > {code}org.jboss.tools.forge2.runtime_2.0.1.Alpha1-v20130927-1755-B403.jar{code} > Shouldn't that be at version 2.1.0 or 2.0.100, not 2.0.1? > [1] http://download.jboss.org/jbosstools/builds/staging/jbosstools-forge_mast... -- 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, 6 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 October 2013