November 2011 - jbosstools-issues

[JBoss JIRA] Created: (JBIDE-9559) Schema Generation From DDlWizard doesn't reflect changes in the classes

by Elhanan Maayan (JIRA)

Schema Generation From DDlWizard doesn't reflect changes in the classes ----------------------------------------------------------------------- Key: JBIDE-9559 URL: https://issues.jboss.org/browse/JBIDE-9559 Project: Tools (JBoss Tools) Issue Type: Bug Components: Hibernate Affects Versions: 3.3.x Reporter: Elhanan Maayan Assignee: Max Rydahl Andersen when generating a schema from generate tables from entities, the file is only generated once,. if i change anything in the classes (like table name,columns etc..) attempting to generate again, will not change the file only restarting eclipse will do so. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 2 months

12
21
0 / 0

[JBoss JIRA] Created: (JBDS-1733) JBDS50_0060: [COMMIT] (Dev) Forge

by mark yarborough (JIRA)

JBDS50_0060: [COMMIT] (Dev) Forge --------------------------------- Key: JBDS-1733 URL: https://issues.jboss.org/browse/JBDS-1733 Project: Developer Studio (JBoss Developer Studio) Issue Type: Feature Request Components: Requirements Reporter: mark yarborough -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 2 months

6
7
0 / 0

[JBoss JIRA] Created: (JBIDE-9709) osgi deployments fails

by Max Rydahl Andersen (JIRA)

osgi deployments fails ---------------------- Key: JBIDE-9709 URL: https://issues.jboss.org/browse/JBIDE-9709 Project: Tools (JBoss Tools) Issue Type: Feature Request Components: JBossAS/Servers Affects Versions: 3.3.0.M3 Reporter: Vlado Pakan Assignee: Rob Stryker Fix For: 3.3.0.M4 while testing JBIDE-9206: Deployment works for war deployments, but fails for OSGI deployments temporary dir gets created This is what server says: 16:40:06,375 INFO [org.jboss.as.server.deployment] (MSC service thread 1-4) Starting deployment of "testnull" 16:40:06,375 ERROR [org.jboss.msc.service.fail] (MSC service thread 1-4) MSC00001: Failed to start service jboss.deployment.unit.testnull.STRUCTURE: org.jboss.msc.service.StartException in service jboss.deployment.unit.testnull.STRUCTURE: Failed to process phase STRUCTURE of deployment "testnull" at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:121) at org.jboss.msc.service.ServiceControllerImpl$StartTask.run(ServiceControllerImpl.java:1765) at org.jboss.msc.service.ServiceControllerImpl$ClearTCCLTask.run(ServiceControllerImpl.java:2291) at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:886) [:1.6.0_27] at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:908) [:1.6.0_27] at java.lang.Thread.run(Thread.java:662) [:1.6.0_27] Caused by: org.jboss.as.server.deployment.DeploymentUnitProcessingException: Failed to mount deployment content at org.jboss.as.server.deployment.module.DeploymentRootMountProcessor.deploy(DeploymentRootMountProcessor.java:82) at org.jboss.as.server.deployment.DeploymentUnitPhaseService.start(DeploymentUnitPhaseService.java:115) ... 5 more Caused by: java.io.IOException: Could not create directory for original name 'testnull' after 10 attempts at org.jboss.vfs.TempFileProvider.createTempDir(TempFileProvider.java:103) at org.jboss.vfs.VFS.mountZip(VFS.java:406) at org.jboss.vfs.VFS.mountZip(VFS.java:434) at org.jboss.as.server.deployment.repository.impl.ServerDeploymentRepositoryImpl.mountDeploymentContent(ServerDeploymentRepositoryImpl.java:75) at org.jboss.as.server.deployment.module.DeploymentRootMountProcessor.deploy(DeploymentRootMountProcessor.java:78) ... 6 more 16:40:06,377 INFO [org.jboss.as.server.controller] (DeploymentScanner-threads - 1) Deployment of "testnull" was rolled back with failure message {"Failed services" => {"jboss.deployment.unit.testnull.STRUCTURE" => "org.jboss.msc.service.StartException in service jboss.deployment.unit.testnull.STRUCTURE: Failed to process phase STRUCTURE of deployment \"testnull\""}} 16:40:06,378 INFO [org.jboss.as.server.deployment] (MSC service thread 1-1) Stopped deployment testnull in 0ms 16:40:06,379 ERROR [org.jboss.as.deployment] (DeploymentScanner-threads - 2) {"Composite operation failed and was rolled back. Steps that failed:" => {"Operation step-2" => {"Failed services" => {"jboss.deployment.unit.testnull.STRUCTURE" => "org.jboss.msc.service.StartException in service jboss.deployment.unit.testnull.STRUCTURE: Failed to process phase STRUCTURE of deployment \"testnull\""}}}} -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 2 months

4
4
0 / 0

[JBoss JIRA] (JBIDE-10191) System properties are ignored

by Andre Dietisheim (Created) (JIRA)

System properties are ignored ----------------------------- Key: JBIDE-10191 URL: https://issues.jboss.org/browse/JBIDE-10191 Project: Tools (JBoss Tools) Issue Type: Bug Components: openshift Affects Versions: 3.3.0.Beta1 Reporter: Andre Dietisheim Assignee: Andre Dietisheim Fix For: 3.3.0.Beta1 -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 2 months

4
3
0 / 0

[JBoss JIRA] (JBIDE-10193) Tests start second workbench window

by Viacheslav Kabanovich (Created) (JIRA)

Tests start second workbench window ----------------------------------- Key: JBIDE-10193 URL: https://issues.jboss.org/browse/JBIDE-10193 Project: Tools (JBoss Tools) Issue Type: Bug Components: CDI, JSF, Seam 2 Affects Versions: 3.3.0.M4 Reporter: Viacheslav Kabanovich Assignee: Viacheslav Kabanovich Fix For: 3.3.0.Beta1 Class JBossPerspectiveTest opens perspective by method IWorkbenchWindow.openPage() that creates new window. It is better to call IWorkbench.showPerspective() that displays perspective in current window. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 2 months

4
3
0 / 0

[JBoss JIRA] (JBIDE-10093) Provide capability to save password

by Pavol Srna (Created) (JIRA)

Provide capability to save password ------------------------------------ Key: JBIDE-10093 URL: https://issues.jboss.org/browse/JBIDE-10093 Project: Tools (JBoss Tools) Issue Type: Feature Request Components: openshift Affects Versions: 3.3.0.M4 Reporter: Pavol Srna Assignee: Andre Dietisheim Fix For: 3.3.0.Beta1 -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 2 months

8
7
0 / 0

[JBoss JIRA] (JBIDE-10271) Make the Forge "cd" Command Aware of the Eclipse Workspace

by Koen Aers (Created) (JIRA)

Make the Forge "cd" Command Aware of the Eclipse Workspace ---------------------------------------------------------- Key: JBIDE-10271 URL: https://issues.jboss.org/browse/JBIDE-10271 Project: Tools (JBoss Tools) Issue Type: Feature Request Components: forge Reporter: Koen Aers Assignee: Koen Aers Fix For: 3.3.0.Beta1 Like the special character '~' in Forge represents the user's home folder, another special character ('#'?) can indicate the root of the workspace. Thus it would be possible to issue "cd #" to navigate to the workspace root. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 2 months

3
6
0 / 0

[JBoss JIRA] (JBIDE-10270) Link Workspace Selection to Forge Runtime

by Koen Aers (Created) (JIRA)

Link Workspace Selection to Forge Runtime ----------------------------------------- Key: JBIDE-10270 URL: https://issues.jboss.org/browse/JBIDE-10270 Project: Tools (JBoss Tools) Issue Type: Feature Request Components: forge Reporter: Koen Aers Assignee: Koen Aers Fix For: 3.3.0.Beta1 This feature needs the possibility to be enabled/disabled as a preference. When it is enabled and Forge is running, the current selection will automatically be picked up by the Forge runtime. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 2 months

3
4
0 / 0

[JBoss JIRA] (JBIDE-10264) Wizard-ify the project examples

by Fred Bricon (Created) (JIRA)

Wizard-ify the project examples ------------------------------- Key: JBIDE-10264 URL: https://issues.jboss.org/browse/JBIDE-10264 Project: Tools (JBoss Tools) Issue Type: Feature Request Components: project-examples Affects Versions: 3.3.0.M4 Reporter: Fred Bricon Assignee: Snjezana Peco Fix For: 3.3.0.Beta1 In the wake of JBIDE-9776 and JBIDE-10140, it turns out that, in order for us to contribute 5 new wizards to the "New " menu under the Jboss perspective and in the "New project" section of JBoss central, "project examples" based projects should be created via a Wizard implementation from the get go. Current project examples workflow involves : - displaying a form dialog : to display missing runtimes and let the user install/download the required runtimes - launching a workspace job, which in turn : * downloads the example * does the actual project import (launches a wizard for maven archetypes) * resolve quickfixes Ideally, all these steps would be part of a single wizard, spanning one to 3 pages (depending on the complexity/requirements of the examples). Everything contributed by the form dialog would be replaced by a wizard page, which would bring consistency to the UI. I'm aware this is not a simple task to refactor the existing workflow to such an infrastructure but ultimately, that would allow us to easily contribute new project wizards to the IDE in a standard way. Current target is 3.3.0.Beta1. Snjeza, WDYT? -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 2 months

9
34
0 / 0

[JBoss JIRA] Created: (JBIDE-9547) JPA: Can't remove @NamedNativeQuery#resultClass field from ui

by Dmitry Geraskov (JIRA)

JPA: Can't remove @NamedNativeQuery#resultClass field from ui -------------------------------------------------------------- Key: JBIDE-9547 URL: https://issues.jboss.org/browse/JBIDE-9547 Project: Tools (JBoss Tools) Issue Type: Bug Components: Hibernate Affects Versions: 3.3.0.M2 Reporter: Dmitry Geraskov Assignee: Dmitry Geraskov Fix For: 3.3.0.M3 -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 2 months

4
8
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 November 2011