November 2010 - jbosstools-issues

[JBoss JIRA] Created: (JBIDE-6684) adding a file thru JBDS adds a dot at the end of the file name (when the file is without extension)

by Denny Xu (JIRA)

adding a file thru JBDS adds a dot at the end of the file name (when the file is without extension) --------------------------------------------------------------------------------------------------- Key: JBIDE-6684 URL: https://jira.jboss.org/browse/JBIDE-6684 Project: Tools (JBoss Tools) Issue Type: Bug Components: drools Affects Versions: 3.2.0.M1 Reporter: Denny Xu Assignee: Denny Xu Fix For: 3.2.x -- 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

15 years, 2 months

2
3
0 / 0

[JBoss JIRA] Created: (JBIDE-6405) Failed to update action org.jboss.tools.common.xstudio.action.ModulesConfigurationActionDelegate

by Leonard Tyson (JIRA)

Failed to update action org.jboss.tools.common.xstudio.action.ModulesConfigurationActionDelegate ------------------------------------------------------------------------------------------------ Key: JBIDE-6405 URL: https://jira.jboss.org/browse/JBIDE-6405 Project: Tools (JBoss Tools) Issue Type: Bug Environment: eclipse.buildId= java.version=1.6.0_17 java.vendor=Sun Microsystems Inc. BootLoader constants: OS=win32, ARCH=x86, WS=win32, NL=en_US Framework arguments: -product org.eclipse.epp.package.jee.product Command-line arguments: -os win32 -ws win32 -arch x86 -product org.eclipse.epp.package.jee.product Reporter: Leonard Tyson Tried to open the web xml editor; received following error: java.lang.NullPointerException at org.jboss.tools.common.model.project.ProjectHome.getLocationFrom_project_File(ProjectHome.java:62) at org.jboss.tools.common.model.project.ProjectHome.getLocation(ProjectHome.java:53) at org.jboss.tools.common.model.project.ProjectHome.getLocation(ProjectHome.java:39) at org.jboss.tools.common.model.project.ModelNature.checkModelNature(ModelNature.java:237) at org.jboss.tools.common.model.util.EclipseResourceUtil.getModelNature(EclipseResourceUtil.java:245) at org.jboss.tools.common.model.ui.action.file.ModelResourceActionDelegate.getObjectByResource(ModelResourceActionDelegate.java:112) at org.jboss.tools.common.model.ui.action.file.ModelResourceActionDelegate.selectionChanged(ModelResourceActionDelegate.java:71) at org.eclipse.ui.internal.PluginAction.refreshEnablement(PluginAction.java:206) at org.eclipse.ui.internal.PluginAction.selectionChanged(PluginAction.java:277) at org.eclipse.ui.internal.ObjectActionContributor$1.run(ObjectActionContributor.java:157) at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42) at org.eclipse.ui.internal.ObjectActionContributor.contributeObjectActions(ObjectActionContributor.java:160) at org.eclipse.ui.internal.ObjectActionContributorManager.contributeObjectActions(ObjectActionContributorManager.java:97) at org.eclipse.ui.internal.PopupMenuExtender.addObjectActions(PopupMenuExtender.java:262) at org.eclipse.ui.internal.PopupMenuExtender.menuAboutToShow(PopupMenuExtender.java:339) at org.eclipse.jface.action.MenuManager.fireAboutToShow(MenuManager.java:338) at org.eclipse.jface.action.MenuManager.handleAboutToShow(MenuManager.java:469) at org.eclipse.jface.action.MenuManager.access$1(MenuManager.java:465) at org.eclipse.jface.action.MenuManager$2.menuShown(MenuManager.java:491) at org.eclipse.swt.widgets.TypedListener.handleEvent(TypedListener.java:235) at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84) at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1003) at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1027) at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1008) at org.eclipse.swt.widgets.Control.WM_INITMENUPOPUP(Control.java:4270) at org.eclipse.swt.widgets.Control.windowProc(Control.java:3974) at org.eclipse.swt.widgets.Canvas.windowProc(Canvas.java:342) at org.eclipse.swt.widgets.Decorations.windowProc(Decorations.java:1578) at org.eclipse.swt.widgets.Shell.windowProc(Shell.java:2010) at org.eclipse.swt.widgets.Display.windowProc(Display.java:4619) at org.eclipse.swt.internal.win32.OS.TrackPopupMenu(Native Method) at org.eclipse.swt.widgets.Menu._setVisible(Menu.java:254) at org.eclipse.swt.widgets.Display.runPopups(Display.java:3936) at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3497) at org.eclipse.ui.internal.Workbench.runEventLoop(Workbench.java:2405) -- 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

15 years, 2 months

4
6
0 / 0

[JBoss JIRA] Created: (JBIDE-6663) Exception in org.jboss.tools.modeshape.rest

by Snjezana Peco (JIRA)

Exception in org.jboss.tools.modeshape.rest ------------------------------------------- Key: JBIDE-6663 URL: https://jira.jboss.org/browse/JBIDE-6663 Project: Tools (JBoss Tools) Issue Type: Feature Request Components: modeshape Affects Versions: 3.2.x Reporter: Snjezana Peco Steps to reproduce: - create some project (it doesn't have to be a Java project) - delete it You will get the following exception: !ENTRY org.jboss.tools.modeshape.rest 4 0 2010-07-20 17:33:10.578 !MESSAGE Error obtaining the "published" property from the resource "L/test/.project" !STACK 1 org.eclipse.core.internal.resources.ResourceException: Resource '/test/.project' does not exist. at org.eclipse.core.internal.resources.Resource.checkExists(Resource.java:326) at org.eclipse.core.internal.resources.Resource.checkAccessible(Resource.java:200) at org.eclipse.core.internal.resources.Resource.checkAccessibleAndLocal(Resource.java:206) at org.eclipse.core.internal.resources.Resource.getPersistentProperty(Resource.java:1178) at org.jboss.tools.modeshape.rest.PublishedResourceHelper.getPublishedOnWorkspaces(PublishedResourceHelper.java:134) at org.jboss.tools.modeshape.rest.PublishedResourceHelper.isPublished(PublishedResourceHelper.java:193) at org.jboss.tools.modeshape.rest.views.ModeShapeContentProvider.decorate(ModeShapeContentProvider.java:147) at org.eclipse.ui.internal.decorators.LightweightDecoratorDefinition.decorate(LightweightDecoratorDefinition.java:263) at org.eclipse.ui.internal.decorators.LightweightDecoratorManager$LightweightRunnable.run(LightweightDecoratorManager.java:81) at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42) at org.eclipse.ui.internal.decorators.LightweightDecoratorManager.decorate(LightweightDecoratorManager.java:365) at org.eclipse.ui.internal.decorators.LightweightDecoratorManager.getDecorations(LightweightDecoratorManager.java:347) at org.eclipse.ui.internal.decorators.DecorationScheduler$1.ensureResultCached(DecorationScheduler.java:371) at org.eclipse.ui.internal.decorators.DecorationScheduler$1.run(DecorationScheduler.java:331) at org.eclipse.core.internal.jobs.Worker.run(Worker.java:54) !SUBENTRY 1 org.eclipse.core.resources 4 368 2010-07-20 17:33:10.578 !MESSAGE Resource '/test/.project' does not exist. ModeShapeContentProvider.decorate() should check if the ""element" resource exists. -- 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

15 years, 2 months

4
3
0 / 0

[JBoss JIRA] Created: (JBIDE-6233) Cannot compile org.jboss.tools.ui.bot.ext

by Nick Boldt (JIRA)

Cannot compile org.jboss.tools.ui.bot.ext ----------------------------------------- Key: JBIDE-6233 URL: https://jira.jboss.org/jira/browse/JBIDE-6233 Project: Tools (JBoss Tools) Issue Type: Bug Components: testing Affects Versions: 3.2.next Reporter: Nick Boldt Assignee: Dominik Pospisil Is this a coding error? A change in SWTBot? Something I need to help you fix? Does it work locally? [java] [javac] 211. ERROR in /home/hudson/hudson_workspace/workspace/jbosstools-nightly-3.2.next/jbds-build/eclipse/plugins/org.jboss.tools.ui.bot.ext/src/org/jboss/tools/ui/bot/ext/config/requirement/ClearWorkspace.java (at line 23) [java] [javac] SWTTestExt.bot.closeAllShells(); [java] [javac] ^^^^^^^^^^^^^^ [java] [javac] The method closeAllShells() is undefined for the type SWTBotExt [java] [javac] ---------- [java] [javac] 212. ERROR in /home/hudson/hudson_workspace/workspace/jbosstools-nightly-3.2.next/jbds-build/eclipse/plugins/org.jboss.tools.ui.bot.ext/src/org/jboss/tools/ui/bot/ext/config/requirement/ClearWorkspace.java (at line 24) [java] [javac] SWTTestExt.bot.closeAllEditors(); [java] [javac] ^^^^^^^^^^^^^^^ [java] [javac] The method closeAllEditors() is undefined for the type SWTBotExt http://hudson.qa.jboss.com/hudson/job/jbosstools-nightly-3.2.next/171/con... -- 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

15 years, 2 months

4
7
0 / 0

[JBoss JIRA] Created: (JBIDE-6299) OpenOn for reRender/for attributes of RichFaces components.

by Alexey Kazakov (JIRA)

OpenOn for reRender/for attributes of RichFaces components. ----------------------------------------------------------- Key: JBIDE-6299 URL: https://jira.jboss.org/browse/JBIDE-6299 Project: Tools (JBoss Tools) Issue Type: Feature Request Components: jsp/jsf/xml source editing Reporter: Alexey Kazakov Assignee: Daniel Azarov Fix For: 3.2.next We have code completion for component IDs for some richfaces attributes. Such as reRender, for, ... It would be useful if we supported not only code completion but OpenOne too. -- 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

15 years, 2 months

2
3
0 / 0

[JBoss JIRA] Created: (JBIDE-6231) New Seam Project Wizard should not deploy project automatically

by Dominik Pospisil (JIRA)

New Seam Project Wizard should not deploy project automatically --------------------------------------------------------------- Key: JBIDE-6231 URL: https://jira.jboss.org/jira/browse/JBIDE-6231 Project: Tools (JBoss Tools) Issue Type: Bug Components: Seam Affects Versions: 3.1.0.GA Reporter: Dominik Pospisil Assignee: Alexey Kazakov New Seam Project Wizard automatically deploys created project on target server. This feature is incosistent with DynamicWebProject wizard and should be considered to be removed. -- 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

15 years, 2 months

4
4
0 / 0

[JBoss JIRA] Created: (JBDS-1177) .metadata deploy issues

by Brice Ruth (JIRA)

.metadata deploy issues ----------------------- Key: JBDS-1177 URL: https://jira.jboss.org/jira/browse/JBDS-1177 Project: Developer Studio (JBoss Developer Studio) Issue Type: Bug Environment: WinXP SP2, jdk1.5.0_13, eclipse-jee-galileo-sr2, jboss_tools 3.1 final, m2e 0.10 Reporter: Brice Ruth >From #JbossTools on IRC: [11:07] <bruth> Another issue: apparently when I change from the default of deploying to .metadata to using the JBoss deploy/ folder, two things don't happen, (1) the files aren't cleaned out from .metadata and (2) the references that tell the JBoss instance to deploy things in the .metadata folder aren't removed, so JBoss starts, deploys from deploy/ then also tries to deploy from .metadata, generating all sorts of duplicate MBean errors -- 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

15 years, 2 months

5
7
0 / 0

[JBoss JIRA] Created: (JBIDE-6102) Server deployment status synchronization improvements

by Dominik Pospisil (JIRA)

Server deployment status synchronization improvements ----------------------------------------------------- Key: JBIDE-6102 URL: https://jira.jboss.org/jira/browse/JBIDE-6102 Project: Tools (JBoss Tools) Issue Type: Feature Request Components: JBossAS Reporter: Dominik Pospisil Assignee: Rob Stryker Fix For: 3.2.next I can see couple of ways how the project deployment status could be improved. 1) Currently, project deployment status could get easily out of sync. Once the JBT successfully initiates project deployment, it always assumes that the deployment was successful. JBT does not detect deployment failures and If something went wrong it gets out of sync. JBT should check deployment result. Also, when a project is manually undeployed / deployed from the server the change is not picked up by JBT. 2) The server view only displays deployments managed by JBT within current workspace. It would be nice if the user has an overview of projects/applications/resources deployed in different workspaces or externally. It would be really handy e.g. when a user often switches workspaces, deploy various project in different workspaces. It could prevent a user of being confused what actually is or is not deployed. -- 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

15 years, 2 months

3
3
0 / 0

[JBoss JIRA] Created: (JBIDE-6156) Exceptions in Seam Wizard under unusual circumstances

by Rob Stryker (JIRA)

Exceptions in Seam Wizard under unusual circumstances ----------------------------------------------------- Key: JBIDE-6156 URL: https://jira.jboss.org/jira/browse/JBIDE-6156 Project: Tools (JBoss Tools) Issue Type: Bug Components: Seam Affects Versions: 3.1.0.GA Reporter: Rob Stryker Assignee: Rob Stryker Fix For: 3.2.next, 3.6-Helios https://bugs.eclipse.org/bugs/show_bug.cgi?id=303317 Fixed this bug upstream but not sure if they'll accept the patch ;) I'm not sure if there's already a bug here for it but I'll dup it if there is. Build Identifier: I20090528-2000 Path for project must have only one segment. java.lang.IllegalArgumentException: Path for project must have only one segment. at org.eclipse.core.runtime.Assert.isLegal(Assert.java:63) at org.eclipse.core.internal.resources.WorkspaceRoot.getProject(WorkspaceRoot.java:181) at org.eclipse.wst.common.project.facet.core.internal.FacetedProjectWorkingCopy.getFacetedProject(FacetedProjectWorkingCopy.java:428) at org.eclipse.jst.common.project.facet.core.libprov.LibraryInstallDelegate.refresh(LibraryInstallDelegate.java:376) at org.eclipse.jst.common.project.facet.core.libprov.LibraryInstallDelegate$2.handleEvent(LibraryInstallDelegate.java:132) at org.eclipse.wst.common.project.facet.core.internal.FacetedProjectWorkingCopy.notifyListeners(FacetedProjectWorkingCopy.java:1690) at org.eclipse.wst.common.project.facet.core.internal.FacetedProjectWorkingCopy.resumeEventNotification(FacetedProjectWorkingCopy.java:1735) at org.eclipse.wst.common.project.facet.core.internal.FacetedProjectWorkingCopy.setTargetedRuntimes(FacetedProjectWorkingCopy.java:1237) at org.jboss.tools.seam.ui.wizard.SeamProjectWizard.setRuntimeAndDefaultFacets(SeamProjectWizard.java:222) at org.eclipse.wst.web.ui.internal.wizards.NewProjectDataModelFacetWizard$2.propertyChanged(NewProjectDataModelFacetWizard.java:215) at org.eclipse.wst.common.frameworks.internal.datamodel.DataModelImpl.notifyListeners(DataModelImpl.java:346) at org.eclipse.wst.common.frameworks.internal.datamodel.DataModelImpl.notifyPropertyChange(DataModelImpl.java:337) Reproducible: Always Steps to Reproduce: EXECUTE: New dynamic web project. EXECUTE: Input project name "test2/2" ASSERT: Warning, related to incorrect project name appears. EXECUTE: Change Server runtime FAILURE: Two same exceptions thrown in error log each time, when runtime changes. -- 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

15 years, 2 months

4
4
0 / 0

[JBoss JIRA] Created: (JBIDE-6215) 5 ASTestSuite tests failing for last 4 builds

by Nick Boldt (JIRA)

5 ASTestSuite tests failing for last 4 builds ----------------------------------------------- Key: JBIDE-6215 URL: https://jira.jboss.org/jira/browse/JBIDE-6215 Project: Tools (JBoss Tools) Issue Type: Bug Components: JBossAS Affects Versions: 3.2.next Reporter: Nick Boldt Assignee: Rob Stryker These tests have been failing for the last 4 builds: ASTestSuite.testEar5WithJBoss42 ASTestSuite.testEar5WithJBoss50 ASTestSuite.testEar5WithJBoss51 ASTestSuite.testMain ASTestSuite.testMain http://hudson.qa.jboss.com/hudson/job/jbosstools-nightly-3.2.next/lastCom... -- 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

15 years, 2 months

4
4
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 2010