February 2014 - jbosstools-issues

[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: --------------------------------------------- I'm not a fan. This UI requires you to do operations individually - not in bulk. Why not just provide an Update and Uninstall button ? > 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

1
0
0 / 0

[JBoss JIRA] (JBIDE-16607) Seam 2.3 Potlet deployment error on JPP 6

by Radoslav Rábara (JIRA)

[ https://issues.jboss.org/browse/JBIDE-16607?page=com.atlassian.jira.plugi... ] Radoslav Rábara updated JBIDE-16607: ------------------------------------ Attachment: jpp61-server-log > Seam 2.3 Potlet deployment error on JPP 6 > ----------------------------------------- > > Key: JBIDE-16607 > URL: https://issues.jboss.org/browse/JBIDE-16607 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: portal-gatein > Affects Versions: 4.2.0.Alpha2 > Reporter: Radoslav Rábara > Priority: Critical > Fix For: 4.2.0.Beta1 > > Attachments: jpp61-server-log > > > Deployment of Seam Portal Project ends with error when it's deployed to JPP 6. > As far as I know, we have quickstarts for portal development on JPP 6. So is creating Portal Project via Dynamic Web Project supported only for older versions of EPP? -- 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

1
0
0 / 0

[JBoss JIRA] (JBIDE-16607) Seam 2.3 Potlet deployment error on JPP 6

by Radoslav Rábara (JIRA)

Radoslav Rábara created JBIDE-16607: --------------------------------------- Summary: Seam 2.3 Potlet deployment error on JPP 6 Key: JBIDE-16607 URL: https://issues.jboss.org/browse/JBIDE-16607 Project: Tools (JBoss Tools) Issue Type: Bug Components: portal-gatein Affects Versions: 4.2.0.Alpha2 Reporter: Radoslav Rábara Priority: Critical Fix For: 4.2.0.Beta1 Deployment of Seam Portal Project ends with error when it's deployed to JPP 6. As far as I know, we have quickstarts for portal development on JPP 6. So is creating Portal Project via Dynamic Web Project supported only for older versions of EPP? -- 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

1
0
0 / 0

[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 updated JBIDE-16592: ----------------------------------- Attachment: JBIDE_16592_shot2.jpeg Another shot, taking into account some pitfalls noticed by [~mmurray] !JBIDE_16592_shot2.jpeg! > 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

1
0
0 / 0

[JBoss JIRA] (JBIDE-16606) New Server Wizard updated for 'profiles'

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-16606?page=com.atlassian.jira.plugi... ] Rob Stryker commented on JBIDE-16606: ------------------------------------- <rawblem> http://imgur.com/m5Jllwv,vdNvUeB#0 <rawblem> http://imgur.com/m5Jllwv,vdNvUeB#1 > New Server Wizard updated for 'profiles' > ---------------------------------------- > > Key: JBIDE-16606 > URL: https://issues.jboss.org/browse/JBIDE-16606 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: server > Affects Versions: 4.2.0.Beta1 > Reporter: Rob Stryker > Assignee: Rob Stryker > Labels: affects_documentation > Fix For: 4.2.0.Beta1 > > > With the additions of server profiles, servers in the rse profile (or others) do not necessarily require a local runtime. This means in a new server wizard, we don't need to force the user to create a runtime until they're in a profile that requires one. > This will make changes to the new server wizard workflow which may affect some swt bot tests and documentation -- 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

1
0
0 / 0

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

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-14744?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen reassigned JBIDE-14744: ------------------------------------------- Assignee: Andre Dietisheim (was: Max Rydahl Andersen) > 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

1
0
0 / 0

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

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15897?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen updated JBIDE-15897: ---------------------------------------- Sprint: Sprint to 31.03.14 > 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, 2 months

1
0
0 / 0

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

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-14744?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen updated JBIDE-14744: ---------------------------------------- Sprint: Sprint to 31.03.14 > 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: Max Rydahl Andersen > 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

1
0
0 / 0

[JBoss JIRA] (JBIDE-15476) Allow users to provide downloadble cartidges

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15476?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-15476: ------------------------------------- Fix Version/s: 4.2.0.Beta1 (was: LATER) > Allow users to provide downloadble cartidges > -------------------------------------------- > > Key: JBIDE-15476 > URL: https://issues.jboss.org/browse/JBIDE-15476 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: openshift > Affects Versions: 4.1.1.Alpha2 > Reporter: Andre Dietisheim > Labels: help_wanted > Fix For: 4.2.0.Beta1 > > Attachments: 2013-09-30 17.14.bmml, 2013-09-30 17.14.bmml, 2013-09-30 17.14.bmml, 2013-09-30 17.14.bmml, 2013-09-30 17.14.bmml, 2013-09-30 17.14.bmml, 2013-09-30 17.14.bmml, 2013-09-30 17.14.bmml, 2013-09-30 17.14.bmml, 2013-09-30 17.14.bmml, 2013-09-30 17.14.bmml, 2013-09-30 17.14.bmml, 2013-09-30 17.14.bmml, 2013-09-30 17.14.bmml, 2013-09-30 17.14.png, add-cartridge.png, add-downloadable-cartridge.png, new-application-1.png, new-application-2.png > > > OpenShift allows lately to provide your very own cartridge by giving it a git-url where the cartridge source may get cloned from. In the Web-UI this looks as follows: > !add-downloadable-cartridge.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, 2 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-15476) Allow users to provide downloadble cartidges

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15476?page=com.atlassian.jira.plugi... ] Andre Dietisheim reassigned JBIDE-15476: ---------------------------------------- Assignee: Andre Dietisheim > Allow users to provide downloadble cartidges > -------------------------------------------- > > Key: JBIDE-15476 > URL: https://issues.jboss.org/browse/JBIDE-15476 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: openshift > Affects Versions: 4.1.1.Alpha2 > Reporter: Andre Dietisheim > Assignee: Andre Dietisheim > Labels: help_wanted > Fix For: 4.2.0.Beta1 > > Attachments: 2013-09-30 17.14.bmml, 2013-09-30 17.14.bmml, 2013-09-30 17.14.bmml, 2013-09-30 17.14.bmml, 2013-09-30 17.14.bmml, 2013-09-30 17.14.bmml, 2013-09-30 17.14.bmml, 2013-09-30 17.14.bmml, 2013-09-30 17.14.bmml, 2013-09-30 17.14.bmml, 2013-09-30 17.14.bmml, 2013-09-30 17.14.bmml, 2013-09-30 17.14.bmml, 2013-09-30 17.14.bmml, 2013-09-30 17.14.png, add-cartridge.png, add-downloadable-cartridge.png, new-application-1.png, new-application-2.png > > > OpenShift allows lately to provide your very own cartridge by giving it a git-url where the cartridge source may get cloned from. In the Web-UI this looks as follows: > !add-downloadable-cartridge.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, 2 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 February 2014