March 2011 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] Created: (JBIDE-7125) Usage Reporting description in N&N

by Max Andersen (JIRA)

Usage Reporting description in N&N ---------------------------------- Key: JBIDE-7125 URL: https://jira.jboss.org/browse/JBIDE-7125 Project: Tools (JBoss Tools) Issue Type: Sub-task Components: usage Reporter: Denis Golovin Assignee: Andre Dietisheim Fix For: 3.2.0.M2 -- 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

14 years, 1 month

3
5
0 / 0

[JBoss JIRA] Created: (JBDS-1508) Calculate properly font size when displaying version information on Splashscreen

by Vlado Pakan (JIRA)

Calculate properly font size when displaying version information on Splashscreen -------------------------------------------------------------------------------- Key: JBDS-1508 URL: https://issues.jboss.org/browse/JBDS-1508 Project: Developer Studio (JBoss Developer Studio) Issue Type: Feature Request Components: ui/branding Affects Versions: 4.0.0.CR1 Environment: JBDS 4.0.0.v20110116-1048-H515-CR1 Reporter: Vlado Pakan Priority: Minor Currently is font size of version text displayed on JBDS splash screen hardcoded. It's fine until version text is not too long. When complete build id is displayed ( when property -DSHOW_BUILDID_ON_STARTUP=true is specified when starting eclipse) than version text is too long and is displayed only partially. Logic how to calculate displayed text dimensions is already in source code so we need to find out maximal rectangle which can version text occupy and upon that dimensions properly calculate font size used for version text. -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 1 month

2
6
0 / 0

[JBoss JIRA] Created: (JBIDE-7361) Seam toolbar items are showing up in the Teiid toolbar

by Paul Nittel (JIRA)

Seam toolbar items are showing up in the Teiid toolbar ------------------------------------------------------ Key: JBIDE-7361 URL: https://jira.jboss.org/browse/JBIDE-7361 Project: Tools (JBoss Tools) Issue Type: Bug Components: Seam Affects Versions: LATER Environment: Fedora 12, JBDS 4.0.0 H52 with EDS Reporter: Paul Nittel Assignee: Alexey Kazakov Attachments: Screenshot-SeamTools.png I was inspecting the toolbar to test actions when I noticed that there was no "Find Model Object" button. I did find the "Open Seam Component" and "Open Spring Bean" buttons, but I'm in the Teiid perspective. Even with the Seam perspective closed, there toolbar contains these buttons. Screenshot will be attached. -- 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

14 years, 1 month

8
20
0 / 0

[JBoss JIRA] Created: (JBIDE-8394) Fetching inaccesible db can cause irresponsive ui and other issues

by Jiri Peterka (JIRA)

Fetching inaccesible db can cause irresponsive ui and other issues ------------------------------------------------------------------ Key: JBIDE-8394 URL: https://issues.jboss.org/browse/JBIDE-8394 Project: Tools (JBoss Tools) Issue Type: Bug Components: Hibernate Affects Versions: 3.2.0.CR2 (tentative) Environment: JBDS 4.0.0.CR3 H162, Linux 64 Reporter: Jiri Peterka Priority: Critical UI is not responsive when trying to connect stopped DB, some independent actions (like connection other running databases is blocked as well). When rebuild configuration is trigged, ui is completely frozen. Screencast http://www.screencast.com/t/p9uP59dNt Expected state: 1. Connection try should be shorter 2. Stopping fetching job should work 3. Independent databases should be always accesssible 4. IDE should not be freezing or forbidden action should be disabled -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 1 month

9
18
0 / 0

[JBoss JIRA] Created: (JBIDE-8464) Ensure that the Seam Project wizard opens the Seam perspective with the Web Development perspective as preferred

by Brian Fitzpatrick (JIRA)

Ensure that the Seam Project wizard opens the Seam perspective with the Web Development perspective as preferred ---------------------------------------------------------------------------------------------------------------- Key: JBIDE-8464 URL: https://issues.jboss.org/browse/JBIDE-8464 Project: Tools (JBoss Tools) Issue Type: Bug Components: Seam Affects Versions: 3.2.0.Final Reporter: Brian Fitzpatrick Assignee: Alexey Kazakov Fix For: 3.2.1, 3.3.0.M1 This task is an extension of JBDS-1554. When creating a new Seam Project, the Seam perspective is already set as the final perspective and opened by default. We also need to add the Web Development (perspective) to the "preferred" list. This can be done by updating the Seam Project wizard's "newWizard" extension point and setting the "preferredPerspectives" properties. In order to see these properties, you'll need to grab the Eclipse SDK and Eclipse Platform SDKs to be installed if they aren't already or they won't appear as options in the plugin editor. final perspective ID = Seam perspective (already done) preferred list = Seam perspective and Web Development perspective IDs -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 1 month

5
7
0 / 0

[JBoss JIRA] Created: (JBIDE-8563) Alternative being not being recognized as so.

by José Freitas (JIRA)

Alternative being not being recognized as so. --------------------------------------------- Key: JBIDE-8563 URL: https://issues.jboss.org/browse/JBIDE-8563 Project: Tools (JBoss Tools) Issue Type: Bug Components: cdi (jsr-299) Affects Versions: 3.2.0.Final Reporter: José Freitas Assignee: Alexey Kazakov Priority: Minor the problem occurs on booking example: https://github.com/seam/examples/ declaring on WEB-INF/beans.xml {code} <alternatives> <class>org.jboss.seam.examples.booking.bootstrap.ApplicationInitializer</class> </alternatives> {code} gives me the error check: {code} <class> element must specify the name of an alternative bean class [JSR-299 §5.1.1] {code} but the class is declared as an Alternative {code} @Alternative public class ApplicationInitializer{ ... {code} -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 1 month

6
12
0 / 0

[JBoss JIRA] Created: (JBDS-1099) Verify JBDS update site capacity for Eclipse bits

by Mark Yarborough (JIRA)

Verify JBDS update site capacity for Eclipse bits ------------------------------------------------- Key: JBDS-1099 URL: https://jira.jboss.org/jira/browse/JBDS-1099 Project: Developer Studio (JBoss Developer Studio) Issue Type: Task Components: Program Affects Versions: LATER Reporter: Mark Yarborough The JBDS team would like to ensure that the JBDS update site has capacity (disk and bandwidth) to support the addition of Eclipse bits. This will ensure that the version of eclipse that users pull is the same version that the JBDS release validated in product QE, and should make updating easier for customers. However, addition of these bits will potentially take more disk space and more download bandwidth, hence this "program" related task jira... -- 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

14 years, 1 month

3
6
0 / 0

[JBoss JIRA] Created: (JBIDE-7756) Add JUnit tests for portlets

by Snjezana Peco (JIRA)

Add JUnit tests for portlets ---------------------------- Key: JBIDE-7756 URL: https://jira.jboss.org/browse/JBIDE-7756 Project: Tools (JBoss Tools) Issue Type: Feature Request Components: Portal/GateIn Reporter: Snjezana Peco Assignee: Snjezana Peco -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 1 month

5
11
0 / 0

[JBoss JIRA] Created: (JBIDE-8182) "Could not initialize NSS" error entry in log

by Denis Golovin (JIRA)

"Could not initialize NSS" error entry in log --------------------------------------------- Key: JBIDE-8182 URL: https://issues.jboss.org/browse/JBIDE-8182 Project: Tools (JBoss Tools) Issue Type: Bug Components: Visual Page Editor core Affects Versions: 3.2.0.CR1 Reporter: Denis Golovin Assignee: Maxim Areshkau It doesn't affect Visual Editor, it is still working even right after exception java.security.ProviderException: Could not initialize NSS at sun.security.pkcs11.SunPKCS11.<init>(SunPKCS11.java:201) at sun.security.pkcs11.SunPKCS11.<init>(SunPKCS11.java:103) at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method) at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:57) at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45) at java.lang.reflect.Constructor.newInstance(Constructor.java:532) at sun.security.jca.ProviderConfig$3.run(ProviderConfig.java:262) at sun.security.jca.ProviderConfig$3.run(ProviderConfig.java:244) at java.security.AccessController.doPrivileged(Native Method) at sun.security.jca.ProviderConfig.doLoadProvider(ProviderConfig.java:244) at sun.security.jca.ProviderConfig.getProvider(ProviderConfig.java:224) at sun.security.jca.ProviderList.loadAll(ProviderList.java:281) at sun.security.jca.ProviderList.removeInvalid(ProviderList.java:298) at sun.security.jca.Providers.getFullProviderList(Providers.java:170) at java.security.Security.getProviders(Security.java:457) at org.eclipse.equinox.internal.security.ui.SecurityConfigurationSection.write(SecurityConfigurationSection.java:26) at org.eclipse.ui.internal.ConfigurationInfo.appendExtensions(ConfigurationInfo.java:107) at org.eclipse.ui.internal.ConfigurationInfo.getSystemSummary(ConfigurationInfo.java:73) at org.eclipse.ui.internal.about.AboutSystemPage$1.runInUIThread(AboutSystemPage.java:154) at org.eclipse.ui.progress.UIJob$1.run(UIJob.java:95) 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:3515) at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3164) 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.dialogs.AboutDialog$1.run(AboutDialog.java:126) at org.eclipse.swt.custom.BusyIndicator.showWhile(BusyIndicator.java:70) at org.eclipse.ui.internal.dialogs.AboutDialog.buttonPressed(AboutDialog.java:121) at org.eclipse.jface.dialogs.Dialog$2.widgetSelected(Dialog.java:624) at org.eclipse.swt.widgets.TypedListener.handleEvent(TypedListener.java:234) at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84) at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1258) at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3540) at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3161) 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.about.AboutHandler.execute(AboutHandler.java:32) at org.eclipse.ui.internal.handlers.HandlerProxy.execute(HandlerProxy.java:293) 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:241) at org.eclipse.ui.internal.actions.CommandAction.runWithEvent(CommandAction.java:157) at org.eclipse.jface.action.ActionContributionItem.handleWidgetSelection(ActionContributionItem.java:584) at org.eclipse.jface.action.ActionContributionItem.access$2(ActionContributionItem.java:501) 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:1258) at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3540) at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3161) at org.eclipse.ui.internal.Workbench.runEventLoop(Workbench.java:2640) at org.eclipse.ui.internal.Workbench.runUI(Workbench.java:2604) at org.eclipse.ui.internal.Workbench.access$4(Workbench.java:2438) at org.eclipse.ui.internal.Workbench$7.run(Workbench.java:671) at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332) at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:664) at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:149) at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:115) 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:57) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:616) 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) Caused by: java.io.IOException: /home/eskimo/jbdevstudio-h84-CR1/studio/plugins/org.mozilla.xulrunner.gtk.linux.x86_1.9.1.2/xulrunner/libnssutil3.so: version `NSSUTIL_3.12.5' not found (required by /usr/lib/libnss3.so) at sun.security.pkcs11.Secmod.nssLoadLibrary(Native Method) at sun.security.pkcs11.Secmod.initialize(Secmod.java:203) at sun.security.pkcs11.SunPKCS11.<init>(SunPKCS11.java:197) ... 70 more -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 1 month

7
10
0 / 0

[JBoss JIRA] Created: (JBIDE-7997) Server View: Delete shortcut does not work on multiple selection

by Yahor Radtsevich (JIRA)

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

14 years, 1 month

5
15
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 March 2011