December 2010 - jbosstools-issues

[JBoss JIRA] Commented: (JBDS-17) Next button should be disabled If the installation folder was not selected .

by Max Andersen (JIRA)

[ https://issues.jboss.org/browse/JBDS-17?page=com.atlassian.jira.plugin.sy... ] Max Andersen commented on JBDS-17: ---------------------------------- Cleaning the gutters. Closing old bug reports with no updates the last 18 months. If you feel this close was unwarranted then please reopen or create a new one with link to the old and we will revisit. > Next button should be disabled If the installation folder was not selected . > ----------------------------------------------------------------------------- > > Key: JBDS-17 > URL: https://issues.jboss.org/browse/JBDS-17 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Components: installer > Affects Versions: 1.0.0.GA > Reporter: Anton Klimkovich > Assignee: Vladimir Ralev > Priority: Optional > Fix For: LATER > > > Run installation of RHDS > Go to step 3 > Clean field with installation path > Next button should be enabled. > If clean field with installation path and press Next the warning message will appear. ("You have not specified a target location. Is this correct ? "). If you press OK button The path to Folder where Installation was run will be inserted to installation path field. -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 3 months

1
0
0 / 0

[JBoss JIRA] Closed: (JBDS-17) Next button should be disabled If the installation folder was not selected .

by Max Andersen (JIRA)

[ https://issues.jboss.org/browse/JBDS-17?page=com.atlassian.jira.plugin.sy... ] Max Andersen closed JBDS-17. ---------------------------- Resolution: Out of Date > Next button should be disabled If the installation folder was not selected . > ----------------------------------------------------------------------------- > > Key: JBDS-17 > URL: https://issues.jboss.org/browse/JBDS-17 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Bug > Components: installer > Affects Versions: 1.0.0.GA > Reporter: Anton Klimkovich > Assignee: Vladimir Ralev > Priority: Optional > Fix For: LATER > > > Run installation of RHDS > Go to step 3 > Clean field with installation path > Next button should be enabled. > If clean field with installation path and press Next the warning message will appear. ("You have not specified a target location. Is this correct ? "). If you press OK button The path to Folder where Installation was run will be inserted to installation path field. -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 3 months

1
0
0 / 0

[JBoss JIRA] Updated: (JBIDE-7887) Execution Plan for a query executed in Teiid is hard to find in JBDS

by Max Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-7887?page=com.atlassian.jira.plugin... ] Max Andersen updated JBIDE-7887: -------------------------------- Fix Version/s: 3.2.0.CR1 John - targeted for CR1 just to remember feedback. If not relevant now then set the fix version appropriately (and im moving it off JBDS since not jbds specific) > Execution Plan for a query executed in Teiid is hard to find in JBDS > -------------------------------------------------------------------- > > Key: JBIDE-7887 > URL: https://issues.jboss.org/browse/JBIDE-7887 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: teiid > Reporter: Ramesh Reddy > Assignee: John Doyle > Fix For: 3.2.0.CR1 > > > Currently viewing of the execution plan is little cumbersome, it is not readily available as it did previous incarnation of the MetaMatrix Designer. Currently, the user needs to right click on the query and select "Teiid_7.1 --> Query Plan" see the query plan. > When a query is executed, the statement executed has the query already associated with it, so there is no good reason for user to take yet another step before they can see the query plan. It should be automatically populated in the "Execution Plan" tab when the query is executed. Or provide tool bar button on the "SQL Results" panel, that will take user to the "Execution Plan" of the current query. In case of query plan not available this tool bar button could be greyed out. > Since the query plan is in XML, show it in XML editor (read-only), that will let the user collapse or expand the the nodes to see and understand it, otherwise these are rather long, could be confusing to scroll. -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 3 months

1
0
0 / 0

[JBoss JIRA] Updated: (JBIDE-7886) Launch instance wizard: cannot launch image that does not start with ami-

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-7886?page=com.atlassian.jira.plugin... ] Andre Dietisheim updated JBIDE-7886: ------------------------------------ Steps to Reproduce: 1) make sure you have a connection to a ec2 backed deltacloud 2) go to the cloud view and select an image that does not start with ami-* (ex. aki-a53adfcc) 3) give it a name 4) hit finish Result: You get an error dialog that reports you an internal server error on the deltacloud server The error details are the following: org.jboss.tools.deltacloud.core.client.DeltaCloudClientException: The server reported an error "Internal Server Error" on requesting "http://try.steamcannon.org/deltacloud/api/instances?image_id=aki-a53adfcc..." was: 1) make sure you have a connection to a ec2 backed deltacloud 2) go to the cloud view and select an image that does not start with ami-* (ex. aki-a53adfcc) 3) give it a name 4) hit finish Result: You get an error dialog that reports you an internal server error on the deltacloud server > Launch instance wizard: cannot launch image that does not start with ami- > ------------------------------------------------------------------------- > > Key: JBIDE-7886 > URL: https://issues.jboss.org/browse/JBIDE-7886 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: deltacloud > Affects Versions: 3.2.0.Beta2 > Reporter: Andre Dietisheim > Assignee: Andre Dietisheim > Fix For: 3.2.0.Final > > -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 3 months

1
0
0 / 0

[JBoss JIRA] Created: (JBIDE-7808) Should ship with demos, cheat sheets and examples on using Infinispan

by Manik Surtani (JIRA)

Should ship with demos, cheat sheets and examples on using Infinispan --------------------------------------------------------------------- Key: JBIDE-7808 URL: https://jira.jboss.org/browse/JBIDE-7808 Project: Tools (JBoss Tools) Issue Type: Feature Request Components: infinispan Reporter: Manik Surtani Assignee: Max Andersen This could be repackaged versions of the demos that ship with Infinispan anyway. Further tutorials are available on Infinispan's wiki, along with a DZone RefCard which could be used as information sources for this feature. -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 3 months

2
1
0 / 0

[JBoss JIRA] Created: (JBIDE-7807) Report Infinispan-related bugs to JIRA

by Manik Surtani (JIRA)

Report Infinispan-related bugs to JIRA -------------------------------------- Key: JBIDE-7807 URL: https://jira.jboss.org/browse/JBIDE-7807 Project: Tools (JBoss Tools) Issue Type: Feature Request Components: infinispan Reporter: Manik Surtani Assignee: Max Andersen Using the IDE's built-in bug-reporting features, we should be able to report Infinispan-specific bugs to Infinispan's JIRA. -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 3 months

2
1
0 / 0

[JBoss JIRA] Created: (JBIDE-7806) Configuration Editor for Infinispan config files

by Manik Surtani (JIRA)

Configuration Editor for Infinispan config files ------------------------------------------------ Key: JBIDE-7806 URL: https://jira.jboss.org/browse/JBIDE-7806 Project: Tools (JBoss Tools) Issue Type: Feature Request Components: infinispan Reporter: Manik Surtani Assignee: Max Andersen Infinispan's configuration files come with XSD schemas which means a rich UI for editing and validating these files should be easy to build. Further, each field could contain accompanying help text, including sample values, details of each field, etc. Again, all of this is available online and can be linked to. http://docs.jboss.org/infinispan/4.2/apidocs/config.html http://docs.jboss.org/infinispan/schemas/infinispan-config-4.2.xsd -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 3 months

2
1
0 / 0

[JBoss JIRA] Created: (JBIDE-7810) Wizard to create a new Infinispan project

by Manik Surtani (JIRA)

Wizard to create a new Infinispan project ----------------------------------------- Key: JBIDE-7810 URL: https://jira.jboss.org/browse/JBIDE-7810 Project: Tools (JBoss Tools) Issue Type: Feature Request Components: infinispan Reporter: Manik Surtani Assignee: Max Andersen Could use the Infinispan Maven Archetype which will be built as a part of ISPN-817 -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 3 months

2
1
0 / 0

[JBoss JIRA] Created: (JBIDE-7809) Data grid configuration migration

by Manik Surtani (JIRA)

Data grid configuration migration --------------------------------- Key: JBIDE-7809 URL: https://jira.jboss.org/browse/JBIDE-7809 Project: Tools (JBoss Tools) Issue Type: Feature Request Components: infinispan Reporter: Manik Surtani Assignee: Max Andersen Infinispan has the ability to migrate configs from competing data grids on to Infinispan. Currently supported are migrating from JBoss Cache, EHCache and Coherence onto Infinispan. http://community.jboss.org/wiki/ConfigurationMigrationTools Ideally the IDE should detect configs of these competing data grids (they have XSDs or DTDs which can be used to detect, falling back to root element names) and provide a context menu to "migrate to Infinispan". This migration may optionally launch a migration wizard which could import Infinispan libs (add deps to a pom.xml?) and walk the user through a set of steps to migrate code. -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 3 months

2
1
0 / 0

[JBoss JIRA] Updated: (JBIDE-7885) jboss tools property editor enhancements for I18N

by nimo stephan (JIRA)

[ https://issues.jboss.org/browse/JBIDE-7885?page=com.atlassian.jira.plugin... ] nimo stephan updated JBIDE-7885: -------------------------------- Summary: jboss tools property editor enhancements for I18N (was: jboss tools property editor enhancements) > jboss tools property editor enhancements for I18N > ------------------------------------------------- > > Key: JBIDE-7885 > URL: https://issues.jboss.org/browse/JBIDE-7885 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Environment: jboss tools, eclipse > Reporter: nimo stephan > Assignee: Max Andersen > > It would be nice to enhance the property editor of jboss tools with the ability to provide a comfortable way for editing i18n. > Look at http://sourceforge.net/projects/eclipse-rbe/ (screenshots) which comes very handy when editing multiple language-files. > JSF provides I18N out of the box with .property files, but there is no way in jboss tools to handle (edit/create/view) different locations in a comfortable way. It should be possible, for example, to have a table-overview of all avaiable keys with their values without opening each property-file and toggling from one to another. Look at http://sourceforge.net/projects/eclipse-rbe/ for impressions. -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 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 2010