December 2013 - jbosstools-issues

[JBoss JIRA] (JBIDE-14744) Allow users to choose from quickstarts/templates when creatingApplication wizard: new application

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-14744?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-14744: ------------------------------------- Summary: Allow users to choose from quickstarts/templates when creatingApplication wizard: new application (was: Allow users to choose from quickstarts/templates when creating new application) > Allow users to choose from quickstarts/templates when creatingApplication wizard: new application > ------------------------------------------------------------------------------------------------- > > Key: JBIDE-14744 > URL: https://issues.jboss.org/browse/JBIDE-14744 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: openshift > Affects Versions: 4.1.0.Beta2 > Reporter: Andre Dietisheim > Fix For: LATER > > Attachments: openshift-quickstart.png > > > The web ui offers a large set of quickstarts/templates: > !openshift-quickstart.png! > in a mail from clayton on the 4th of june: > {quote} > For QuickStarts, brokers may choose to > a) enable community quickstarts > (the URL you saw below, set by COMMUNITY_QUICKSTART_URL being a URL in /etc/openshift/broker.conf) > b) enable their own list of quickstarts > (a different url, /broker/rest/quickstarts, configured from /etc/openshift/quickstarts.json) > c) disable the quickstarts link > (delete /etc/openshift/quickstarts.json) > To correctly fetch the quickstarts for a server, retrieve the API document > /broker/rest/api > and look for the LIST_QUICKSTARTS link. If it is present, you may retrieve quickstarts. If it is absent, you should assume there are no quickstarts. > Retrieving the list of quickstarts, unlike other REST API feed calls, is very specific: > * API versioning is not supported > * Only JSON is supported > * The body of the response is slightly different than standard REST API feed results > * If you encounter a parse error or an unexpected data value you are required to handle it gracefully by omitting the entry - the API may change without warning (although hopefully not) > The format of the JSON response (in either a) or b) above) is: > {quote} > {code} > { > data: [ > quickstart: { > id: "<string id>", > href: "<absolute URL to a display URL for the quickstart>", > name: "<name>", > updated: "<last update date in seconds from the epoch>", > summary: "<brief HTML body of the item>", > body: "<full HTML body of the item>", > cartridges: "<cartridge spec>", > website: "<URL of metadata about the source of the quickstart or the technology>", > tags: "<comma delimited list of tags>", > language: "<display name of the type of quickstart>", > initial_git_url: "<absolute URL or Git reference to source>", > provider: "openshift|reviewed|partner|community", # default is community > }, > ] > } > {code} > {quote} > You should assume that arbitrary content could be injected into any of these fields and defend yourself against XSS appropriately. You should also assume that the structure could be changed at any time. > Cartridge spec: > The cartridge spec is defined as either: > a) a comma delimited list of cartridge name search conditions > b) a string containing a JSON array > If the leading character of the cartridge spec is '[', you must convert the cartridge spec to JSON and submit the value provided to the server on creation as the "cartridges" field. > Otherwise, > 1) split the string by "," into "segments" > 2) trim whitespace from each segment > 3) split each segment by "|" into "matches" - these represent logical ORs > 4) strip leading and trailing "*" characters > 5) For each segment, return all cartridges that have a case-insensitive substring match on any of the "matches" in that segment for the user to select. > See https://github.com/openshift/origin-server/blob/77e1d3a6476ecb9dad5be6dea... > and https://github.com/openshift/origin-server/blob/77e1d3a6476ecb9dad5be6dea... > {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, 3 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-14744) Allow users to choose from quickstarts/templates when creatingApplication wizard: new application

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-14744?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-14744: ------------------------------------- Labels: application_wizard (was: ) > Allow users to choose from quickstarts/templates when creatingApplication wizard: new application > ------------------------------------------------------------------------------------------------- > > Key: JBIDE-14744 > URL: https://issues.jboss.org/browse/JBIDE-14744 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: openshift > Affects Versions: 4.1.0.Beta2 > Reporter: Andre Dietisheim > Labels: application_wizard > Fix For: LATER > > Attachments: openshift-quickstart.png > > > The web ui offers a large set of quickstarts/templates: > !openshift-quickstart.png! > in a mail from clayton on the 4th of june: > {quote} > For QuickStarts, brokers may choose to > a) enable community quickstarts > (the URL you saw below, set by COMMUNITY_QUICKSTART_URL being a URL in /etc/openshift/broker.conf) > b) enable their own list of quickstarts > (a different url, /broker/rest/quickstarts, configured from /etc/openshift/quickstarts.json) > c) disable the quickstarts link > (delete /etc/openshift/quickstarts.json) > To correctly fetch the quickstarts for a server, retrieve the API document > /broker/rest/api > and look for the LIST_QUICKSTARTS link. If it is present, you may retrieve quickstarts. If it is absent, you should assume there are no quickstarts. > Retrieving the list of quickstarts, unlike other REST API feed calls, is very specific: > * API versioning is not supported > * Only JSON is supported > * The body of the response is slightly different than standard REST API feed results > * If you encounter a parse error or an unexpected data value you are required to handle it gracefully by omitting the entry - the API may change without warning (although hopefully not) > The format of the JSON response (in either a) or b) above) is: > {quote} > {code} > { > data: [ > quickstart: { > id: "<string id>", > href: "<absolute URL to a display URL for the quickstart>", > name: "<name>", > updated: "<last update date in seconds from the epoch>", > summary: "<brief HTML body of the item>", > body: "<full HTML body of the item>", > cartridges: "<cartridge spec>", > website: "<URL of metadata about the source of the quickstart or the technology>", > tags: "<comma delimited list of tags>", > language: "<display name of the type of quickstart>", > initial_git_url: "<absolute URL or Git reference to source>", > provider: "openshift|reviewed|partner|community", # default is community > }, > ] > } > {code} > {quote} > You should assume that arbitrary content could be injected into any of these fields and defend yourself against XSS appropriately. You should also assume that the structure could be changed at any time. > Cartridge spec: > The cartridge spec is defined as either: > a) a comma delimited list of cartridge name search conditions > b) a string containing a JSON array > If the leading character of the cartridge spec is '[', you must convert the cartridge spec to JSON and submit the value provided to the server on creation as the "cartridges" field. > Otherwise, > 1) split the string by "," into "segments" > 2) trim whitespace from each segment > 3) split each segment by "|" into "matches" - these represent logical ORs > 4) strip leading and trailing "*" characters > 5) For each segment, return all cartridges that have a case-insensitive substring match on any of the "matches" in that segment for the user to select. > See https://github.com/openshift/origin-server/blob/77e1d3a6476ecb9dad5be6dea... > and https://github.com/openshift/origin-server/blob/77e1d3a6476ecb9dad5be6dea... > {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, 3 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-16145) OpenShift Tools: info i icon missing from New OpenShift App wizard

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-16145?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-16145: ------------------------------------- Estimated Difficulty: Low > OpenShift Tools: info i icon missing from New OpenShift App wizard > ------------------------------------------------------------------ > > Key: JBIDE-16145 > URL: https://issues.jboss.org/browse/JBIDE-16145 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.1.1.CR1 > Reporter: Michelle Murray > Attachments: OpenShift_newapp.png > > > In New OpenShift Application wizard, the following have * (asterisk) at the beginning: > * use existing application check box > * name field > * type field > This should be the (i) icon (blue i in a circle) like in Window>Install New Software wizard. > There maybe more in the wizard but I haven't got past the first page. > !OpenShift_newapp.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, 3 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-16145) OpenShift Tools: info i icon missing from New OpenShift App wizard

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-16145?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-16145: ------------------------------------- Fix Version/s: 4.2.x > OpenShift Tools: info i icon missing from New OpenShift App wizard > ------------------------------------------------------------------ > > Key: JBIDE-16145 > URL: https://issues.jboss.org/browse/JBIDE-16145 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.1.1.CR1 > Reporter: Michelle Murray > Fix For: 4.2.x > > Attachments: OpenShift_newapp.png > > > In New OpenShift Application wizard, the following have * (asterisk) at the beginning: > * use existing application check box > * name field > * type field > This should be the (i) icon (blue i in a circle) like in Window>Install New Software wizard. > There maybe more in the wizard but I haven't got past the first page. > !OpenShift_newapp.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, 3 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-16157) Typo in OpenShift preferences: time out > timeout

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-16157?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-16157: ------------------------------------- Fix Version/s: 4.2.x > Typo in OpenShift preferences: time out > timeout > ------------------------------------------------- > > Key: JBIDE-16157 > URL: https://issues.jboss.org/browse/JBIDE-16157 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.1.1.CR1, 4.2.0.Alpha1 > Reporter: Michelle Murray > Fix For: 4.2.x > > > In JBIDE-16044 (+ JBIDE-16051), I stated that the field name in the OpenShift pane of Preferences window should be 'Request remote time out'. > I was wrong. It should be one word in this instance. So 'Request remote *timeout*'. > FYI, both one word and two word usages exist but for use in different instances: > * time out = verb, e.g. the server will time out > * timeout = adjective or noun, e.g. timeout behavior or server timeout -- 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, 3 months

1
0
0 / 0

[JBoss JIRA] (JBDS-2868) Support multiple protocols when talking to OpenShift servers

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBDS-2868?page=com.atlassian.jira.plugin.... ] Andre Dietisheim updated JBDS-2868: ----------------------------------- Assignee: (was: Andre Dietisheim) > Support multiple protocols when talking to OpenShift servers > ------------------------------------------------------------ > > Key: JBDS-2868 > URL: https://issues.jboss.org/browse/JBDS-2868 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: openshift > Reporter: Andre Dietisheim > > The OpenShift backend offers different protocol version. Even though the OpenShift team is backporting new features to the current protocol 1.2 we're currently talking, we'll have to ramp up in protocol version at some point. Since we cannot loose the ability to talk to old servers (especially since OpenShift Enterprise is available), we have to be able to talk in different protocol versions. -- 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, 3 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-16299) NLS missing message: ClientTimeoutExplanation in: org.jboss.tools.openshift.express.internal.ui.OpenshiftUIMessages

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-16299?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-16299: ------------------------------------- Estimated Difficulty: Low > NLS missing message: ClientTimeoutExplanation in: org.jboss.tools.openshift.express.internal.ui.OpenshiftUIMessages > ------------------------------------------------------------------------------------------------------------------- > > Key: JBIDE-16299 > URL: https://issues.jboss.org/browse/JBIDE-16299 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.1.1.Final > Reporter: Denis Golovin > Priority: Trivial > -- 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, 3 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-15897) Make all relevant OpenShift Explorer actions available from Server Adapter

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15897?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-15897: ------------------------------------- Fix Version/s: 4.2.x > Make all relevant OpenShift Explorer actions available from Server Adapter > -------------------------------------------------------------------------- > > Key: JBIDE-15897 > URL: https://issues.jboss.org/browse/JBIDE-15897 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: openshift > Reporter: Max Rydahl Andersen > Fix For: 4.2.x > > Attachments: explorer-context-menu.png, server-adapter-context-menu.png > > > JBIDE-11841 was done earlier but only added the missing actions - when new actions are added we tend to forget to add them. > Explorer: > !explorer-context-menu.png! > Server adapter: > !server-adapter-context-menu.png! > We should make it so these actions (when relevant) gets added to both places (openshift explorer / server adapter) and optimally also available in an OpenShift context menu on a project. > Meaning you don't have to navigate to explorer view constantly. -- 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, 3 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-15897) Make all relevant OpenShift Explorer actions available from Server Adapter

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15897?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-15897: ------------------------------------- Estimated Difficulty: Low > Make all relevant OpenShift Explorer actions available from Server Adapter > -------------------------------------------------------------------------- > > Key: JBIDE-15897 > URL: https://issues.jboss.org/browse/JBIDE-15897 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: openshift > Reporter: Max Rydahl Andersen > Fix For: 4.2.x > > Attachments: explorer-context-menu.png, server-adapter-context-menu.png > > > JBIDE-11841 was done earlier but only added the missing actions - when new actions are added we tend to forget to add them. > Explorer: > !explorer-context-menu.png! > Server adapter: > !server-adapter-context-menu.png! > We should make it so these actions (when relevant) gets added to both places (openshift explorer / server adapter) and optimally also available in an OpenShift context menu on a project. > Meaning you don't have to navigate to explorer view constantly. -- 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, 3 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-15897) Make all relevant OpenShift Explorer actions available from Server Adapter

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15897?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-15897: ------------------------------------- Assignee: (was: Andre Dietisheim) > Make all relevant OpenShift Explorer actions available from Server Adapter > -------------------------------------------------------------------------- > > Key: JBIDE-15897 > URL: https://issues.jboss.org/browse/JBIDE-15897 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: openshift > Reporter: Max Rydahl Andersen > Attachments: explorer-context-menu.png, server-adapter-context-menu.png > > > JBIDE-11841 was done earlier but only added the missing actions - when new actions are added we tend to forget to add them. > Explorer: > !explorer-context-menu.png! > Server adapter: > !server-adapter-context-menu.png! > We should make it so these actions (when relevant) gets added to both places (openshift explorer / server adapter) and optimally also available in an OpenShift context menu on a project. > Meaning you don't have to navigate to explorer view constantly. -- 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, 3 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 December 2013