February 2012 - jbosstools-issues

[JBoss JIRA] Created: (JBIDE-1841) Error #1 while performing SchemaExport if server isn't started.

by Anton Klimkovich (JIRA)

Error #1 while performing SchemaExport if server isn't started. --------------------------------------------------------------- Key: JBIDE-1841 URL: http://jira.jboss.com/jira/browse/JBIDE-1841 Project: Tools (JBoss Tools) Issue Type: Bug Components: Hibernate Affects Versions: 2.0.1 Reporter: Anton Klimkovich Priority: Minor Attachments: exception.txt, TestHib.zip EXECUTE: Import attached java project. EXECUTE: Open Hibernate Configuration View EXECUTE: Right mouse click and select Add Configuration from context menu EXECUTE: On Main tab select imported project and path to cfg.xml EXECUTE: On Clathpath tab set path to hsqldb.jar EXECUTE: On Mappings tab add path to mapping file. EXECUTE: Press Apply button and Ok button ASSERT: Hibernate configuration appear in Hibernate Configuration View EXECUTE: Right mouse click on configeration in Hibernate Configuration View and select Run SchemaExport FAILURE: java.sql.SQLException: socket creation error Log attached. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 1 month

3
10
0 / 0

[JBoss JIRA] Created: (JBDS-1226) Progress Monitor when no server install required is incomplete

by Rob Stryker (JIRA)

Progress Monitor when no server install required is incomplete -------------------------------------------------------------- Key: JBDS-1226 URL: https://jira.jboss.org/browse/JBDS-1226 Project: Developer Studio (JBoss Developer Studio) Issue Type: Bug Components: installer Affects Versions: 3.0.1.GA Reporter: Rob Stryker Assignee: Denis Golovin Attachments: JBDS-1226.pic1.jpg When not adding a server, the progress monitor says "2 / 2" but the progress monitor is only half complete -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 1 month

4
8
0 / 0

[JBoss JIRA] Created: (JBIDE-4121) On a mac, once I minimize the yellow middle button, JBDS I have no way of clicking in the task bar to bring it back, I have to use the dock at the bottom of the screen in the right hand side.

by Jim Tyrrell (JIRA)

On a mac, once I minimize the yellow middle button, JBDS I have no way of clicking in the task bar to bring it back, I have to use the dock at the bottom of the screen in the right hand side. ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- Key: JBIDE-4121 URL: https://jira.jboss.org/jira/browse/JBIDE-4121 Project: Tools (JBoss Tools) Issue Type: Feature Request Reporter: Jim Tyrrell Other programs will use a diamond in the Window drop down to indicate the minimized window to maximize the application. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 1 month

3
13
0 / 0

[JBoss JIRA] Created: (JBIDE-7297) Problem with mavenized Seam project and Seam bundled with EAP

by Snjezana Peco (JIRA)

Problem with mavenized Seam project and Seam bundled with EAP ------------------------------------------------------------- Key: JBIDE-7297 URL: https://jira.jboss.org/browse/JBIDE-7297 Project: Tools (JBoss Tools) Issue Type: Bug Components: maven Affects Versions: 3.2.0.M2 Reporter: Snjezana Peco Assignee: Snjezana Peco A mavenized Seam project uses the <SEAM_HOME>build/root.pom.xml file to resolve versions of some maven artifacts Seam requires. Seam included in EAP contains some artifacts that don't exist on https://repository.jboss.org/nexus/content/groups/public and http://repository.jboss.org/maven2. For instance, 3.3.2.GA_CP03 is the version of hibernate-core, 3.3.1.SP2 is the version of richfaces, beta3.SP13 is the version of jboss-embedded-api ... and aren't on any of these two repositories. They exist on the http://repository.jboss.org/maven2-brew repository. Max, Should we add this repository to the pom.xml of a Seam parent project? -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 1 month

3
7
0 / 0

[JBoss JIRA] Created: (JBIDE-2764) Split up build(s) in smaller pieces

by Max Rydahl Andersen (JIRA)

Split up build(s) in smaller pieces ----------------------------------- Key: JBIDE-2764 URL: https://jira.jboss.org/jira/browse/JBIDE-2764 Project: Tools (JBoss Tools) Issue Type: Feature Request Components: Build/Releng Reporter: Max Rydahl Andersen Fix For: LATER Currently our build is very monolithic (for no real good reason) and that results in the build being very slow, not easy to see which component cause a failure since all dependents will also fail, respins takes alot of time ;( We should split up the build in smaller parts (not necessarily all the way down to modules) which makes it possible to build the various part more or less independently by just being able to take the generated artifacts from dependent builds. It would also be beneficial if the compile, test and upload parts gets separated so e.g. tests can be executed on separate platforms without having a full rebuild. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 1 month

1
1
0 / 0

[JBoss JIRA] Created: (JBIDE-7180) Unable to locate AMI in images list

by Pete Muir (JIRA)

Unable to locate AMI in images list ----------------------------------- Key: JBIDE-7180 URL: https://jira.jboss.org/browse/JBIDE-7180 Project: Tools (JBoss Tools) Issue Type: Bug Components: deltacloud Affects Versions: 3.2.0.M2 Reporter: Pete Muir Priority: Critical deltacloud appears to return some size limited set of images available, and in EC2 I have > 5000 -- so obviously the one I want isn't in this sublist (nb I have made this guess based upon going to the deltacloud web interface and browsing the images (the AMI I want isn't there), and then restricting by owner id (it is). -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 1 month

4
19
0 / 0

[JBoss JIRA] Created: (JBIDE-7426) Cannot update deltacloudd via gem update because of rack incompatiblity

by Jeff Johnston (JIRA)

Cannot update deltacloudd via gem update because of rack incompatiblity ----------------------------------------------------------------------- Key: JBIDE-7426 URL: https://jira.jboss.org/browse/JBIDE-7426 Project: Tools (JBoss Tools) Issue Type: Bug Components: deltacloud Affects Versions: 3.2.0.Beta1 Reporter: Jeff Johnston Using the instructions from www.deltacloud.org, the deltacloud core is installed via rubygems. If an update (sudo gem update), the rack component will attempt to update to 1.2.1, however, this causes the deltacloudd server to fail and one must uninstall rack to 1.1.0. The deltacloud team has been assigned a bug: https://bugzilla.redhat.com/show_bug.cgi?id=646633 to fix this. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 1 month

3
5
0 / 0

[JBoss JIRA] Created: (JBIDE-7372) run deltacloud in our tests

by Andre Dietisheim (JIRA)

run deltacloud in our tests --------------------------- Key: JBIDE-7372 URL: https://jira.jboss.org/browse/JBIDE-7372 Project: Tools (JBoss Tools) Issue Type: Feature Request Affects Versions: 3.2.0.Beta1 Reporter: Andre Dietisheim Assignee: Andre Dietisheim We need a self contained test setup where we have deltacloud started/stopped within our tests. this should be feasible with jruby -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 1 month

2
13
0 / 0

[JBoss JIRA] Created: (JBIDE-7365) Trying to start a stopped EC2 instance results in infinite starting task

by Jeff Johnston (JIRA)

Trying to start a stopped EC2 instance results in infinite starting task ------------------------------------------------------------------------ Key: JBIDE-7365 URL: https://jira.jboss.org/browse/JBIDE-7365 Project: Tools (JBoss Tools) Issue Type: Bug Components: deltacloud Affects Versions: 3.2.0.Beta2 Reporter: Jeff Johnston Using deltacloud 0.0.7, when an EC2 instance is stopped, it is no longer listed as TERMINATED as it was in deltacloud 0.0.5. Instead, it is listed as STOPPED and the REST interface reports that a START action is possible. This is not true. An EC2 instance, once stopped, is terminated and cannot be restarted. The Deltacloud tools get the available actions from the REST interface and so if a user attempts to start the instance, the tools will allow this and set up a task to wait for the state to change from STOPPED, but this will never happen and the task remains in the task list indefinitely due to the fact that the task cannot be cancelled. The Deltacloud tools currently does not support cancelling state-change-wait tasks because they are necessary to keep the cached data up-to-date (e.g. we need to know when an instance in PENDING becomes RUNNING and if the user has stopped an instance, we need to know when it is officially STOPPED or TERMINATED as this affects available actions, for example. The task continuously waits and refreshes the instance, waiting for a state change. If a user requests another action, the current wait-task will be cancelled and the new one will take it's place (e.g. one can STOP a PENDING instance that hasn't achieved RUNNING state yet). A bug has been opened against Deltacloud server: https://bugzilla.redhat.com/show_bug.cgi?id=64285 regarding the invalid action/state settings for the stopped EC2 instance. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 1 month

3
17
0 / 0

[JBoss JIRA] Created: (JBIDE-7181) Ability to search images

by Pete Muir (JIRA)

Ability to search images ------------------------ Key: JBIDE-7181 URL: https://jira.jboss.org/browse/JBIDE-7181 Project: Tools (JBoss Tools) Issue Type: Feature Request Components: deltacloud Affects Versions: 3.2.0.M2 Reporter: Pete Muir I have over 5000 images available to me on deltacloud, browsing them in a list that is not searchable/filterable makes this tool unusable -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

12 years, 1 month

4
10
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jbosstools-issues February 2012