March 2012 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBDS-2053) Welcome Screen has layout problems in "stand by" mode

by Denis Golovin (JIRA)

Denis Golovin created JBDS-2053: ----------------------------------- Summary: Welcome Screen has layout problems in "stand by" mode Key: JBDS-2053 URL: https://issues.jboss.org/browse/JBDS-2053 Project: Developer Studio (JBoss Developer Studio) Issue Type: Bug Security Level: Public (Everyone can see) Components: Welcome Affects Versions: 5.0.0.Beta1 Environment: Windows & x86_64 Reporter: Denis Golovin Assignee: Victor Rubezhny Priority: Optional !Screenshot151.png! -- 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

13 years, 11 months

4
16
0 / 0

[JBoss JIRA] (JBIDE-9867) Deadlock in Libs.updatePaths() occures while running org.jboss.tools.jsf.test.JsfAllTests

by Viacheslav Kabanovich (Created) (JIRA)

Deadlock in Libs.updatePaths() occures while running org.jboss.tools.jsf.test.JsfAllTests ----------------------------------------------------------------------------------------- Key: JBIDE-9867 URL: https://issues.jboss.org/browse/JBIDE-9867 Project: Tools (JBoss Tools) Issue Type: Bug Components: common/jst/core Affects Versions: 3.3.0.M3 Reporter: Viacheslav Kabanovich Assignee: Viacheslav Kabanovich Fix For: 3.3.0.M4 Synchronized methods Libs.updatePaths() requests for resolved class path of the current project. That initializes a lot of features in Eclipse that may start jobs in new threads. As a result two threads may be invoking Libs.updatePaths(), the first one waiting for the other, while Eclipses rules may demand the other to yield to the first. The request for class path should be moved out of synchronization block. -- 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

13 years, 11 months

4
4
0 / 0

[JBoss JIRA] (JBIDE-11292) Maven Import/Archetype (JBoss Central) usage sometimes invalidates previously imported projects

by Burr Sutter (JIRA)

Burr Sutter created JBIDE-11292: ----------------------------------- Summary: Maven Import/Archetype (JBoss Central) usage sometimes invalidates previously imported projects Key: JBIDE-11292 URL: https://issues.jboss.org/browse/JBIDE-11292 Project: Tools (JBoss Tools) Issue Type: Bug Components: maven Reporter: Burr Sutter Assignee: Fred Bricon "Project configuration is not up-to-date with pom.xml. Run project configuration update" I have noticed, with beta1e and perhaps beta1d, that when I load up my workspace with projects - created via the archetypes, quickstarts and even File Import - perhaps, after a restart of the IDE - the next time I import (file-import or archetype) another maven project, the previous projects throw up the project configuration error msg. -- 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

13 years, 11 months

3
6
0 / 0

[JBoss JIRA] (JBIDE-11118) No code completion for entities in HB4.0

by Jiri Peterka (JIRA)

Jiri Peterka created JBIDE-11118: ------------------------------------ Summary: No code completion for entities in HB4.0 Key: JBIDE-11118 URL: https://issues.jboss.org/browse/JBIDE-11118 Project: Tools (JBoss Tools) Issue Type: Bug Components: hibernate Affects Versions: 3.3.0.Beta1 Environment: jbosstools-3.3_stable_branch.aggregate-Update-2012-02-24_23-15-15-H93, L64 Reporter: Jiri Peterka Assignee: Dmitry Geraskov Fix For: 3.3.0.CR1 Have Hibernate 4.0 HQL Editor for "from" CC works for class name start, like "Cu" it doesn't work. Just "No HQL completions available" message For Hibernate 3.5 HQL Editor it works -- 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

13 years, 11 months

2
5
0 / 0

[JBoss JIRA] (JBIDE-11378) NPE while editing package-info.java

by Jiri Peterka (JIRA)

Jiri Peterka created JBIDE-11378: ------------------------------------ Summary: NPE while editing package-info.java Key: JBIDE-11378 URL: https://issues.jboss.org/browse/JBIDE-11378 Project: Tools (JBoss Tools) Issue Type: Bug Components: hibernate Affects Versions: 3.3.0.Beta1 Environment: JBDS 5.0.0.beta1 #105, L64 Reporter: Jiri Peterka Assignee: Dmitry Geraskov Fix For: 3.3.0.Beta2 Attachments: internal-hb-error.png java.lang.NullPointerException at org.jboss.tools.hibernate.jpt.core.internal.HibernateJpaProject$4.transform(HibernateJpaProject.java:134) at org.jboss.tools.hibernate.jpt.core.internal.HibernateJpaProject$4.transform(HibernateJpaProject.java:1) at org.eclipse.jpt.common.utility.internal.iterables.TransformationIterable$DefaultTransformer.transform(TransformationIterable.java:87) at org.eclipse.jpt.common.utility.internal.iterators.TransformationIterator.transform(TransformationIterator.java:95) at org.eclipse.jpt.common.utility.internal.iterators.TransformationIterator.next(TransformationIterator.java:83) at org.eclipse.jpt.common.utility.internal.iterators.FilteringIterator.loadNext(FilteringIterator.java:119) at org.eclipse.jpt.common.utility.internal.iterators.FilteringIterator.<init>(FilteringIterator.java:87) at org.eclipse.jpt.common.utility.internal.iterables.FilteringIterable.iterator(FilteringIterable.java:66) at org.eclipse.jpt.common.utility.internal.iterables.CompositeIterable$1.transform(CompositeIterable.java:81) at org.eclipse.jpt.common.utility.internal.iterables.CompositeIterable$1.transform(CompositeIterable.java:1) at org.eclipse.jpt.common.utility.internal.iterators.TransformationIterator.next(TransformationIterator.java:83) at org.eclipse.jpt.common.utility.internal.iterators.CompositeIterator.loadCurrentIterator(CompositeIterator.java:150) at org.eclipse.jpt.common.utility.internal.iterators.CompositeIterator.hasNext(CompositeIterator.java:113) at org.eclipse.jpt.jpa.core.internal.context.ContextContainerTools.sync(ContextContainerTools.java:101) at org.eclipse.jpt.jpa.core.internal.context.ContextContainerTools.update(ContextContainerTools.java:88) at org.eclipse.jpt.jpa.core.internal.context.persistence.AbstractPersistenceUnit.updateImpliedClassRefs(AbstractPersistenceUnit.java:961) at org.eclipse.jpt.jpa.core.internal.context.persistence.AbstractPersistenceUnit.update(AbstractPersistenceUnit.java:252) at org.jboss.tools.hibernate.jpt.core.internal.context.HibernatePersistenceUnit.update(HibernatePersistenceUnit.java:96) at org.eclipse.jpt.jpa.core.internal.context.AbstractJpaContextNode.updateNodes(AbstractJpaContextNode.java:55) at org.eclipse.jpt.jpa.core.internal.jpa1.context.persistence.GenericPersistence.update(GenericPersistence.java:69) at org.eclipse.jpt.jpa.core.internal.jpa1.context.persistence.GenericPersistenceXml.update(GenericPersistenceXml.java:113) at org.eclipse.jpt.jpa.core.internal.jpa1.context.GenericRootContextNode.syncPersistenceXml(GenericRootContextNode.java:123) at org.eclipse.jpt.jpa.core.internal.jpa1.context.GenericRootContextNode.updatePersistenceXml(GenericRootContextNode.java:157) at org.eclipse.jpt.jpa.core.internal.jpa1.context.GenericRootContextNode.update(GenericRootContextNode.java:73) at org.eclipse.jpt.jpa.core.internal.AbstractJpaProject.update(AbstractJpaProject.java:1905) at org.eclipse.jpt.jpa.core.GenericJpaProjectManager$2.execute(GenericJpaProjectManager.java:452) at org.eclipse.jpt.common.core.internal.utility.JobSynchronizer$SynchronizationJob.run(JobSynchronizer.java:160) at org.eclipse.jpt.common.core.internal.utility.CallbackJobSynchronizer$CallbackSynchronizationJob.run(CallbackJobSynchronizer.java:137) at org.eclipse.core.internal.jobs.Worker.run(Worker.java:54) -- 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

13 years, 11 months

3
15
0 / 0

[JBoss JIRA] (JBIDE-11395) Binding to all ports option missing from server editor

by Rob Stryker (JIRA)

Rob Stryker created JBIDE-11395: ----------------------------------- Summary: Binding to all ports option missing from server editor Key: JBIDE-11395 URL: https://issues.jboss.org/browse/JBIDE-11395 Project: Tools (JBoss Tools) Issue Type: Bug Components: JBossAS/Servers Affects Versions: 3.3.0.Beta3 Reporter: Rob Stryker Assignee: Rob Stryker Fix For: 3.3.0.Beta3 -- 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

13 years, 11 months

2
2
0 / 0

[JBoss JIRA] (JBIDE-11185) ConcurrentModificationException in SeamRuntimeListFieldEditor when user deletes Seam Runtime (probably during project building)

by Daniel Azarov (JIRA)

Daniel Azarov created JBIDE-11185: ------------------------------------- Summary: ConcurrentModificationException in SeamRuntimeListFieldEditor when user deletes Seam Runtime (probably during project building) Key: JBIDE-11185 URL: https://issues.jboss.org/browse/JBIDE-11185 Project: Tools (JBoss Tools) Issue Type: Bug Components: Seam 2 Affects Versions: 3.3.0.M5 Reporter: Daniel Azarov Assignee: Viacheslav Kabanovich This issue was found during verification of JBIDE-11174 I had few seam projects with few different seam runtimes, I just started the Studio and began deleting seam runtimes one by one. I got few similar exceptions: {code} java.util.ConcurrentModificationException at java.util.ArrayList$Itr.checkForComodification(ArrayList.java:782) at java.util.ArrayList$Itr.next(ArrayList.java:754) at org.jboss.tools.seam.ui.widget.editor.SeamRuntimeListFieldEditor.performApply(SeamRuntimeListFieldEditor.java:181) at org.jboss.tools.seam.ui.widget.editor.SeamRuntimeListFieldEditor$RemoveAction.run(SeamRuntimeListFieldEditor.java:1174) at org.jboss.tools.seam.ui.widget.editor.SeamRuntimeListFieldEditor$ActionButton$1.widgetSelected(SeamRuntimeListFieldEditor.java:949) at org.eclipse.swt.widgets.TypedListener.handleEvent(TypedListener.java:240) 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:3588) at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3209) 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.WorkbenchPreferenceDialog.open(WorkbenchPreferenceDialog.java:215) at org.eclipse.ui.internal.handlers.ShowPreferencePageHandler.execute(ShowPreferencePageHandler.java:54) 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:3588) at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3209) at org.eclipse.ui.internal.Workbench.runEventLoop(Workbench.java:2696) at org.eclipse.ui.internal.Workbench.runUI(Workbench.java:2660) at org.eclipse.ui.internal.Workbench.access$4(Workbench.java:2494) at org.eclipse.ui.internal.Workbench$7.run(Workbench.java:674) at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332) at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:667) at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:149) at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:123) 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:344) 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:622) at org.eclipse.equinox.launcher.Main.basicRun(Main.java:577) at org.eclipse.equinox.launcher.Main.run(Main.java:1410) at org.eclipse.equinox.launcher.Main.main(Main.java:1386) {code} -- 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

13 years, 11 months

4
5
0 / 0

[JBoss JIRA] (JBIDE-11035) No notification when errors occur during publish

by Daniel Atallah (JIRA)

Daniel Atallah created JBIDE-11035: -------------------------------------- Summary: No notification when errors occur during publish Key: JBIDE-11035 URL: https://issues.jboss.org/browse/JBIDE-11035 Project: Tools (JBoss Tools) Issue Type: Bug Components: JBossAS/Servers Affects Versions: 3.3.0.M5 Environment: Windows 7 64-bit / Eclipse Indigo SR1 32-bit / JBoss 4.2.3 (32-bit JVM) Reporter: Daniel Atallah Assignee: Rob Stryker I've been experiencing issues with the reliability of publishing an EAR to the local server. While trying to debug the issue, I've noticed that in the eclipse log there are lots of failures (examples follow) - these aren't reported anywhere and it looks like the publish succeeded (the server is even marked as "Synchronized"). Here are some examples of the errors in the log: {noformat} !ENTRY org.jboss.ide.eclipse.as.core 4 1644298242 2012-02-23 09:04:48.883 !MESSAGE Full publish failed for module Rating !SUBENTRY 1 org.jboss.ide.eclipse.as.core 4 0 2012-02-23 09:04:48.883 !MESSAGE The system cannot find the path specified !STACK 0 java.io.IOException: The system cannot find the path specified at java.io.WinNTFileSystem.createFileExclusively(Native Method) at java.io.File.checkAndCreate(File.java:1704) at java.io.File.createTempFile(File.java:1792) at org.jboss.ide.eclipse.as.core.publishers.AbstractServerToolsPublisher.createForceZippedChild(AbstractServerToolsPublisher.java:246) at org.jboss.ide.eclipse.as.core.publishers.AbstractServerToolsPublisher.transferForceZippedChild(AbstractServerToolsPublisher.java:282) at org.jboss.ide.eclipse.as.core.publishers.AbstractServerToolsPublisher.fullPublish(AbstractServerToolsPublisher.java:216) at org.jboss.ide.eclipse.as.core.publishers.AbstractServerToolsPublisher.publishModule(AbstractServerToolsPublisher.java:113) at org.jboss.ide.eclipse.as.core.server.internal.v7.JBoss7JSTPublisher.publishModule(JBoss7JSTPublisher.java:39) at org.jboss.ide.eclipse.as.core.publishers.AbstractPublishMethod.publishModule(AbstractPublishMethod.java:79) at org.jboss.ide.eclipse.as.core.server.internal.DeployableServerBehavior.publishModule(DeployableServerBehavior.java:103) at org.eclipse.wst.server.core.model.ServerBehaviourDelegate.publishModule(ServerBehaviourDelegate.java:1046) at org.eclipse.wst.server.core.model.ServerBehaviourDelegate.publishModules(ServerBehaviourDelegate.java:1138) at org.eclipse.wst.server.core.model.ServerBehaviourDelegate.publish(ServerBehaviourDelegate.java:955) at org.eclipse.wst.server.core.model.ServerBehaviourDelegate.publish(ServerBehaviourDelegate.java:774) at org.eclipse.wst.server.core.internal.Server.publishImpl(Server.java:3027) at org.eclipse.wst.server.core.internal.Server$PublishJob.run(Server.java:341) at org.eclipse.core.internal.jobs.Worker.run(Worker.java:54) {noformat} The above appears to be specifically related to just the deployment. {noformat} !ENTRY org.jboss.ide.eclipse.as.core 4 1644298242 2012-02-23 08:28:12.652 !MESSAGE Full publish failed for module RatingEngine !SUBENTRY 1 org.eclipse.wst.server.core 4 1644298251 2012-02-23 08:28:12.652 !MESSAGE Error copying file META-INF\MANIFEST.MF: The system cannot find the path specified !SUBENTRY 1 org.eclipse.wst.server.core 4 1644298251 2012-02-23 08:28:12.652 !MESSAGE Error copying file com\foo\rating\czar\Accessor$ShutdownHook.class: The system cannot find the path specified !SUBENTRY 1 org.eclipse.wst.server.core 4 1644298251 2012-02-23 08:28:12.652 !MESSAGE Error copying file com\foo\rating\czar\Accessor.class: The system cannot find the path specified !SUBENTRY 1 org.eclipse.wst.server.core 4 1644298251 2012-02-23 08:28:12.652 !MESSAGE Error copying file com\foo\rating\czar\ClassWeight.class: The system cannot find the path specified !SUBENTRY 1 org.eclipse.wst.server.core 4 1644298251 2012-02-23 08:28:12.652 !MESSAGE Error copying file com\foo\rating\czar\Client.class: The system cannot find the path specified !SUBENTRY 1 org.eclipse.wst.server.core 4 1644298251 2012-02-23 08:28:12.652 !MESSAGE Error copying file com\foo\rating\czar\CommunicationException.class: The system cannot find the path specified ... {noformat} The above was a case of eclipse not having actually built the project but thinking it had. With the way it works now, we have no idea if the publish succeeded or not - we only know if code changes don't seem to take effect (or in the case of a Clean publish, when the EAR deployment fails). There is something odd going on to cause the deployment issues (any pointers about the root cause are certainly welcome), but regardless of the reason, I think it is important that it's clear when a deployment isn't successful. -- 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

13 years, 11 months

4
6
0 / 0

[JBoss JIRA] Created: (JBIDE-9783) Project facets dont support JDK 1.7

by Andre Dietisheim (JIRA)

Project facets dont support JDK 1.7 ----------------------------------- Key: JBIDE-9783 URL: https://issues.jboss.org/browse/JBIDE-9783 Project: Tools (JBoss Tools) Issue Type: Bug Components: JBossAS/Servers Affects Versions: 3.3.0.M3 Reporter: Andre Dietisheim Assignee: Rob Stryker Fix For: 3.3.0.M4 Currently our facets dont support JDK 1.7. See the discussion in the tools forum: http://community.jboss.org/message/628812#628812 -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

13 years, 11 months

5
4
0 / 0

[JBoss JIRA] (JBIDE-10984) When adding a new server , UI shows the wrong text for execution environment

by shay Matasaro (JIRA)

shay Matasaro created JBIDE-10984: ------------------------------------- Summary: When adding a new server , UI shows the wrong text for execution environment Key: JBIDE-10984 URL: https://issues.jboss.org/browse/JBIDE-10984 Project: Tools (JBoss Tools) Issue Type: Bug Components: JBossAS/Servers Affects Versions: 3.3.0.M5 Environment: Ubuntu 11.10 , Eclipse indigo Reporter: shay Matasaro Assignee: Rob Stryker Priority: Minor Attachments: addnewserver.png When adding a AS 7.1 server , the UI is showing the wrong text for the execution environment although the JRE is the correct one. JRE is showing 1.6.30 , but execution environment is showing standard edition 1.4 See image attached. not sure about impact so marking it as minor Shay -- 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

13 years, 11 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 March 2012