[JBoss JIRA] (JBIDE-16592) Allow to update/remove software installed from Central
by Mickael Istria (JIRA)
[ https://issues.jboss.org/browse/JBIDE-16592?page=com.atlassian.jira.plugi... ]
Mickael Istria commented on JBIDE-16592:
----------------------------------------
It seems to be possible IMO that a users wants in the same time to uninstall a component, install another one, update another one, and install early access for yet another one.
Is this a usage we want to ignore? I don't get what would happen if the user check "Enable early-access". In case a component has both release and early access available, how should user see the difference?
> Allow to update/remove software installed from Central
> ------------------------------------------------------
>
> Key: JBIDE-16592
> URL: https://issues.jboss.org/browse/JBIDE-16592
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: central
> Reporter: Mickael Istria
> Fix For: 4.2.0.Beta1
>
> Attachments: JBIDE-16592-wip.jpeg, JBIDE_16592_shot2.jpeg
>
>
> Central software page should allow user to update or uninstall some modules.
--
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, 2 months
[JBoss JIRA] (JBIDE-16619) running new download runtimes from quick access result in exception
by Max Rydahl Andersen (JIRA)
[ https://issues.jboss.org/browse/JBIDE-16619?page=com.atlassian.jira.plugi... ]
Max Rydahl Andersen updated JBIDE-16619:
----------------------------------------
Fix Version/s: 4.1.2.CR1
(was: 4.2.0.Beta1)
> running new download runtimes from quick access result in exception
> -------------------------------------------------------------------
>
> Key: JBIDE-16619
> URL: https://issues.jboss.org/browse/JBIDE-16619
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: server
> Reporter: Max Rydahl Andersen
> Assignee: Rob Stryker
> Priority: Blocker
> Labels: regression
> Fix For: 4.1.2.CR1
>
>
> Cmd+3, type "download" and choose the "new download runtimes" item and you get:
> java.lang.ClassCastException: org.jboss.tools.runtime.ui.internal.wizard.DownloadRuntimesWizard cannot be cast to org.eclipse.ui.IWorkbenchWizard
> org.jboss.tools.runtime.ui.internal.wizard.DownloadRuntimesWizard cannot be cast to org.eclipse.ui.IWorkbenchWizard
--
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, 2 months
[JBoss JIRA] (JBIDE-16619) running new download runtimes from quick access result in exception
by Max Rydahl Andersen (JIRA)
[ https://issues.jboss.org/browse/JBIDE-16619?page=com.atlassian.jira.plugi... ]
Max Rydahl Andersen commented on JBIDE-16619:
---------------------------------------------
if present in maintanence we should fix this too.
> running new download runtimes from quick access result in exception
> -------------------------------------------------------------------
>
> Key: JBIDE-16619
> URL: https://issues.jboss.org/browse/JBIDE-16619
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: server
> Reporter: Max Rydahl Andersen
> Assignee: Rob Stryker
> Priority: Blocker
> Labels: regression
> Fix For: 4.1.2.CR1
>
>
> Cmd+3, type "download" and choose the "new download runtimes" item and you get:
> java.lang.ClassCastException: org.jboss.tools.runtime.ui.internal.wizard.DownloadRuntimesWizard cannot be cast to org.eclipse.ui.IWorkbenchWizard
> org.jboss.tools.runtime.ui.internal.wizard.DownloadRuntimesWizard cannot be cast to org.eclipse.ui.IWorkbenchWizard
--
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, 2 months
[JBoss JIRA] (JBIDE-16619) running new download runtimes from quick access result in exception
by Max Rydahl Andersen (JIRA)
Max Rydahl Andersen created JBIDE-16619:
-------------------------------------------
Summary: running new download runtimes from quick access result in exception
Key: JBIDE-16619
URL: https://issues.jboss.org/browse/JBIDE-16619
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: server
Reporter: Max Rydahl Andersen
Assignee: Rob Stryker
Priority: Blocker
Fix For: 4.2.0.Beta1
Cmd+3, type "download" and choose the "new download runtimes" item and you get:
java.lang.ClassCastException: org.jboss.tools.runtime.ui.internal.wizard.DownloadRuntimesWizard cannot be cast to org.eclipse.ui.IWorkbenchWizard
org.jboss.tools.runtime.ui.internal.wizard.DownloadRuntimesWizard cannot be cast to org.eclipse.ui.IWorkbenchWizard
--
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, 2 months
[JBoss JIRA] (JBIDE-16592) Allow to update/remove software installed from Central
by Max Rydahl Andersen (JIRA)
[ https://issues.jboss.org/browse/JBIDE-16592?page=com.atlassian.jira.plugi... ]
Max Rydahl Andersen commented on JBIDE-16592:
---------------------------------------------
There is already an Install button. Why not add an Uninstall (or remove) button and then just keep the simpler and less complex combobox operations ?
like wise in that row could be a combo stating if they want to use earlyaccess or not.
This does not need to be an action on each individual element.
> Allow to update/remove software installed from Central
> ------------------------------------------------------
>
> Key: JBIDE-16592
> URL: https://issues.jboss.org/browse/JBIDE-16592
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: central
> Reporter: Mickael Istria
> Fix For: 4.2.0.Beta1
>
> Attachments: JBIDE-16592-wip.jpeg, JBIDE_16592_shot2.jpeg
>
>
> Central software page should allow user to update or uninstall some modules.
--
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, 2 months
[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 edited comment on JBIDE-14744 at 2/19/14 8:31 AM:
-------------------------------------------------------------------
It turns out that the spec is incomplete when it comes to cartridges. My current understanding of it is as follows:
{code}
- cartridge-spec := list of items
- list of items := ([) item,(item)* (])
- item := name | url | json object
- json object := json object with name- | url-proprety
- name := name | name-pattern
- name-pattern := substring (| substring)*
- substring := (*)string(*)
{code}
some examples:
{code:javascript}
"cartridges": "php-*, mysql-*",
"cartridges": "ruby-1.9, mysql",
"cartridges": "jbossas-",
"cartridges": "python-2|python-3",
"cartridges": "php-5",
"cartridges": "[{"url" : "https://cartreflect-claytondev.rhcloud.com/github/smarterclayton/openshift-go-cart#golang"}]",
"cartridges": "[{"url":"https://cartreflect-claytondev.rhcloud.com/reflect?github=aerogear/openshift-origin-cartridge-aerogear-push#AeroGear"}, "mysql-5"]",
"cartridges": "https://raw.github.com/openshift-cartridges/openshift-wildfly-cartridge/m...",
{code}
was (Author: adietish):
It turns out that the spec is incomplete when it comes to cartridges. My current understanding of it is as follows:
{code}
- cartridge-spec := list of items
- list of items := ([) item,(item)* (])
- item := name | url | json object
- json object := json object with name- | url-proprety
- name := name | name-pattern
- name-pattern := substring (| substring)*
- substring := (*)string(*)
{code}
some examples:
{code}
"cartridges": "php-*, mysql-*",
"cartridges": "ruby-1.9, mysql",
"cartridges": "jbossas-",
"cartridges": "python-2|python-3",
"cartridges": "php-5",
"cartridges": "[{"url" : "https://cartreflect-claytondev.rhcloud.com/github/smarterclayton/openshift-go-cart#golang"}]",
"cartridges": "[{"url":"https://cartreflect-claytondev.rhcloud.com/reflect?github=aerogear/openshift-origin-cartridge-aerogear-push#AeroGear"}, "mysql-5"]",
"cartridges": "https://raw.github.com/openshift-cartridges/openshift-wildfly-cartridge/m...",
{code}
> 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
> Assignee: Andre Dietisheim
> Priority: Blocker
> Labels: application_wizard
> Fix For: 4.2.0.Beta1
>
> Attachments: 2014-01-22 17.16.bmml, 2014-01-22 17.16.bmml, 2014-01-22 17.16.bmml, 2014-01-22 17.16.bmml, 2014-01-22 17.16.bmml, 2014-01-22 17.16.bmml, 2014-01-22 17.16.bmml, 2014-01-22 17.16.bmml, 2014-01-22 17.16.bmml, 2014-01-22 17.16.png, alternative-cartridges.png, crobson_2014-01-28 16.11.bmml, crobson_2014-01-28 16.11.bmml, crobson_2014-01-28 16.11.png, 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, 2 months
[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 edited comment on JBIDE-14744 at 2/19/14 8:32 AM:
-------------------------------------------------------------------
It turns out that the spec is incomplete when it comes to cartridges. My current understanding of it is as follows:
{code}
- cartridge-spec := list of items
- list of items := ([) item,(item)* (])
- item := name | url | json object
- json object := json object with name- | url-proprety
- name := name | name-pattern
- name-pattern := substring (| substring)*
- substring := (*)string(*)
{code}
some examples:
{code}
"cartridges": "php-*, mysql-*",
"cartridges": "ruby-1.9, mysql",
"cartridges": "jbossas-",
"cartridges": "python-2|python-3",
"cartridges": "php-5",
"cartridges": "[{"url" : "https://cartreflect-claytondev.rhcloud.com/github/smarterclayton/openshift-go-cart#golang"}]",
"cartridges": "[{"url":"https://cartreflect-claytondev.rhcloud.com/reflect?github=aerogear/openshift-origin-cartridge-aerogear-push#AeroGear"}, "mysql-5"]",
"cartridges": "https://raw.github.com/openshift-cartridges/openshift-wildfly-cartridge/m...",
{code}
was (Author: adietish):
It turns out that the spec is incomplete when it comes to cartridges. My current understanding of it is as follows:
{code}
- cartridge-spec := list of items
- list of items := ([) item,(item)* (])
- item := name | url | json object
- json object := json object with name- | url-proprety
- name := name | name-pattern
- name-pattern := substring (| substring)*
- substring := (*)string(*)
{code}
some examples:
{code:javascript}
"cartridges": "php-*, mysql-*",
"cartridges": "ruby-1.9, mysql",
"cartridges": "jbossas-",
"cartridges": "python-2|python-3",
"cartridges": "php-5",
"cartridges": "[{"url" : "https://cartreflect-claytondev.rhcloud.com/github/smarterclayton/openshift-go-cart#golang"}]",
"cartridges": "[{"url":"https://cartreflect-claytondev.rhcloud.com/reflect?github=aerogear/openshift-origin-cartridge-aerogear-push#AeroGear"}, "mysql-5"]",
"cartridges": "https://raw.github.com/openshift-cartridges/openshift-wildfly-cartridge/m...",
{code}
> 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
> Assignee: Andre Dietisheim
> Priority: Blocker
> Labels: application_wizard
> Fix For: 4.2.0.Beta1
>
> Attachments: 2014-01-22 17.16.bmml, 2014-01-22 17.16.bmml, 2014-01-22 17.16.bmml, 2014-01-22 17.16.bmml, 2014-01-22 17.16.bmml, 2014-01-22 17.16.bmml, 2014-01-22 17.16.bmml, 2014-01-22 17.16.bmml, 2014-01-22 17.16.bmml, 2014-01-22 17.16.png, alternative-cartridges.png, crobson_2014-01-28 16.11.bmml, crobson_2014-01-28 16.11.bmml, crobson_2014-01-28 16.11.png, 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, 2 months
[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 edited comment on JBIDE-14744 at 2/19/14 8:31 AM:
-------------------------------------------------------------------
It turns out that the spec is incomplete when it comes to cartridges. My current understanding of it is as follows:
{code}
- cartridge-spec := list of items
- list of items := ([) item,(item)* (])
- item := name | url | json object
- json object := json object with name- | url-proprety
- name := name | name-pattern
- name-pattern := substring (| substring)*
- substring := (*)string(*)
{code}
some examples:
{code}
"cartridges": "php-*, mysql-*",
"cartridges": "ruby-1.9, mysql",
"cartridges": "jbossas-",
"cartridges": "python-2|python-3",
"cartridges": "php-5",
"cartridges": "[{"url" : "https://cartreflect-claytondev.rhcloud.com/github/smarterclayton/openshift-go-cart#golang"}]",
"cartridges": "[{"url":"https://cartreflect-claytondev.rhcloud.com/reflect?github=aerogear/openshift-origin-cartridge-aerogear-push#AeroGear"}, "mysql-5"]",
"cartridges": "https://raw.github.com/openshift-cartridges/openshift-wildfly-cartridge/m...",
{code}
was (Author: adietish):
It turns out that the spec is incomplete when it comes to cartridges. My current understanding of it is as follows:
{code}
- cartridge-spec := list of items
- list of items := ([) item,(item)* (])
- item := name | url | json object
- json object := json object with name- | url-proprety
- name := name | name-pattern
- name-pattern := substring (| substring)*
- substring := (*)string(*)
{code}
> 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
> Assignee: Andre Dietisheim
> Priority: Blocker
> Labels: application_wizard
> Fix For: 4.2.0.Beta1
>
> Attachments: 2014-01-22 17.16.bmml, 2014-01-22 17.16.bmml, 2014-01-22 17.16.bmml, 2014-01-22 17.16.bmml, 2014-01-22 17.16.bmml, 2014-01-22 17.16.bmml, 2014-01-22 17.16.bmml, 2014-01-22 17.16.bmml, 2014-01-22 17.16.bmml, 2014-01-22 17.16.png, alternative-cartridges.png, crobson_2014-01-28 16.11.bmml, crobson_2014-01-28 16.11.bmml, crobson_2014-01-28 16.11.png, 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, 2 months