February 2012 - jbosstools-issues

[JBoss JIRA] (JBIDE-10982) Instead of generating a 1-test dummy file with Ant script, use Maven to generate empty TEXT-{classname}.xml files before running surefire

by Nick Boldt (JIRA)

Nick Boldt created JBIDE-10982: ---------------------------------- Summary: Instead of generating a 1-test dummy file with Ant script, use Maven to generate empty TEXT-{classname}.xml files before running surefire Key: JBIDE-10982 URL: https://issues.jboss.org/browse/JBIDE-10982 Project: Tools (JBoss Tools) Issue Type: Sub-task Components: Build/Releng, testing Affects Versions: 3.3.0.Beta1 Reporter: Nick Boldt Assignee: Mickael Istria Fix For: 3.3.0.CR1 Instead of generating a 1-test dummy file with Ant script [1], use Maven to generate *empty* TEXT-{classname}.xml files before running surefire. That way should a test fail it won't be see as red, but as yellow (due to unparseable TEST*.xml file). [1] http://anonsvn.jboss.org/repos/jbosstools/trunk/build/results/collect-tes... See also JBIDE-10964 -- 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

2
7
0 / 0

[JBoss JIRA] Created: (JBIDE-4346) -Djava.library.path always overwritten with some default

by arne anka (JIRA)

-Djava.library.path always overwritten with some default -------------------------------------------------------- Key: JBIDE-4346 URL: https://jira.jboss.org/jira/browse/JBIDE-4346 Project: Tools (JBoss Tools) Issue Type: Bug Components: JBossAS Affects Versions: 3.0.1.GA Environment: jboss 4.2.2.GA eclipse: Version: 3.4.2 Build id: M20090211-1700 Reporter: arne anka in the launch configuration for my configured jboss server i need to add another directory to the parameter -Djava.library.path. after editing it looks like -Djava.library.path="/home/arne/jboss-4.2.2.GA/bin/native:/foo/bar/" saving and reopening shows instead -Djava.library.path="/home/arne/jboss-4.2.2.GA/bin/native" adding another parameter instead -Djava.library.path="/foo/bar" resulting in -Djava.library.path="/home/arne/jboss-4.2.2.GA/bin/native" -Djava.library.path="/foo/bar" ends up with -Djava.library.path="/home/arne/jboss-4.2.2.GA/bin/native" -Djava.library.path="/home/arne/jboss-4.2.2.GA/bin/native" after saving obviously some simple logic checks for the existence of the -Djava.library.path parameter and overwrites it with a default instead of at least appending its default. i don't really see what's the meaning behind that, and therefore am convinced it has to be a bug. additionally, it stops me from running at least one webapp, that requires the parameter to be set correctly. -- 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

4
10
0 / 0

[JBoss JIRA] (JBIDE-11103) Hibernate Console Internal Error while code completion in Criteria Editor

by Jiri Peterka (JIRA)

Jiri Peterka created JBIDE-11103: ------------------------------------ Summary: Hibernate Console Internal Error while code completion in Criteria Editor Key: JBIDE-11103 URL: https://issues.jboss.org/browse/JBIDE-11103 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.zip, L64 Reporter: Jiri Peterka Assignee: Dmitry Geraskov Fix For: 3.3.0.CR1 Attachments: hb-internal-error.png Java Model Exception: Java Model Status [hibernatelib does not exist] at org.eclipse.jdt.internal.core.JavaElement.newJavaModelException(JavaElement.java:505) at org.eclipse.jdt.internal.core.Openable.generateInfos(Openable.java:246) at org.eclipse.jdt.internal.core.JavaElement.openWhenClosed(JavaElement.java:518) at org.eclipse.jdt.internal.core.JavaElement.getElementInfo(JavaElement.java:255) at org.eclipse.jdt.internal.core.JavaElement.getElementInfo(JavaElement.java:241) at org.eclipse.jdt.internal.core.JavaProject.getJavaProjectElementInfo(JavaProject.java:1638) at org.eclipse.jdt.internal.core.JavaProject.newNameLookup(JavaProject.java:2325) at org.eclipse.jdt.internal.core.SearchableEnvironment.<init>(SearchableEnvironment.java:59) at org.eclipse.jdt.internal.core.SearchableEnvironment.<init>(SearchableEnvironment.java:66) at org.eclipse.jdt.internal.core.JavaProject.newSearchableNameEnvironment(JavaProject.java:2350) at org.eclipse.jdt.internal.core.eval.EvaluationContextWrapper.codeComplete(EvaluationContextWrapper.java:110) at org.eclipse.jdt.internal.core.eval.EvaluationContextWrapper.codeComplete(EvaluationContextWrapper.java:99) at org.eclipse.jdt.internal.core.eval.EvaluationContextWrapper.codeComplete(EvaluationContextWrapper.java:87) at org.hibernate.eclipse.criteriaeditor.CriteriaEditor.codeComplete(CriteriaEditor.java:220) at org.hibernate.eclipse.criteriaeditor.JavaCompletionProcessor.computeCompletionProposals(JavaCompletionProcessor.java:108) at org.eclipse.jface.text.contentassist.ContentAssistant.computeCompletionProposals(ContentAssistant.java:1830) at org.eclipse.jface.text.contentassist.CompletionProposalPopup.computeProposals(CompletionProposalPopup.java:556) at org.eclipse.jface.text.contentassist.CompletionProposalPopup.access$16(CompletionProposalPopup.java:553) at org.eclipse.jface.text.contentassist.CompletionProposalPopup$2.run(CompletionProposalPopup.java:488) at org.eclipse.swt.custom.BusyIndicator.showWhile(BusyIndicator.java:70) at org.eclipse.jface.text.contentassist.CompletionProposalPopup.showProposals(CompletionProposalPopup.java:482) at org.eclipse.jface.text.contentassist.ContentAssistant.showPossibleCompletions(ContentAssistant.java:1656) at org.eclipse.jface.text.source.SourceViewer.doOperation(SourceViewer.java:930) at org.eclipse.ui.texteditor.TextOperationAction$1.run(TextOperationAction.java:128) at org.eclipse.swt.custom.BusyIndicator.showWhile(BusyIndicator.java:70) at org.eclipse.ui.texteditor.TextOperationAction.run(TextOperationAction.java:126) at org.eclipse.jface.action.Action.runWithEvent(Action.java:498) at org.eclipse.ui.commands.ActionHandler.execute(ActionHandler.java:185) at org.eclipse.ui.internal.handlers.LegacyHandlerWrapper.execute(LegacyHandlerWrapper.java:109) 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.keys.WorkbenchKeyboard.executeCommand(WorkbenchKeyboard.java:468) at org.eclipse.ui.internal.keys.WorkbenchKeyboard.press(WorkbenchKeyboard.java:786) at org.eclipse.ui.internal.keys.WorkbenchKeyboard.processKeyEvent(WorkbenchKeyboard.java:885) at org.eclipse.ui.internal.keys.WorkbenchKeyboard.filterKeySequenceBindings(WorkbenchKeyboard.java:567) at org.eclipse.ui.internal.keys.WorkbenchKeyboard.access$3(WorkbenchKeyboard.java:508) at org.eclipse.ui.internal.keys.WorkbenchKeyboard$KeyDownFilter.handleEvent(WorkbenchKeyboard.java:123) at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84) at org.eclipse.swt.widgets.Display.filterEvent(Display.java:1531) at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1257) at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1282) at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1267) at org.eclipse.swt.widgets.Widget.sendKeyEvent(Widget.java:1294) at org.eclipse.swt.widgets.Widget.gtk_key_press_event(Widget.java:730) at org.eclipse.swt.widgets.Control.gtk_key_press_event(Control.java:3019) at org.eclipse.swt.widgets.Composite.gtk_key_press_event(Composite.java:734) at org.eclipse.swt.widgets.Widget.windowProc(Widget.java:1743) at org.eclipse.swt.widgets.Control.windowProc(Control.java:5016) at org.eclipse.swt.widgets.Display.windowProc(Display.java:4408) at org.eclipse.swt.internal.gtk.OS._gtk_main_do_event(Native Method) at org.eclipse.swt.internal.gtk.OS.gtk_main_do_event(OS.java:8422) at org.eclipse.swt.widgets.Display.eventProc(Display.java:1245) at org.eclipse.swt.internal.gtk.OS._g_main_context_iteration(Native Method) at org.eclipse.swt.internal.gtk.OS.g_main_context_iteration(OS.java:2276) at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3207) at org.eclipse.ui.internal.Workbench.runEventLoop(Workbench.java:2701) at org.eclipse.ui.internal.Workbench.runUI(Workbench.java:2665) at org.eclipse.ui.internal.Workbench.access$4(Workbench.java:2499) at org.eclipse.ui.internal.Workbench$7.run(Workbench.java:679) at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332) at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:668) 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:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:597) 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) -- 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

2
6
0 / 0

[JBoss JIRA] (JBIDE-10087) JBoss AS 7 is either Standalone or Domain, Default does not really apply any more, look at the screen shot

by Jim Tyrrell (Created) (JIRA)

JBoss AS 7 is either Standalone or Domain, Default does not really apply any more, look at the screen shot ---------------------------------------------------------------------------------------------------------- Key: JBIDE-10087 URL: https://issues.jboss.org/browse/JBIDE-10087 Project: Tools (JBoss Tools) Issue Type: Feature Request Components: JBossAS/Servers Reporter: Jim Tyrrell Assignee: Rob Stryker See the screen shot -- 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

8
8
0 / 0

[JBoss JIRA] Created: (JBIDE-2927) There should be an option to/not to copy the libs/resources when user install Seam facet.

by Alexey Kazakov (JIRA)

There should be an option to/not to copy the libs/resources when user install Seam facet. ----------------------------------------------------------------------------------------- Key: JBIDE-2927 URL: https://jira.jboss.org/jira/browse/JBIDE-2927 Project: Tools (JBoss Tools) Issue Type: Feature Request Components: Seam Reporter: Alexey Kazakov Assignee: Alexey Kazakov Fix For: 3.0.0.cr1 We should add "Copy resources" and "Copy libs" checkboxes to install facet page. Should we disable it by default? -- 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

9
43
0 / 0

[JBoss JIRA] Created: (JBDS-1676) NullPointerException in SmooksGraphicalEditorPart

by Martin Weiler (JIRA)

NullPointerException in SmooksGraphicalEditorPart ------------------------------------------------- Key: JBDS-1676 URL: https://issues.jboss.org/browse/JBDS-1676 Project: Developer Studio (JBoss Developer Studio) Issue Type: Bug Components: SOA Platform Affects Versions: 4.0.0.GA Environment: Windows 7 -vm "C:\Program Files (x86)\Java\jdk1.6.0_23\bin" Reporter: Martin Weiler Attachments: debugInfo.txt, example.jar, example.xsd I have a problem using the 'Smooks Processing' tool to configure a smooks file (used for converting XML to Java) when the Java-class is located in a jar file. The problem seems to relate to the 'Java Mapping' view of the 'Smooks Processing' tool and generates an OutOfMemoryException. The exception occurs when inside the 'Java Mapping' view and clicking or dragging input elements to corresponding output elements or selecting the connection between the elements. The exception sometimes occur at the first adjustments and sometimes it takes several adjustments before it occurs. When using a file where the elements already have been connected, the exception sometimes occur imidiatly when selecting the 'Java Mapping' icon. I have not seen this problem when using a Java-class which is not located in a jar file. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 1 month

6
15
0 / 0

[JBoss JIRA] Created: (JBIDE-9790) ClassCastException with VpeElementMapping use

by Vitali Yemialyanchyk (JIRA)

ClassCastException with VpeElementMapping use --------------------------------------------- Key: JBIDE-9790 URL: https://issues.jboss.org/browse/JBIDE-9790 Project: Tools (JBoss Tools) Issue Type: Bug Components: Visual Page Editor core, Visual Page Editor Templates Affects Versions: 3.3.0.M3 Reporter: Vitali Yemialyanchyk Assignee: Yahor Radtsevich Priority: Optional VpeElementMapping expected VpeTemplate as one of parameters in constructor, but in VpeVisualDomBuilder in line function stopToggle (line 940) it cast elementMapping.getTemplate() to VpeTemplateSafeWrapper, i.e. by default it expect VpeTemplateSafeWrapper in VpeElementMapping. You should update VpeElementMapping so it expect VpeTemplateSafeWrapper or wrap VpeTemplate to VpeTemplateSafeWrapper in VpeElementMapping. Cause we get such exception: java.lang.ClassCastException: com.hp.dcp.ve.ui.template.JSPCustomTagTemplate cannot be cast to org.jboss.tools.vpe.editor.template.VpeTemplateSafeWrapper at org.jboss.tools.vpe.editor.VpeVisualDomBuilder.stopToggle(VpeVisualDomBuilder.java:940) at org.jboss.tools.vpe.editor.VpeController.notifyChangedInUiThread(VpeController.java:730) at org.jboss.tools.vpe.editor.VpeController$1.runInUIThread(VpeController.java:554) 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:135) at org.eclipse.swt.widgets.Display.runAsyncMessages(Display.java:4140) at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3757) 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(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source) at java.lang.reflect.Method.invoke(Unknown Source) 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) of course we can fix it on our side - but you should make your code safe to prevent such errors. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 1 month

7
18
0 / 0

[JBoss JIRA] (JBIDE-10745) VPE toolbar buttons are not updated after VPE Preferences page has been changed

by Denis Maliarevich (JIRA)

Denis Maliarevich created JBIDE-10745: ----------------------------------------- Summary: VPE toolbar buttons are not updated after VPE Preferences page has been changed Key: JBIDE-10745 URL: https://issues.jboss.org/browse/JBIDE-10745 Project: Tools (JBoss Tools) Issue Type: Bug Reporter: Denis Maliarevich VPE toolbar buttons are not updated after VPE Properties page has been changed -- 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

2
8
0 / 0

[JBoss JIRA] (JBIDE-11047) BrowserSim: the features should be disabled for 64-bit Java on 64-bit Windows

by Yahor Radtsevich (JIRA)

Yahor Radtsevich created JBIDE-11047: ---------------------------------------- Summary: BrowserSim: the features should be disabled for 64-bit Java on 64-bit Windows Key: JBIDE-11047 URL: https://issues.jboss.org/browse/JBIDE-11047 Project: Tools (JBoss Tools) Issue Type: Bug Reporter: Yahor Radtsevich BrowserSim cannot be run on 64-bit Java on 64-bit Windows (JBIDE-11046). The platform filters of plugins should be changed to disable BrowserSim there. -- 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
58
0 / 0

[JBoss JIRA] (JBIDE-11094) archives uses explodedBundles in surefire/feature xml instead of BundleShape

by Max Rydahl Andersen (JIRA)

Max Rydahl Andersen created JBIDE-11094: ------------------------------------------- Summary: archives uses explodedBundles in surefire/feature xml instead of BundleShape Key: JBIDE-11094 URL: https://issues.jboss.org/browse/JBIDE-11094 Project: Tools (JBoss Tools) Issue Type: Bug Components: Archives Reporter: Max Rydahl Andersen Assignee: Rob Stryker -- 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
16
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