February 2012 - jbosstools-issues

[JBoss JIRA] (JBIDE-10468) jsf enablement should not just look for dependency but also be enabled if /WEB-INF/faces-config.xml is there

by Max Rydahl Andersen (Created) (JIRA)

jsf enablement should not just look for dependency but also be enabled if /WEB-INF/faces-config.xml is there ------------------------------------------------------------------------------------------------------------ Key: JBIDE-10468 URL: https://issues.jboss.org/browse/JBIDE-10468 Project: Tools (JBoss Tools) Issue Type: Bug Components: JBossAS/Servers Reporter: Max Rydahl Andersen Assignee: Rob Stryker Priority: Blocker Fix For: 3.3.0.Beta1 >From Pete Muir: "JSF is included - there is a src/main/webapp/WEB-INF/faces-config.xml to activate JSF on JBoss AS 7. There is no compile time dependency, as most people start with JSF simply through the XHTML markup, and only when they need to do something advanced, actually start using the JSF Java API. I would suggest you trigger the JSF facet based on the presence of the above file or the web.xml stanza, not based on the POM. This is the way an app server does it, so you will see most fidelity this way." -- 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, 1 month

4
3
0 / 0

[JBoss JIRA] Created: (JBIDE-8701) VPE editor row lock on Visual/Source page

by Jiri Peterka (JIRA)

VPE editor row lock on Visual/Source page ----------------------------------------- Key: JBIDE-8701 URL: https://issues.jboss.org/browse/JBIDE-8701 Project: Tools (JBoss Tools) Issue Type: Feature Request Components: Visual Page Editor core Affects Versions: 3.2.0.Final Reporter: Jiri Peterka When Horizontal splitting with the Source Editor is set it would be nice to have switch to have row locking to keep the corresponding visual element on the same row as in source part and via versa. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 1 month

9
45
0 / 0

[JBoss JIRA] (JBIDE-10547) Wrong provider and plug-in name for org.jboss.tools.openshift.egit.core

by Lucia Jelinkova (Created) (JIRA)

Wrong provider and plug-in name for org.jboss.tools.openshift.egit.core ----------------------------------------------------------------------- Key: JBIDE-10547 URL: https://issues.jboss.org/browse/JBIDE-10547 Project: Tools (JBoss Tools) Issue Type: Bug Components: openshift Reporter: Lucia Jelinkova Assignee: Andre Dietisheim Priority: Minor Attachments: plugins.png See screenshot. -- 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, 1 month

6
5
0 / 0

[JBoss JIRA] (JBIDE-9997) VPE base editor sometimes crash a whole Eclipse with next error log

by Vitali Yemialyanchyk (Created) (JIRA)

VPE base editor sometimes crash a whole Eclipse with next error log ------------------------------------------------------------------- Key: JBIDE-9997 URL: https://issues.jboss.org/browse/JBIDE-9997 Project: Tools (JBoss Tools) Issue Type: Bug Components: Visual Page Editor core Affects Versions: 3.3.0.M4 Reporter: Vitali Yemialyanchyk Assignee: Yahor Radtsevich Priority: Critical Attachments: hs_err_pid9120.log take a look at attached stack trace. it is VPE only. there is a function in our application, which works intensively with attributes update. and we get this exception. so my opinion - in your code - VpeController.notifyChangedInUiThread is not safe implemented. exception which ErrorLog I provide - I can't reproduce on my rather slow machine, but other one can reproduce it on more quick computer. so my opinion - you should review this function - it is definitely unsafe - and you can get whole JBoss Studio crash with this problem - so you should make all efforts to fix this. -- 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, 1 month

7
8
0 / 0

[JBoss JIRA] (JBIDE-10431) browsersim should be sexy

by Max Rydahl Andersen (Created) (JIRA)

browsersim should be sexy ------------------------- Key: JBIDE-10431 URL: https://issues.jboss.org/browse/JBIDE-10431 Project: Tools (JBoss Tools) Issue Type: Bug Components: Visual Page Editor core Reporter: Max Rydahl Andersen Assignee: Yahor Radtsevich Priority: Critical Fix For: 3.3.0.Beta1 Lets add some gfx for the known models so it gets a more recognizable look. Xavier found http://www.smashingmagazine.com/2010/08/27/free-wireframing-kits-ui-desig... as a place where to get various frames for iphone,blackberry and various androids. -- 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, 1 month

5
11
0 / 0

[JBoss JIRA] (JBIDE-10728) NPE at DnD from JBoss Tools Palette into Outline of JBoss Tools HTML editor

by Viacheslav Kabanovich (JIRA)

Viacheslav Kabanovich created JBIDE-10728: --------------------------------------------- Summary: NPE at DnD from JBoss Tools Palette into Outline of JBoss Tools HTML editor Key: JBIDE-10728 URL: https://issues.jboss.org/browse/JBIDE-10728 Project: Tools (JBoss Tools) Issue Type: Bug Components: Visual Page Editor core Affects Versions: 3.3.0.M5 Reporter: Viacheslav Kabanovich Assignee: Yahor Radtsevich Fix For: 3.3.0.Beta1 EXECUTE: Open an xhtml file in JBoss Tools HTML editor. EXECUTE: Open Outline view and expand content of the file in it. EXECUTE: Open JBoss Tools Palette view, select some element in it, drag it and drop into Outline. FAILURE: NullPointerException (see npe.txt) Method DndUtil.getCurrentDragSession() returns null. It seems that simple check for null in getSupportedDataFlavors() solves the problem, and after that drop works properly. -- 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, 1 month

3
4
0 / 0

[JBoss JIRA] Created: (TOOLSDOC-221) JBDS50_0410: OSX Lion support documentation

by Isaac Rooskov (JIRA)

JBDS50_0410: OSX Lion support documentation ------------------------------------------- Key: TOOLSDOC-221 URL: https://issues.jboss.org/browse/TOOLSDOC-221 Project: Documentation for JBoss Tools and Developer Studio Issue Type: Task Security Level: Public (Everyone can see) Reporter: Isaac Rooskov Assignee: Isaac Rooskov Priority: Critical Fix For: 3.3.0.Final Tracking bug for documentation of the PRD requirement JBDS50_0410: OSX Lion support Current status: Committed Description: New documentation for OSX Lion support -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 1 month

1
1
0 / 0

[JBoss JIRA] Created: (JBDS-1686) com.jboss.jbds.all feature has no details in update view

by Nick Boldt (JIRA)

com.jboss.jbds.all feature has no details in update view -------------------------------------------------------- Key: JBDS-1686 URL: https://issues.jboss.org/browse/JBDS-1686 Project: Developer Studio (JBoss Developer Studio) Issue Type: Bug Components: installer Affects Versions: 4.1.0.CR2 Reporter: Nick Boldt Fix For: 4.1.0.CR2 Attachments: Screenshot.png As in JBDS-1675 (https://issues.jboss.org/browse/JBDS-1675?focusedCommentId=12609024&page=...), it's possible to install JBDS 4.1.0.CR2 into JBDS 4.0.0.GA. HOWEVER, as seen below, there are new details shown for the com.jboss.jbds.all feature. !Screenshot.png! -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 1 month

3
8
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] (JBIDE-10628) Discover new m2e connectors fails

by Jochen Buchholz (JIRA)

Jochen Buchholz created JBIDE-10628: --------------------------------------- Summary: Discover new m2e connectors fails Key: JBIDE-10628 URL: https://issues.jboss.org/browse/JBIDE-10628 Project: Tools (JBoss Tools) Issue Type: Bug Components: maven Affects Versions: 3.3.0.M5 Environment: Linux 3.1.6-gentoo #1 SMP x86_64 Intel(R) Core(TM) i7-2720QM CPU @ 2.20GHz GenuineIntel GNU/Linux IcedTea JDK 6.1.10.4 eclipse-jee-indigo-SR1-linux-gtk-x86_64.tar.gz Reporter: Jochen Buchholz Assignee: Fred Bricon I followed the guide on https://community.jboss.org/community/tools/blog/2011/12/23/jboss-tools-m... I installed eclipse-jee-indigo-SR1-linux-gtk-x86_64.tar.gz and update JBoss Tools from http://download.jboss.org/jbosstools/updates/development/indigo/ . I started with the Kitchensink example on the "Jboss Central". I opened the pom.xml and put the pointer over the plugin tag of the maven-compiler-plugin. An Error/Quickfix pop's up (snip snap): Plugin execution not covered by lifecycle configuration: org.apache.maven.plugins:maven-compiler-plugin:2.3.1:compile (execution: default-compile, phase: compile) 2 Quickfixes avaiulable: -Permanently mark goal bla bla bla -Discover new m2e connectors CoreException: Could not calculate build plan .... I choose "Discover new m2e connectors" and got an error: "Discovery completed without finding any extensions. Please check your network connection and try again." Very confusing Message, because my network connection is ok. It is impossible to discover m2e connectors under Preferences->maven-> Discovery->Open Catalog. The Catalog URL is http://download.eclipse.org/technology/m2e/discovery/directory.xml When I install m2e without Jbosstools Help->install new software m2e is able to discover connectors. -- 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, 1 month

5
18
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 February 2012