November 2008 - jbosstools-issues

[JBoss JIRA] Created: (JBDS-463) Diff markers in docs for beta1

by Svetlana mukhina (JIRA)

Diff markers in docs for beta1 ------------------------------ Key: JBDS-463 URL: https://jira.jboss.org/jira/browse/JBDS-463 Project: Developer Studio Issue Type: Task Components: documentation Affects Versions: 1.1.0.GA Reporter: Svetlana mukhina Assignee: OLga Chikvina Fix For: 2.0.0.beta1 Compare doc files from alpha to the current ones, diff markers should be add to the corresponding new and updated parts. -- 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

17 years, 4 months

4
10
0 / 0

[JBoss JIRA] Created: (JBDS-399) create diff files for all guides

by Svetlana mukhina (JIRA)

create diff files for all guides --------------------------------- Key: JBDS-399 URL: https://jira.jboss.org/jira/browse/JBDS-399 Project: Developer Studio Issue Type: Task Components: documentation Affects Versions: 1.1.0.GA Reporter: Svetlana mukhina Assignee: Svetlana mukhina Fix For: 2.0.0.alpha diff files are required between 2.1.x and 3.alpha with some markers with diffmk -- 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

17 years, 4 months

4
15
0 / 0

[JBoss JIRA] Created: (JBIDE-2841) Design of XML selection wizard page

by John Graham (JIRA)

Design of XML selection wizard page ----------------------------------- Key: JBIDE-2841 URL: https://jira.jboss.org/jira/browse/JBIDE-2841 Project: Tools (JBoss Tools) Issue Type: Bug Components: smooks Reporter: John Graham Assignee: Xue Peng Fix For: 3.0.0.beta1 The XML selection wizard page (image attached) needs a number of changes: 1. The XSD label should be changed to XML 2. The Browse buttons should be below the text box, and stacked vertically (not horizontally as they are now) 3. The "Load" button is problematic: Why does the user have to do this? Why not just load the XML when it selected? -- 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

17 years, 4 months

3
4
0 / 0

[JBoss JIRA] Created: (JBIDE-3194) There should be a classpath container page for changing the ESB runtime of ESB project

by Denny Xu (JIRA)

There should be a classpath container page for changing the ESB runtime of ESB project -------------------------------------------------------------------------------------- Key: JBIDE-3194 URL: https://jira.jboss.org/jira/browse/JBIDE-3194 Project: Tools (JBoss Tools) Issue Type: Feature Request Components: esb Affects Versions: 3.0.0.beta1 Environment: So far, when an ESB runtime is configured to a ESB project, there is a UI for the user to change the esb runtime, so need to add classpath container page for ESB runtime. Reporter: Denny Xu Assignee: Denny Xu Fix For: 3.0.0.cr1 -- 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

17 years, 4 months

2
3
0 / 0

[JBoss JIRA] Created: (JBIDE-3241) JBoss Tools has many different plugin providers, including some unset ones

by Nick Boldt (JIRA)

JBoss Tools has many different plugin providers, including some unset ones -------------------------------------------------------------------------- Key: JBIDE-3241 URL: https://jira.jboss.org/jira/browse/JBIDE-3241 Project: Tools (JBoss Tools) Issue Type: Bug Reporter: Nick Boldt Attachments: Screenshot-About Eclipse Platform Plug-ins .png There are many provider names for the various JBoss Tools plugins, including: (blank) BundleVendor Hibernate Team JBoss Drools JBoss Inc. JBoss, a division of Red Hat Jeff Mesnil PLUGIN_PROVIDER providerName Red Hat, Inc. I suggest these all need to be synched to be either "jboss.org", or "JBoss, a division of Red Hat" -- 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

17 years, 4 months

3
7
0 / 0

[JBoss JIRA] Created: (JBDS-490) get JBDS build to run locally and diagnose build failures

by Nick Boldt (JIRA)

get JBDS build to run locally and diagnose build failures --------------------------------------------------------- Key: JBDS-490 URL: https://jira.jboss.org/jira/browse/JBDS-490 Project: Developer Studio Issue Type: Bug Components: Build Reporter: Nick Boldt Priority: Critical Build has been failing since October 28. http://hudson.qa.jboss.com/hudson/view/DevStudio/job/devstudio-nightly/ -- 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

17 years, 4 months

1
4
0 / 0

[JBoss JIRA] Created: (JBIDE-3301) Finish button on Rule Wizard enabled before complete

by John Graham (JIRA)

Finish button on Rule Wizard enabled before complete ---------------------------------------------------- Key: JBIDE-3301 URL: https://jira.jboss.org/jira/browse/JBIDE-3301 Project: Tools (JBoss Tools) Issue Type: Bug Components: drools Affects Versions: 3.0.0.cr1 Environment: JBossTools-3.0.0.CR1-N200811261221-ALL-linux-gtk.zip Reporter: John Graham Priority: Minor Fix For: 3.0.0.cr1 The Finish button on the Rule Resource wizard is enabled before all the necessary information (target folder, rule file name, package name) is present. This button should be enabled/disabled depending on the presence/absence of these required fields. -- 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

17 years, 4 months

2
1
0 / 0

[JBoss JIRA] Created: (JBIDE-3300) Error when creating new rule resource

by John Graham (JIRA)

Error when creating new rule resource ------------------------------------- Key: JBIDE-3300 URL: https://jira.jboss.org/jira/browse/JBIDE-3300 Project: Tools (JBoss Tools) Issue Type: Bug Components: drools Affects Versions: 3.0.0.cr1 Environment: JBossTools-3.0.0.CR1-N200811261221-ALL-linux-gtk Reporter: John Graham Fix For: 3.0.0.cr1 New-->Drools-->Rule Resource Make sure there is no folder/project selected, type in a package name (but not file name), click Finish. --> Error message logged: null Error Wed Nov 26 15:45:28 GMT-05:00 2008 Unhandled event loop exception java.lang.NullPointerException at org.eclipse.ui.dialogs.WizardNewFileCreationPage.createNewFile(WizardNewFileCreationPage.java:347) at org.drools.eclipse.wizard.rule.NewRulePackagePage.finish(NewRulePackagePage.java:138) at org.drools.eclipse.wizard.rule.NewRulePackageWizard.performFinish(NewRulePackageWizard.java:37) at org.eclipse.jface.wizard.WizardDialog.finishPressed(WizardDialog.java:742) at org.eclipse.jface.wizard.WizardDialog.buttonPressed(WizardDialog.java:373) at org.eclipse.jface.dialogs.Dialog$2.widgetSelected(Dialog.java:624) at org.eclipse.swt.widgets.TypedListener.handleEvent(TypedListener.java:228) at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84) at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1158) at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3401) at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3033) at org.eclipse.jface.window.Window.runEventLoop(Window.java:825) at org.eclipse.jface.window.Window.open(Window.java:801) at org.eclipse.ui.internal.handlers.WizardHandler$New.executeHandler(WizardHandler.java:253) at org.eclipse.ui.internal.handlers.WizardHandler.execute(WizardHandler.java:273) at org.eclipse.ui.internal.handlers.HandlerProxy.execute(HandlerProxy.java:281) at org.eclipse.core.commands.Command.executeWithChecks(Command.java:476) at org.eclipse.core.commands.ParameterizedCommand.executeWithChecks(ParameterizedCommand.java:508) at org.eclipse.ui.internal.handlers.HandlerService.executeCommand(HandlerService.java:169) at org.eclipse.ui.internal.handlers.SlaveHandlerService.executeCommand(SlaveHandlerService.java:247) at org.eclipse.ui.internal.actions.CommandAction.runWithEvent(CommandAction.java:157) at org.eclipse.jface.action.ActionContributionItem.handleWidgetSelection(ActionContributionItem.java:583) at org.eclipse.jface.action.ActionContributionItem.access$2(ActionContributionItem.java:500) at org.eclipse.jface.action.ActionContributionItem$5.handleEvent(ActionContributionItem.java:411) at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84) at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1158) at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3401) at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3033) at org.eclipse.ui.internal.Workbench.runEventLoop(Workbench.java:2382) at org.eclipse.ui.internal.Workbench.runUI(Workbench.java:2346) at org.eclipse.ui.internal.Workbench.access$4(Workbench.java:2198) at org.eclipse.ui.internal.Workbench$5.run(Workbench.java:493) at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:288) at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:488) at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:149) at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:113) at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:193) 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:386) 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:549) at org.eclipse.equinox.launcher.Main.basicRun(Main.java:504) at org.eclipse.equinox.launcher.Main.run(Main.java:1236) -- 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

17 years, 4 months

2
1
0 / 0

[JBoss JIRA] Created: (JBIDE-3303) Consistency in name of Drools preference page

by John Graham (JIRA)

Consistency in name of Drools preference page --------------------------------------------- Key: JBIDE-3303 URL: https://jira.jboss.org/jira/browse/JBIDE-3303 Project: Tools (JBoss Tools) Issue Type: Bug Components: drools Affects Versions: 3.0.0.cr1 Environment: JBossTools-3.0.0.CR1-N200811261221-ALL-linux-gtk Reporter: John Graham Priority: Minor Fix For: 3.0.0.cr1 The Drools preference page appears in the preference tree list as "Drools Preferences" To be consistent with the rest of Eclipse, it should simply say "Drools" -- 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

17 years, 4 months

2
2
0 / 0

[JBoss JIRA] Created: (RHDS-221) Installer does not accept 64-Bit JVMs on Linux

by Holger Pirk (JIRA)

Installer does not accept 64-Bit JVMs on Linux ---------------------------------------------- Key: RHDS-221 URL: http://jira.jboss.com/jira/browse/RHDS-221 Project: Red Hat Developer Studio Issue Type: Bug Components: installer Affects Versions: 1.0.0.beta2 Environment: Linux x86_64, any jdk Reporter: Holger Pirk Priority: Minor Fix For: 1.0.0.CR1 When picking the JVM, the installer shows a "The chosen directory does not contain a Java VM"-message, when picking a 64-bit jdk. It checks for "selected-path/lib/i386/client/libjvm.so" to verify the path but it is "selected-path/lib/amd64/server/libjvm.so" for a 64-bit jdk. -- 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

17 years, 4 months

7
17
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 2008