December 2010 - jbosstools-issues

[JBoss JIRA] Created: (JBIDE-7780) name of tree elements is handled by parent instead of element itself

by Andre Dietisheim (JIRA)

name of tree elements is handled by parent instead of element itself -------------------------------------------------------------------- Key: JBIDE-7780 URL: https://jira.jboss.org/browse/JBIDE-7780 Project: Tools (JBoss Tools) Issue Type: Feature Request Components: deltacloud Affects Versions: 3.2.0.Beta2 Reporter: Andre Dietisheim Assignee: Andre Dietisheim Fix For: 3.2.0.CR1 The current implementation of the CloudViewElement - the elements that are displayed in the cloud viewer tree - do not have their own implementation that returns their name. Their name is set by their parent. This is bad towards separation of concern and code readability/understandability. -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 3 months

2
2
0 / 0

[JBoss JIRA] Created: (JBIDE-7779) Cloud view: labels for instances are the image id

by Andre Dietisheim (JIRA)

Cloud view: labels for instances are the image id ------------------------------------------------- Key: JBIDE-7779 URL: https://jira.jboss.org/browse/JBIDE-7779 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.Beta2 the cloud viewer displays the name it gets for an instance. unfortunately Deltacloud reports the image id as name for an instance. We need a workaround for this since instances cannot be distinguised in the cloud view if they were launched from the same image -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 3 months

3
9
0 / 0

[JBoss JIRA] Created: (JBIDE-7774) NewConnectionWizard should remember hte last used deltacloud url

by Rob Stryker (JIRA)

NewConnectionWizard should remember hte last used deltacloud url ---------------------------------------------------------------- Key: JBIDE-7774 URL: https://jira.jboss.org/browse/JBIDE-7774 Project: Tools (JBoss Tools) Issue Type: Feature Request Components: deltacloud Affects Versions: 3.2.0.Beta2 Reporter: Rob Stryker Assignee: Rob Stryker Fix For: 3.2.0.CR1 title says it all -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 3 months

2
2
0 / 0

[JBoss JIRA] Created: (JBIDE-7769) launch instance wizard takes 10 seconds to load

by Rob Stryker (JIRA)

launch instance wizard takes 10 seconds to load ----------------------------------------------- Key: JBIDE-7769 URL: https://jira.jboss.org/browse/JBIDE-7769 Project: Tools (JBoss Tools) Issue Type: Bug Components: deltacloud Affects Versions: 3.2.0.Beta2 Reporter: Rob Stryker Assignee: Rob Stryker Fix For: 3.2.0.CR1 Opening the "Launch Instance" wizard takes 10 seconds because it executes two remote commands in the UI thread. First it fetches hte profiles, then it fetches hte realms. This should be delayed out as much as possible. Combos should be created with only one item saying "Loading..." and combo should be disabled. Fetching commands should be launched in another thread, and, upon completion, update the combo with either the proper items or a none-available string. Updates should be done in UI thread of course. -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 3 months

2
2
0 / 0

[JBoss JIRA] Created: (JBIDE-7874) ESB tests fail when run outside all-in-one collection of tests

by Nick Boldt (JIRA)

ESB tests fail when run outside all-in-one collection of tests -------------------------------------------------------------- Key: JBIDE-7874 URL: https://issues.jboss.org/browse/JBIDE-7874 Project: Tools (JBoss Tools) Issue Type: Bug Components: esb Affects Versions: 3.2.0.CR1 Reporter: Nick Boldt Assignee: Brian Fitzpatrick I've created a new ESB-only build job [0]. [0] http://hudson.qa.jboss.com/hudson/job/jbosstools-3.2_trunk.component--esb/ Unfortunately, it's not passing all its tests (unlike when run in the all-in-one job) [1]. [1] http://hudson.qa.jboss.com/hudson/view/DevStudio_Trunk/job/jbosstools-3.2... Here's a snippet of the errors [2]. [2] http://hudson.qa.jboss.com/hudson/job/jbosstools-3.2_trunk.component--esb... Running org.jboss.tools.esb.project.core.test.ESBProjectAllTests [ResourceUtils]:Target Import Location: /esbTestProject [ResourceUtils]:Full path to source: /qa/hudson_ws/workspace/jbosstools-3.2_trunk.component--esb/sources/tests/org.jboss.tools.esb.project.core.test/projects/esbTestProject/ [ResourceUtils]:Protocol: file [Fatal Error] :1:1: Premature end of file. [Fatal Error] :1:1: Premature end of file. [ResourceUtils]:Target Import Location: /esbTestProject_2 [ResourceUtils]:Full path to source: /qa/hudson_ws/workspace/jbosstools-3.2_trunk.component--esb/sources/tests/org.jboss.tools.esb.project.core.test/projects/esbTestProject_2/ [ResourceUtils]:Protocol: file [Fatal Error] :1:1: Premature end of file. Tests run: 7, Failures: 6, Errors: 0, Skipped: 0, Time elapsed: 12.279 sec <<< FAILURE! testUserCustomizedESBRuntime(org.jboss.tools.esb.project.core.test.ESBProjectDeploymentTest) Time elapsed: 8.246 sec <<< FAILURE! junit.framework.AssertionFailedError: unalbe to read User customized ESB runtime, jbossesb-rosetta.jar is not in classpath. expected:<true> but was:<false> at junit.framework.Assert.fail(Assert.java:47) at junit.framework.Assert.failNotEquals(Assert.java:283) at junit.framework.Assert.assertEquals(Assert.java:64) at junit.framework.Assert.assertEquals(Assert.java:143) at org.jboss.tools.esb.project.core.test.ESBProjectDeploymentTest.testUserCustomizedESBRuntime(ESBProjectDeploymentTest.java:233) testSOAP50Deployment(org.jboss.tools.esb.project.core.test.ESBProjectDeploymentTest) Time elapsed: 0.008 sec <<< FAILURE! junit.framework.AssertionFailedError: null at junit.framework.Assert.fail(Assert.java:47) at junit.framework.Assert.assertTrue(Assert.java:20) at junit.framework.Assert.assertTrue(Assert.java:27) at org.jboss.tools.esb.project.core.test.ESBProjectDeploymentTest.createServer(ESBProjectDeploymentTest.java:354) at org.jboss.tools.esb.project.core.test.ESBProjectDeploymentTest.testESBDeployment(ESBProjectDeploymentTest.java:266) at org.jboss.tools.esb.project.core.test.ESBProjectDeploymentTest.testSOAP50Deployment(ESBProjectDeploymentTest.java:238) testSOAP43Deployment(org.jboss.tools.esb.project.core.test.ESBProjectDeploymentTest) Time elapsed: 0.008 sec <<< FAILURE! junit.framework.AssertionFailedError: null at junit.framework.Assert.fail(Assert.java:47) at junit.framework.Assert.assertTrue(Assert.java:20) at junit.framework.Assert.assertTrue(Assert.java:27) at org.jboss.tools.esb.project.core.test.ESBProjectDeploymentTest.createServer(ESBProjectDeploymentTest.java:354) at org.jboss.tools.esb.project.core.test.ESBProjectDeploymentTest.testESBDeployment(ESBProjectDeploymentTest.java:266) at org.jboss.tools.esb.project.core.test.ESBProjectDeploymentTest.testSOAP43Deployment(ESBProjectDeploymentTest.java:243) testJBossServer50Deployment(org.jboss.tools.esb.project.core.test.ESBProjectDeploymentTest) Time elapsed: 0.008 sec <<< FAILURE! junit.framework.AssertionFailedError: null at junit.framework.Assert.fail(Assert.java:47) at junit.framework.Assert.assertTrue(Assert.java:20) at junit.framework.Assert.assertTrue(Assert.java:27) at org.jboss.tools.esb.project.core.test.ESBProjectDeploymentTest.createServer(ESBProjectDeploymentTest.java:354) at org.jboss.tools.esb.project.core.test.ESBProjectDeploymentTest.testESBDeployment(ESBProjectDeploymentTest.java:266) at org.jboss.tools.esb.project.core.test.ESBProjectDeploymentTest.testJBossServer50Deployment(ESBProjectDeploymentTest.java:248) testJbossServer51Deployment(org.jboss.tools.esb.project.core.test.ESBProjectDeploymentTest) Time elapsed: 0.017 sec <<< FAILURE! junit.framework.AssertionFailedError: null at junit.framework.Assert.fail(Assert.java:47) at junit.framework.Assert.assertTrue(Assert.java:20) at junit.framework.Assert.assertTrue(Assert.java:27) at org.jboss.tools.esb.project.core.test.ESBProjectDeploymentTest.createServer(ESBProjectDeploymentTest.java:354) at org.jboss.tools.esb.project.core.test.ESBProjectDeploymentTest.testESBDeployment(ESBProjectDeploymentTest.java:266) at org.jboss.tools.esb.project.core.test.ESBProjectDeploymentTest.testJbossServer51Deployment(ESBProjectDeploymentTest.java:253) testJbossServer42Deployment(org.jboss.tools.esb.project.core.test.ESBProjectDeploymentTest) Time elapsed: 0.012 sec <<< FAILURE! junit.framework.AssertionFailedError: null at junit.framework.Assert.fail(Assert.java:47) at junit.framework.Assert.assertTrue(Assert.java:20) at junit.framework.Assert.assertTrue(Assert.java:27) at org.jboss.tools.esb.project.core.test.ESBProjectDeploymentTest.createServer(ESBProjectDeploymentTest.java:354) at org.jboss.tools.esb.project.core.test.ESBProjectDeploymentTest.testESBDeployment(ESBProjectDeploymentTest.java:266) at org.jboss.tools.esb.project.core.test.ESBProjectDeploymentTest.testJbossServer42Deployment(ESBProjectDeploymentTest.java:258) Results : Failed tests: testUserCustomizedESBRuntime(org.jboss.tools.esb.project.core.test.ESBProjectDeploymentTest) testSOAP50Deployment(org.jboss.tools.esb.project.core.test.ESBProjectDeploymentTest) testSOAP43Deployment(org.jboss.tools.esb.project.core.test.ESBProjectDeploymentTest) testJBossServer50Deployment(org.jboss.tools.esb.project.core.test.ESBProjectDeploymentTest) testJbossServer51Deployment(org.jboss.tools.esb.project.core.test.ESBProjectDeploymentTest) testJbossServer42Deployment(org.jboss.tools.esb.project.core.test.ESBProjectDeploymentTest) Tests run: 7, Failures: 6, Errors: 0, Skipped: 0 [INFO] org.jboss.tools.esb.project.core .................. SUCCESS [51.084s] [INFO] org.jboss.tools.esb.core .......................... SUCCESS [4.492s] [INFO] org.jboss.tools.esb.ui ............................ SUCCESS [3.644s] [INFO] org.jboss.tools.esb.project.ui .................... SUCCESS [4.373s] [INFO] org.jboss.tools.esb.validator ..................... SUCCESS [6.520s] [INFO] org.jboss.tools.esb.feature ....................... SUCCESS [2.651s] [INFO] org.jboss.tools.esb.core.test ..................... SUCCESS [1:41.159s] [INFO] org.jboss.tools.esb.project.core.test ............. FAILURE [54.543s] [INFO] org.jboss.tools.esb.validator.test ................ SUCCESS [28.226s] [INFO] org.jboss.tools.esb.test.feature .................. SKIPPED [INFO] esb.features ...................................... SUCCESS [0.065s] [INFO] esb.plugins ....................................... SUCCESS [0.006s] [INFO] esb.tests ......................................... SUCCESS [0.006s] [INFO] esb.site .......................................... SUCCESS [4.788s] [INFO] esb.all ........................................... SUCCESS [0.005s] -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 3 months

3
4
0 / 0

[JBoss JIRA] Created: (JBIDE-7695) NPE when adding connection with invalid URL

by Libor Zoubek (JIRA)

NPE when adding connection with invalid URL ------------------------------------------- Key: JBIDE-7695 URL: https://jira.jboss.org/browse/JBIDE-7695 Project: Tools (JBoss Tools) Issue Type: Bug Components: deltacloud Affects Versions: 3.2.0.Beta2 Environment: 3.2.0.v20101119-1705-H261-Beta2 Reporter: Libor Zoubek Assignee: Andre Dietisheim If I enter total nonsense into url (like 'abc' '123') I get NPE - whis should be fixed. There is one little issue related to this one. If I enter 'http://something' dialog gets closed and is treated like valid but not reachable connection. This is fine But if I enter 'http:/something' behavior is same, which is wrong, There is a need to fix regex determining valid or invalid URL. -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 3 months

2
10
0 / 0

[JBoss JIRA] Created: (JBIDE-7735) Compile failed in org/hibernate/eclipse/console/test/CodeGenExternalProcessExecutionTest.java (at line 207):[-1, -1]

by Nick Boldt (JIRA)

Compile failed in org/hibernate/eclipse/console/test/CodeGenExternalProcessExecutionTest.java (at line 207):[-1,-1] ------------------------------------------------------------------------------------------------------------------- Key: JBIDE-7735 URL: https://jira.jboss.org/browse/JBIDE-7735 Project: Tools (JBoss Tools) Issue Type: Bug Components: Hibernate Affects Versions: 3.2.0.CR1 Reporter: Nick Boldt Assignee: Max Andersen Priority: Blocker [ERROR] Failed to execute goal org.sonatype.tycho:maven-osgi-compiler-plugin:0.10.0:compile (default-compile) on project org.hibernate.eclipse.console.test: Compilation failure: Compilation failure: [ERROR] /mnt/hudson_workspace/workspace/jbosstools-3.2_trunk.nightly/sources/hibernatetools/tests/org.hibernate.eclipse.console.test/src/org/hibernate/eclipse/console/test/CodeGenExternalProcessExecutionTest.java (at line 207):[-1,-1] [ERROR] public int compare(IResource o1, IResource o2) { [ERROR] ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ [ERROR] The method compare(IResource, IResource) of type CodeGenExternalProcessExecutionTest.ResComparator must override a superclass method [ERROR] -> [Help 1] -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 3 months

3
4
0 / 0

[JBoss JIRA] Created: (JBIDE-7836) Launch instance wizard: image text field is not in correct tab-order

by Andre Dietisheim (JIRA)

Launch instance wizard: image text field is not in correct tab-order -------------------------------------------------------------------- Key: JBIDE-7836 URL: https://jira.jboss.org/browse/JBIDE-7836 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.CR1 -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 3 months

2
3
0 / 0

[JBoss JIRA] Created: (JBIDE-7847) Instance view: cannot select instance

by Andre Dietisheim (JIRA)

Instance view: cannot select instance ------------------------------------- Key: JBIDE-7847 URL: https://jira.jboss.org/browse/JBIDE-7847 Project: Tools (JBoss Tools) Issue Type: Bug Components: deltacloud Affects Versions: 3.2.0.CR1 Reporter: Andre Dietisheim Assignee: Andre Dietisheim Fix For: 3.2.0.CR1 -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 3 months

2
2
0 / 0

[JBoss JIRA] Created: (JBIDE-7852) Cloud view: tree collapses and looses selection as soon as you change cloud in the image view

by Andre Dietisheim (JIRA)

Cloud view: tree collapses and looses selection as soon as you change cloud in the image view --------------------------------------------------------------------------------------------- Key: JBIDE-7852 URL: https://jira.jboss.org/browse/JBIDE-7852 Project: Tools (JBoss Tools) Issue Type: Bug Components: deltacloud Affects Versions: 3.2.0.CR1 Reporter: Andre Dietisheim Assignee: Andre Dietisheim Fix For: 3.2.0.CR1 -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 3 months

2
3
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