December 2010 - jbosstools-issues

[JBoss JIRA] Created: (JBDS-1475) p2 repo generated during p2 product build doesn't contains binary features with jbdevstudio launcher for linux and windows platforms

by Denis Golovin (JIRA)

p2 repo generated during p2 product build doesn't contains binary features with jbdevstudio launcher for linux and windows platforms ------------------------------------------------------------------------------------------------------------------------------------ Key: JBDS-1475 URL: https://issues.jboss.org/browse/JBDS-1475 Project: Developer Studio (JBoss Developer Studio) Issue Type: Bug Components: Build, P2 Enabled Product Affects Versions: 4.0.0.CR1 Reporter: Denis Golovin Assignee: Denis Golovin Fix For: 4.0.0.CR1 p2 installer and p2 director installs com.jboss.jbds.all root IU from jbds update site without jbdevstudio launcher. This means PDE p2 build generates them from eclipse binary root features, but doesn't update p2repo meta data and artifacts. -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 3 months

1
2
0 / 0

[JBoss JIRA] Created: (JBDS-1477) CLONE - Releated to SOA-2719 - error dialog includes a typo

by Barry LaFond (JIRA)

CLONE - Releated to SOA-2719 - error dialog includes a typo ----------------------------------------------------------- Key: JBDS-1477 URL: https://issues.jboss.org/browse/JBDS-1477 Project: Developer Studio (JBoss Developer Studio) Issue Type: Bug Environment: Version: 4.0.0.Beta2 Build id: v201012070137R Build date: 201012070150 Reporter: Barry LaFond Assignee: Barry LaFond Priority: Minor Attachments: Screenshot.png See SOA-2720 -- 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-8015) ELResolverFactoryManager.getResolvers(ELResolverFactoryManager.java:54) failure

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-8015?page=com.atlassian.jira.plugin... ] Alexey Kazakov updated JBIDE-8015: ---------------------------------- Assignee: Alexey Kazakov Fix Version/s: 3.2.0.CR1 Affects Version/s: 3.2.0.CR1 Component/s: common > ELResolverFactoryManager.getResolvers(ELResolverFactoryManager.java:54) failure > ------------------------------------------------------------------------------- > > Key: JBIDE-8015 > URL: https://issues.jboss.org/browse/JBIDE-8015 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: common > Affects Versions: 3.2.0.CR1 > Reporter: Alexey Kazakov > Assignee: Alexey Kazakov > Fix For: 3.2.0.CR1 > > > Tests run: 40, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 14.633 sec <<< FAILURE! > testGetResolvers(org.jboss.tools.common.el.core.test.resolver.ELResolverFactoryManagerTest) Time elapsed: 0.002 sec <<< ERROR! > java.lang.NullPointerException > at $Proxy0.isAccessible(Unknown Source) > at org.jboss.tools.common.el.core.resolver.ELResolverFactoryManager.getResolvers(ELResolverFactoryManager.java:54) > at org.jboss.tools.common.el.core.test.resolver.ELResolverFactoryManagerTest.testGetResolvers(ELResolverFactoryManagerTest.java:22) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) -- 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-7938) org.hibernate.eclipse.console.test.ConsolePluginAllTests.testCriteriaCodeCompletion fails when run outside nightly build

by Nick Boldt (JIRA)

org.hibernate.eclipse.console.test.ConsolePluginAllTests.testCriteriaCodeCompletion fails when run outside nightly build ------------------------------------------------------------------------------------------------------------------------ Key: JBIDE-7938 URL: https://issues.jboss.org/browse/JBIDE-7938 Project: Tools (JBoss Tools) Issue Type: Sub-task Components: Hibernate Affects Versions: 3.2.0.CR1 Reporter: Nick Boldt Assignee: Max Andersen Not sure why this is failing: http://hudson.qa.jboss.com/hudson/view/DevStudio_Trunk/job/jbosstools-3.2... -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

15 years, 3 months

3
3
0 / 0

[JBoss JIRA] Updated: (JBIDE-8008) SeamProjectNewWizardTest.testJiraJbide1111 failure

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-8008?page=com.atlassian.jira.plugin... ] Alexey Kazakov updated JBIDE-8008: ---------------------------------- Assignee: Daniel Azarov Fix Version/s: 3.2.0.CR1 Affects Version/s: 3.2.0.CR1 Component/s: Seam > SeamProjectNewWizardTest.testJiraJbide1111 failure > -------------------------------------------------- > > Key: JBIDE-8008 > URL: https://issues.jboss.org/browse/JBIDE-8008 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: Seam > Affects Versions: 3.2.0.CR1 > Reporter: Alexey Kazakov > Assignee: Daniel Azarov > Fix For: 3.2.0.CR1 > > > junit.framework.AssertionFailedError: Finish button is disabled at first wizard page in spite of created JBoss AS Runtime, Server, DB Connection and Seam Runtime and valid project name. > at junit.framework.Assert.fail(Assert.java:47) > at junit.framework.Assert.assertTrue(Assert.java:20) > at org.jboss.tools.seam.ui.test.wizard.SeamProjectNewWizardTest.testJiraJbide1111(SeamProjectNewWizardTest.java:130) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) > at java.lang.reflect.Method.invoke(Method.java:597) > at junit.framework.TestCase.runTest(TestCase.java:168) > at junit.framework.TestCase.runBare(TestCase.java:134) > at junit.framework.TestResult$1.protect(TestResult.java:110) > at junit.framework.TestResult.runProtected(TestResult.java:128) > at junit.framework.TestResult.run(TestResult.java:113) > at junit.framework.TestCase.run(TestCase.java:124) > at junit.framework.TestSuite.runTest(TestSuite.java:232) > at junit.framework.TestSuite.run(TestSuite.java:227) > at junit.extensions.TestDecorator.basicRun(TestDecorator.java:24) > at junit.extensions.TestSetup$1.protect(TestSetup.java:23) > at junit.framework.TestResult.runProtected(TestResult.java:128) > at junit.extensions.TestSetup.run(TestSetup.java:27) > at junit.framework.TestSuite.runTest(TestSuite.java:232) > at junit.framework.TestSuite.run(TestSuite.java:227) > at junit.framework.TestSuite.runTest(TestSuite.java:232) > at junit.framework.TestSuite.run(TestSuite.java:227) > at org.junit.internal.runners.JUnit38ClassRunner.run(JUnit38ClassRunner.java:83) > at org.eclipse.jdt.internal.junit4.runner.JUnit4TestReference.run(JUnit4TestReference.java:49) > at org.eclipse.jdt.internal.junit.runner.TestExecution.run(TestExecution.java:38) > at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRunner.java:467) > at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.runTests(RemoteTestRunner.java:683) > at org.eclipse.jdt.internal.junit.runner.RemoteTestRunner.run(RemoteTestRunner.java:390) > at org.eclipse.pde.internal.junit.runtime.RemotePluginTestRunner.main(RemotePluginTestRunner.java:62) > at org.eclipse.pde.internal.junit.runtime.UITestApplication$1.run(UITestApplication.java:116) > at org.eclipse.swt.widgets.RunnableLock.run(RunnableLock.java:35) > at org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchronizer.java:134) > at org.eclipse.swt.widgets.Display.runAsyncMessages(Display.java:3527) > at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3174) > at org.eclipse.ui.internal.Workbench.runEventLoop(Workbench.java:2629) > at org.eclipse.ui.internal.Workbench.runUI(Workbench.java:2593) > at org.eclipse.ui.internal.Workbench.access$4(Workbench.java:2427) > at org.eclipse.ui.internal.Workbench$7.run(Workbench.java:670) > at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332) > at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:663) > at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:149) > at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:115) > at org.eclipse.pde.internal.junit.runtime.UITestApplication.start(UITestApplication.java:47) > at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:196) > at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:110) > at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:79) > at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:369) > at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:179) > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) > at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) > at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) > at java.lang.reflect.Method.invoke(Method.java:597) > at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:619) > at org.eclipse.equinox.launcher.Main.basicRun(Main.java:574) > at org.eclipse.equinox.launcher.Main.run(Main.java:1407) > at org.eclipse.equinox.launcher.Main.main(Main.java:1383) -- 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-1420) Hibernate Configuration Wizard: add "Test Connection" button and validate driver class, URL, user, pwd etc.

by Alexander Chabatar (JIRA)

Hibernate Configuration Wizard: add "Test Connection" button and validate driver class, URL, user, pwd etc. ----------------------------------------------------------------------------------------------------------- Key: JBIDE-1420 URL: http://jira.jboss.com/jira/browse/JBIDE-1420 Project: JBoss Tools Issue Type: Feature Request Components: Hibernate Affects Versions: LATER Reporter: Alexander Chabatar Assigned To: Alexander Chabatar Priority: Minor Fix For: LATER 1) add Test Connection button - should be helpful. 2) Finish button is always enabled. For example if Database dialect is selected but no driver class, no URL, user. Validation might show a warning. -- 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

15 years, 3 months

5
47
0 / 0

[JBoss JIRA] Commented: (JBIDE-8005) Deltacloud server doesn't report the key that was used to launch an instance

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-8005?page=com.atlassian.jira.plugin... ] Andre Dietisheim commented on JBIDE-8005: ----------------------------------------- this is a bug we cannot do anything about. I opened this issue to track the progress on the server. > Deltacloud server doesn't report the key that was used to launch an instance > ---------------------------------------------------------------------------- > > Key: JBIDE-8005 > URL: https://issues.jboss.org/browse/JBIDE-8005 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: deltacloud > Affects Versions: 3.2.0.CR1 > Environment: deltacloud-core 0.1.2 > Reporter: Andre Dietisheim > Assignee: Andre Dietisheim > Fix For: 3.2.x > > > The server does not report the key that was used to create an instance. > I request the following when I create the instance (the key is set: keyname=ad): > http://try.steamcannon.org/deltacloud//api/instances?image_id=ami-7d07ec1... > The server then responds without it (<keyname></keyname>): > <?xml version='1.0' encoding='utf-8' ?> > <instance href='http://try.steamcannon.org/deltacloud/api/instances/i-82a4b6ef' id='i-82a4b6ef'> > <name>ami-7d07ec14</name> > <owner_id>357159121505</owner_id> > <image href='http://try.steamcannon.org/deltacloud/api/images/ami-7d07ec14' id='ami-7d07ec14'></image> > <realm href='http://try.steamcannon.org/deltacloud/api/realms/us-east-1a' id='us-east-1a'></realm> > <state>PENDING</state> > <hardware_profile href='http://try.steamcannon.org/deltacloud/api/hardware_profiles/m1.small' id='m1.small'> > </hardware_profile> > <actions> > <link href='http://try.steamcannon.org/deltacloud/api/instances/i-82a4b6ef/stop' method='post' rel='stop' /> > </actions> > <launch_time>2010-12-25T14:42:22.000Z</launch_time> > <public_addresses> > </public_addresses> > <private_addresses> > </private_addresses> > <authentication type='key'> > <login> > <keyname></keyname> > </login> > </authentication> > </instance> > I created a bug in the deltacloud jira: https://issues.apache.org/jira/browse/DTACLOUD-11 -- 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-7997) Server View: Delete shortcut does not work on multiple selection

by Yahor Radtsevich (JIRA)

[ https://issues.jboss.org/browse/JBIDE-7997?page=com.atlassian.jira.plugin... ] Yahor Radtsevich updated JBIDE-7997: ------------------------------------ Attachment: screenshot-1.png > Server View: Delete shortcut does not work on multiple selection > ---------------------------------------------------------------- > > Key: JBIDE-7997 > URL: https://issues.jboss.org/browse/JBIDE-7997 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: JBossAS > Affects Versions: 3.2.0.Beta2 > Reporter: Yahor Radtsevich > Assignee: Rob Stryker > Attachments: screenshot-1.png > > > If one project is selected in the Server View, the project can be deleted using the Delete button. But if I want to delete several projects from a server, this shortcut does not work. See screenshot-1.png. -- 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-7995) New Hibernate Configuration File (cfg.xml) - page should be possible to scroll content if container wizard page to small

by Vitali Yemialyanchyk (JIRA)

[ https://issues.jboss.org/browse/JBIDE-7995?page=com.atlassian.jira.plugin... ] Vitali Yemialyanchyk updated JBIDE-7995: ---------------------------------------- Attachment: screenshot-1.jpg > New Hibernate Configuration File (cfg.xml) - page should be possible to scroll content if container wizard page to small > ------------------------------------------------------------------------------------------------------------------------ > > Key: JBIDE-7995 > URL: https://issues.jboss.org/browse/JBIDE-7995 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: Hibernate > Affects Versions: 3.2.0.Beta2 > Reporter: Vitali Yemialyanchyk > Assignee: Vitali Yemialyanchyk > Priority: Minor > Fix For: 3.2.0.CR1 > > Attachments: screenshot-1.jpg > > -- 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-7994) Configure->Add Seam Support does not add Seam Facet

by Yahor Radtsevich (JIRA)

[ https://issues.jboss.org/browse/JBIDE-7994?page=com.atlassian.jira.plugin... ] Yahor Radtsevich updated JBIDE-7994: ------------------------------------ Attachment: screenshot-1.png > Configure->Add Seam Support does not add Seam Facet > --------------------------------------------------- > > Key: JBIDE-7994 > URL: https://issues.jboss.org/browse/JBIDE-7994 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: Seam > Reporter: Yahor Radtsevich > Assignee: Alexey Kazakov > Attachments: screenshot-1.png > > > STEPS TO REPRODUCE: > 1. Create new JSF Project. > 2. Right-click on the project->Configure->Add Seam Support->OK. > 3. Open the project properties->Project Facets. > ACTUAL RESULT: > Seam Facet is not checked (screenshot-1.png). > EXPECTED RESULT: > Seam Facet is checked. -- 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