March 2011 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] Created: (JBDS-1534) Invalid links in Drools Documentation

by Vlado Pakan (JIRA)

Invalid links in Drools Documentation ------------------------------------- Key: JBDS-1534 URL: https://issues.jboss.org/browse/JBDS-1534 Project: Developer Studio (JBoss Developer Studio) Issue Type: Bug Components: Doc - Drools Affects Versions: 4.0.0.CR1 Reporter: Vlado Pakan There are these invalid links in Drools Documentation http://download.jboss.org/jbosstools/nightly-docs/en/drools_tools_ref_gui...: Table 4.1. DSL Editor Components. "Sort: please, for more information see the ??? section." Chapter 4.1.1. Edit language mapping Wizard "Their names as well as the meaning of the options are correspond to the rows of the table (see ???TITLE???)." -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 7 months

2
3
0 / 0

[JBoss JIRA] Created: (JBDS-1560) Include BPEL Project Examples in JBDS

by Pavol Srna (JIRA)

Include BPEL Project Examples in JBDS ------------------------------------- Key: JBDS-1560 URL: https://issues.jboss.org/browse/JBDS-1560 Project: Developer Studio (JBoss Developer Studio) Issue Type: Feature Request Components: SOA Platform Affects Versions: 4.0.0.CR2 Reporter: Pavol Srna After installing BPEL Tools from update site in JBDS, it would be nice to have also the BPEL Project Examples installed by default. -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 8 months

6
46
0 / 0

[JBoss JIRA] Created: (JBIDE-8359) VisualEditor throws exception and stays open for file from project that is being closed

by Denis Golovin (JIRA)

VisualEditor throws exception and stays open for file from project that is being closed --------------------------------------------------------------------------------------- Key: JBIDE-8359 URL: https://issues.jboss.org/browse/JBIDE-8359 Project: Tools (JBoss Tools) Issue Type: Bug Components: Visual Page Editor core Affects Versions: 3.2.0.CR1 Reporter: Denis Golovin Assignee: Maxim Areshkau Fix For: 3.3.0.M1 [noformat} Unable to create editor ID org.jboss.tools.jst.jsp.jspeditor.HTMLTextEditor: An unexpected exception was thrown. java.lang.NullPointerException at org.jboss.tools.jst.jsp.selection.bar.SelectionBar.<init>(SelectionBar.java:113) at org.jboss.tools.jst.jsp.jspeditor.JSPMultiPageEditorPart.addPage(JSPMultiPageEditorPart.java:115) at org.jboss.tools.jst.jsp.jspeditor.JSPMultiPageEditor.createPagesForVPE(JSPMultiPageEditor.java:489) at org.jboss.tools.jst.jsp.jspeditor.JSPMultiPageEditor.createPages(JSPMultiPageEditor.java:411) at org.jboss.tools.jst.jsp.jspeditor.JSPMultiPageEditorPart.createPartControl(JSPMultiPageEditorPart.java:164) at org.eclipse.ui.internal.EditorReference.createPartHelper(EditorReference.java:670) at org.eclipse.ui.internal.EditorReference.createPart(EditorReference.java:465) at org.eclipse.ui.internal.WorkbenchPartReference.getPart(WorkbenchPartReference.java:595) at org.eclipse.ui.internal.PartPane.setVisible(PartPane.java:313) at org.eclipse.ui.internal.presentations.PresentablePart.setVisible(PresentablePart.java:180) at org.eclipse.ui.internal.presentations.util.PresentablePartFolder.select(PresentablePartFolder.java:270) at org.eclipse.ui.internal.presentations.util.LeftToRightTabOrder.select(LeftToRightTabOrder.java:65) at org.eclipse.ui.internal.presentations.util.TabbedStackPresentation.selectPart(TabbedStackPresentation.java:473) at org.eclipse.ui.internal.PartStack.refreshPresentationSelection(PartStack.java:1254) at org.eclipse.ui.internal.PartStack.handleDeferredEvents(PartStack.java:1222) at org.eclipse.ui.internal.LayoutPart.deferUpdates(LayoutPart.java:400) at org.eclipse.ui.internal.PartSashContainer.handleDeferredEvents(PartSashContainer.java:1409) at org.eclipse.ui.internal.LayoutPart.deferUpdates(LayoutPart.java:400) at org.eclipse.ui.internal.WorkbenchPage.handleDeferredEvents(WorkbenchPage.java:1420) at org.eclipse.ui.internal.WorkbenchPage.deferUpdates(WorkbenchPage.java:1410) at org.eclipse.ui.internal.WorkbenchPage.closeEditors(WorkbenchPage.java:1384) at org.eclipse.ui.internal.WorkbenchPage.closeEditor(WorkbenchPage.java:1448) at org.eclipse.ui.texteditor.AbstractTextEditor$23.run(AbstractTextEditor.java:4156) 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.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) {noformat} -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 8 months

2
9
0 / 0

[JBoss JIRA] Created: (JBIDE-5046) JSF model/builder

by Alexey Kazakov (JIRA)

JSF model/builder ----------------- Key: JBIDE-5046 URL: https://jira.jboss.org/jira/browse/JBIDE-5046 Project: Tools (JBoss Tools) Issue Type: Task Components: JSF Reporter: Alexey Kazakov Assignee: Viacheslav Kabanovich Fix For: LATER We have to create JSF builder to JSF 2 artifacts into JSF model. Such as: - annotated manage beans - resources ... -- 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, 8 months

2
3
0 / 0

[JBoss JIRA] Created: (JBIDE-6338) Ability to click through to resources specified as part of Shrinkwrap definition

by Pete Muir (JIRA)

Ability to click through to resources specified as part of Shrinkwrap definition -------------------------------------------------------------------------------- Key: JBIDE-6338 URL: https://jira.jboss.org/browse/JBIDE-6338 Project: Tools (JBoss Tools) Issue Type: Feature Request Components: testing Reporter: Pete Muir With Shrinkwrap you can package a resource (such as web.xml) into the archive. Would be great to cmd-click on that resource and be taken to it. -- 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

14 years, 8 months

3
4
0 / 0

[JBoss JIRA] Created: (JBIDE-6568) Give error/warning on use of Class in a TestCase that are not found in the @Deployment

by Aslak Knutsen (JIRA)

Give error/warning on use of Class in a TestCase that are not found in the @Deployment -------------------------------------------------------------------------------------- Key: JBIDE-6568 URL: https://jira.jboss.org/browse/JBIDE-6568 Project: Tools (JBoss Tools) Issue Type: Feature Request Components: testing Reporter: Aslak Knutsen To help avoid trail and error of what to add to the @Deployment in Arquillian, tooling could verify that the classes used in the TestCase are in the defined @Deployment. If not found, it could be marked as a warning/error. -- 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

14 years, 8 months

4
6
0 / 0

[JBoss JIRA] Created: (JBIDE-6318) New Arquillian test wizard

by Pete Muir (JIRA)

New Arquillian test wizard -------------------------- Key: JBIDE-6318 URL: https://jira.jboss.org/browse/JBIDE-6318 Project: Tools (JBoss Tools) Issue Type: Feature Request Components: testing Reporter: Pete Muir Create a new Arquillian test. Wizard would need to ask user to select between JUnit and TestNG (set a preffered one somewhere in prefs?), and then generate a class with boilerplate (@RunWith/extends), and a stub deployment. -- 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

14 years, 8 months

3
2
0 / 0

[JBoss JIRA] Created: (JBIDE-6662) View Arquillian Deployment

by Aslak Knutsen (JIRA)

View Arquillian Deployment -------------------------- Key: JBIDE-6662 URL: https://jira.jboss.org/browse/JBIDE-6662 Project: Tools (JBoss Tools) Issue Type: Feature Request Components: testing Reporter: Aslak Knutsen It should be possible to have a view that will show the exact ShrinkWrap archive Arquillian is deploying for the test given test case. -- 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

14 years, 8 months

3
2
0 / 0

[JBoss JIRA] Created: (JBIDE-6319) Add Arquillian Capabilities

by Pete Muir (JIRA)

Add Arquillian Capabilities --------------------------- Key: JBIDE-6319 URL: https://jira.jboss.org/browse/JBIDE-6319 Project: Tools (JBoss Tools) Issue Type: Feature Request Components: testing Reporter: Pete Muir Ability to right click and select "Add Arquillian to project" - this should add the requisites libraries to the project -- 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

14 years, 8 months

3
2
0 / 0

[JBoss JIRA] Created: (JBIDE-496) Add Maping files

by Krasimir Goutcev (JIRA)

Add Maping files ---------------- Key: JBIDE-496 URL: http://jira.jboss.com/jira/browse/JBIDE-496 Project: JBoss Tools Issue Type: Feature Request Components: Hibernate Tools Reporter: Krasimir Goutcev Assigned To: Max Andersen Possibility to add mapping lfiles as Exadel ORM Explorer -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years, 8 months

4
10
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 2011