November 2011 - jbosstools-issues

[JBoss JIRA] (JBIDE-10132) Errors running builder 'JAX-RS Builder' on project "myproject" when switching Git branch

by Ron Ratovsky (Created) (JIRA)

Errors running builder 'JAX-RS Builder' on project "myproject" when switching Git branch ---------------------------------------------------------------------------------------- Key: JBIDE-10132 URL: https://issues.jboss.org/browse/JBIDE-10132 Project: Tools (JBoss Tools) Issue Type: Bug Components: Webservices Affects Versions: 3.3.0.M4 Environment: Windows 7 64 bit Eclipse Indigo 3.7 SR1 64 bit Java 1.6.0_26 64 bit Reporter: Ron Ratovsky Assignee: Brian Fitzpatrick Attachments: error.log Using EGit, sometimes when switching branches, I get an error in the following form: Errors occurred during the build. Errors running builder 'JAX-RS Builder' on project 'sheker-sp-ws'. Resource '/sheker-sp-ws/src/main/java/com/sheker/ws/rest/MyClass.java' does not exist. Resource '/sheker-sp-ws/src/main/java/com/sheker/ws/rest/MyClass.java' does not exist. Errors running builder 'JAX-RS Builder' on project 'sheker-prod-ws'. Resource '/sheker-prod-ws/src/main/java/com/sheker/ws/rest/AnotherClass.java' does not exist. Resource '/sheker-prod-ws/src/main/java/com/sheker/ws/rest/AnotherClass.java' does not exist. -- 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

6
9
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, 2 months

9
45
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, 2 months

7
8
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, 2 months

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, 2 months

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, 2 months

7
10
0 / 0

[JBoss JIRA] (JBIDE-10033) Forge View shows up in odd location

by Burr Sutter (Created) (JIRA)

Forge View shows up in odd location ----------------------------------- Key: JBIDE-10033 URL: https://issues.jboss.org/browse/JBIDE-10033 Project: Tools (JBoss Tools) Issue Type: Bug Components: forge Environment: JBoss Tools 3.3.M4, Eclipse 3.7 Java EE 32-bit, 32-bit Java 1.6 JDK Reporter: Burr Sutter Attachments: Forge_JBossTools.png Forge is accessible via Ctrl-4 or Window-Show View-Other When requested it shows up on the right-side of my Eclipse window - tall & skinny, this might be because I had previously launched one of the quickstarts that displayed the cheatsheet. 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, 2 months

9
12
0 / 0

[JBoss JIRA] (JBIDE-10272) Automatically Start Forge When Eclipse Starts

by Koen Aers (Created) (JIRA)

Automatically Start Forge When Eclipse Starts --------------------------------------------- Key: JBIDE-10272 URL: https://issues.jboss.org/browse/JBIDE-10272 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 to be controlled by a preference setting. -- 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
2
0 / 0

[JBoss JIRA] (JBIDE-10099) Exception thrown when creating mavenized seam2 project

by Rastislav Wagner (Created) (JIRA)

Exception thrown when creating mavenized seam2 project ------------------------------------------------------ Key: JBIDE-10099 URL: https://issues.jboss.org/browse/JBIDE-10099 Project: Tools (JBoss Tools) Issue Type: Bug Components: maven, Seam 2 Affects Versions: 3.3.0.M4 Reporter: Rastislav Wagner Assignee: Fred Bricon Exception: java.lang.NullPointerException at org.maven.ide.eclipse.wtp.WTPProjectsUtil.isQualifiedAsWebFragment(WTPProjectsUtil.java:462) at org.maven.ide.eclipse.wtp.WebFragmentProjectConfigurator.configure(WebFragmentProjectConfigurator.java:59) at org.eclipse.m2e.core.project.configurator.AbstractLifecycleMapping.configure(AbstractLifecycleMapping.java:72) at org.eclipse.m2e.core.internal.project.ProjectConfigurationManager.updateProjectConfiguration(ProjectConfigurationManager.java:302) at org.eclipse.m2e.core.internal.project.ProjectConfigurationManager.updateProjectConfiguration(ProjectConfigurationManager.java:277) at org.eclipse.m2e.core.internal.project.ProjectConfigurationManager.updateProjectConfiguration(ProjectConfigurationManager.java:262) at org.jboss.tools.maven.core.MavenCoreActivator.updateMavenProjectConfiguration(MavenCoreActivator.java:331) at org.jboss.tools.maven.core.MavenCoreActivator.addMavenCapabilities(MavenCoreActivator.java:236) at org.jboss.tools.maven.core.MavenCoreActivator.createMavenProject(MavenCoreActivator.java:217) at org.jboss.tools.maven.core.MavenCoreActivator.createMavenProject(MavenCoreActivator.java:148) at org.jboss.tools.maven.seam.MavenSeamActivator.configureTestProject(MavenSeamActivator.java:325) at org.jboss.tools.maven.seam.MavenSeamActivator.configureSeamProject(MavenSeamActivator.java:164) at org.jboss.tools.maven.seam.internal.project.facet.MavenPostInstallListener.handleEvent(MavenPostInstallListener.java:62) at org.eclipse.wst.common.project.facet.core.events.internal.DelayedClassLoadingListener.handleEvent(DelayedClassLoadingListener.java:62) at org.eclipse.wst.common.project.facet.core.events.internal.ProjectListenerRegistry.notifyListeners(ProjectListenerRegistry.java:76) at org.eclipse.wst.common.project.facet.core.internal.FacetedProject.notifyListeners(FacetedProject.java:1327) at org.eclipse.wst.common.project.facet.core.internal.FacetedProject.modifyInternal(FacetedProject.java:454) at org.eclipse.wst.common.project.facet.core.internal.FacetedProject.mergeChangesInternal(FacetedProject.java:1181) at org.eclipse.wst.common.project.facet.core.internal.FacetedProject.access$2(FacetedProject.java:1117) at org.eclipse.wst.common.project.facet.core.internal.FacetedProject$5.run(FacetedProject.java:1099) at org.eclipse.core.internal.resources.Workspace.run(Workspace.java:2344) at org.eclipse.wst.common.project.facet.core.internal.FacetedProject.mergeChanges(FacetedProject.java:1109) at org.eclipse.wst.common.project.facet.core.internal.FacetedProjectWorkingCopy.commitChanges(FacetedProjectWorkingCopy.java:2020) at org.eclipse.wst.common.project.facet.ui.ModifyFacetedProjectWizard.performFinish(ModifyFacetedProjectWizard.java:400) at org.eclipse.wst.web.ui.internal.wizards.NewProjectDataModelFacetWizard.performFinish(NewProjectDataModelFacetWizard.java:282) at org.jboss.tools.seam.ui.wizard.SeamProjectWizard.performFinish(SeamProjectWizard.java:348) at org.eclipse.wst.common.project.facet.ui.ModifyFacetedProjectWizard$3.run(ModifyFacetedProjectWizard.java:331) at org.eclipse.core.internal.resources.Workspace.run(Workspace.java:2344) at org.eclipse.wst.common.project.facet.ui.ModifyFacetedProjectWizard$4.run(ModifyFacetedProjectWizard.java:345) at org.eclipse.jface.operation.ModalContext$ModalContextThread.run(ModalContext.java:121) -- 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

7
8
0 / 0

[JBoss JIRA] Created: (JBIDE-9581) Create vanilla Seam getting started project

by Nick Boldt (JIRA)

Create vanilla Seam getting started project ------------------------------------------- Key: JBIDE-9581 URL: https://issues.jboss.org/browse/JBIDE-9581 Project: Tools (JBoss Tools) Issue Type: Bug Components: JBossAS Affects Versions: 3.3.0.M3 Reporter: Nick Boldt Assignee: Rob Stryker Fix For: 3.3.0.M4 (From JBDS-1814 - see https://issues.jboss.org/browse/JBDS-1814?focusedCommentId=12623742&page=...) Concerning the Getting Started Guide content: * for Tools 3.3/JBDS 5, we will want to have a vanilla EE6 getting started project as well as the Seam one. Those project templates are spelled out in the JBDS 5.0 planning docs. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 2 months

6
9
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