October 2007 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] Closed: (JBIDE-245) XDoclet not auto-generating select methods

by Rob Stryker (JIRA)

[ http://jira.jboss.com/jira/browse/JBIDE-245?page=all ] Rob Stryker closed JBIDE-245. ----------------------------- Resolution: Out of Date JIRA cleanup: Closing old bugs > XDoclet not auto-generating select methods > ------------------------------------------ > > Key: JBIDE-245 > URL: http://jira.jboss.com/jira/browse/JBIDE-245 > Project: JBoss Tools > Issue Type: Bug > Affects Versions: 1.5 Release Candidate 1 > Environment: Windows XP, 1.5RC1, Eclipse 3.1.1 > Reporter: Samuel Richter > > Running XDoclet fails to auto-generate a given bean's select methods--they are absent in the auto-generated local home interfaces. This behavior can be observed for version 4.0.x and 3.2.x of the jboss.net xdoclet module version. -- 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

16 years, 9 months

1
0
0 / 0

[JBoss JIRA] Closed: (JBIDE-236) Project Packaging - Ability to choose filename and location for xml file

by Rob Stryker (JIRA)

[ http://jira.jboss.com/jira/browse/JBIDE-236?page=all ] Rob Stryker closed JBIDE-236. ----------------------------- Resolution: Out of Date JIRA cleanup: Closing old bugs > Project Packaging - Ability to choose filename and location for xml file > ------------------------------------------------------------------------ > > Key: JBIDE-236 > URL: http://jira.jboss.com/jira/browse/JBIDE-236 > Project: JBoss Tools > Issue Type: Feature Request > Affects Versions: 1.5 Milestone 2 > Reporter: Gray > Priority: Minor > > Having a GUI tool for managing the packaging of your artifacts is good. > However it would be good if one could choose the output filename and location for the packaging xml file so it could live in the same place your other ant files live (regardless of where that might be for a given Eclipse project). -- 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

16 years, 9 months

1
0
0 / 0

[JBoss JIRA] Closed: (JBIDE-105) Undeploy and Redeploy disabled

by Rob Stryker (JIRA)

[ http://jira.jboss.com/jira/browse/JBIDE-105?page=all ] Rob Stryker closed JBIDE-105. ----------------------------- Resolution: Out of Date JIRA cleanup: Closing old bugs > Undeploy and Redeploy disabled > ------------------------------ > > Key: JBIDE-105 > URL: http://jira.jboss.com/jira/browse/JBIDE-105 > Project: JBoss Tools > Issue Type: Bug > Environment: Eclipse 3.1 M4 > Reporter: Martin Lopez > > After deploying a resource, the options: Undeploy and Redeploy are not enabled. -- 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

16 years, 9 months

1
0
0 / 0

[JBoss JIRA] Closed: (JBIDE-121) NullPointerException during creation of debug configuration

by Rob Stryker (JIRA)

[ http://jira.jboss.com/jira/browse/JBIDE-121?page=all ] Rob Stryker closed JBIDE-121. ----------------------------- Resolution: Out of Date JIRA cleanup: Closing old bugs > NullPointerException during creation of debug configuration > ----------------------------------------------------------- > > Key: JBIDE-121 > URL: http://jira.jboss.com/jira/browse/JBIDE-121 > Project: JBoss Tools > Issue Type: Bug > Reporter: Michael Neubauer > > NullPointerException during creation of debug configuration > In the debug configuration dialog occures a dialog box: > ?An error has occurred. See error log for more details? > (Log file details at > the bottom of this description). If I do not change the > Name of the > configuration the error occurs when I try to select it. > The error immediately > occurs, when I change the name of the configuration. I > am using a gentoo box > with amd64 and the standard emerged packages: > blackdown-jdk-1.4.2.01 > Jboss-ide 1.4.1-e30 > eclipse-3.0.1-r2 > Code: > !ENTRY org.eclipse.core.runtime 4 2 Feb 08, 2005 > 23:26:49.608 > !MESSAGE Problems occurred when invoking code from > plug- > in: "org.eclipse.core.runtime". > !STACK 0 > java.lang.NullPointerException > at > org.jboss.ide.eclipse.launcher.ui.configuration.HomeTab. > updateServerConfigurati > ons(HomeTab.java:328) > at > org.jboss.ide.eclipse.launcher.ui.configuration.HomeTab. > access$1 > (HomeTab.java:311) > at > org.jboss.ide.eclipse.launcher.ui.configuration.HomeTab > $1.modifyText > (HomeTab.java:138) > at > org.eclipse.swt.widgets.TypedListener.handleEvent > (TypedListener.java:187) > at > org.eclipse.swt.widgets.EventTable.sendEvent > (EventTable.java:82) > at org.eclipse.swt.widgets.Widget.sendEvent > (Widget.java:954) > at org.eclipse.swt.widgets.Widget.sendEvent > (Widget.java:978) > at org.eclipse.swt.widgets.Widget.sendEvent > (Widget.java:959) > at org.eclipse.swt.widgets.Text.setText > (Text.java:1563) > at > org.jboss.ide.eclipse.launcher.ui.configuration.HomeTab. > updateHomedirFromConfig > (HomeTab.java:286) > at > org.jboss.ide.eclipse.launcher.ui.configuration.HomeTab. > initializeFrom > (HomeTab.java:219) > at > org.eclipse.debug.ui.AbstractLaunchConfigurationTabGro > up.initializeFrom > (AbstractLaunchConfigurationTabGroup.java:86) > at > org.eclipse.debug.internal.ui.launchConfigurations.Launc > hConfigurationTabGroupV > iewer.displayInstanceTabs > (LaunchConfigurationTabGroupViewer.java:540) > at > org.eclipse.debug.internal.ui.launchConfigurations.Launc > hConfigurationTabGroupV > iewer$5.run > (LaunchConfigurationTabGroupViewer.java:473) > at > org.eclipse.swt.custom.BusyIndicator.showWhile > (BusyIndicator.java:69) > at > org.eclipse.debug.internal.ui.launchConfigurations.Launc > hConfigurationTabGroupV > iewer.inputChanged > (LaunchConfigurationTabGroupViewer.java:490) > at > org.eclipse.debug.internal.ui.launchConfigurations.Launc > hConfigurationTabGroupV > iewer.setInput > (LaunchConfigurationTabGroupViewer.java:454) > at > org.eclipse.debug.internal.ui.launchConfigurations.Launc > hConfigurationsDialog.h > andleLaunchConfigurationSelectionChanged > (LaunchConfigurationsDialog.java:775) > at > org.eclipse.debug.internal.ui.launchConfigurations.Launc > hConfigurationsDialog$2 > .selectionChanged > (LaunchConfigurationsDialog.java:585) > at org.eclipse.jface.viewers.Viewer$2.run > (Viewer.java:159) > at > org.eclipse.core.internal.runtime.InternalPlatform.run > (InternalPlatform.java:616) > at org.eclipse.core.runtime.Platform.run > (Platform.java:747) > at > org.eclipse.jface.viewers.Viewer.fireSelectionChanged > (Viewer.java:157) > at > org.eclipse.jface.viewers.StructuredViewer.updateSelecti > on > (StructuredViewer.java:1394) > at > org.eclipse.jface.viewers.StructuredViewer.setSelection > (StructuredViewer.java:1093) > at org.eclipse.jface.viewers.Viewer.setSelection > (Viewer.java:356) > at > org.eclipse.debug.internal.ui.launchConfigurations.Launc > hConfigurationView.laun > chConfigurationRemoved > (LaunchConfigurationView.java:284) > at > org.eclipse.debug.internal.core.LaunchManager$Configur > ationNotifier.run > (LaunchManager.java:1484) > at > org.eclipse.core.internal.runtime.InternalPlatform.run > (InternalPlatform.java:616) > at org.eclipse.core.runtime.Platform.run > (Platform.java:747) > at > org.eclipse.debug.internal.core.LaunchManager$Configur > ationNotifier.notify > (LaunchManager.java:1505) > at > org.eclipse.debug.internal.core.LaunchManager.launchCo > nfigurationDeleted > (LaunchManager.java:736) > at > org.eclipse.debug.internal.core.LaunchConfiguration.dele > te > (LaunchConfiguration.java:317) > at > org.eclipse.debug.internal.ui.launchConfigurations.Delet > eLaunchConfigurationAct > ion.performAction > (DeleteLaunchConfigurationAction.java:65) > at > org.eclipse.debug.internal.ui.launchConfigurations.Abstr > actLaunchConfigurationA > ction$1.run > (AbstractLaunchConfigurationAction.java:103) > at > org.eclipse.swt.custom.BusyIndicator.showWhile > (BusyIndicator.java:69) > at > org.eclipse.debug.internal.ui.launchConfigurations.Abstr > actLaunchConfigurationA > ction.run(AbstractLaunchConfigurationAction.java:106) > at > org.eclipse.ui.actions.BaseSelectionListenerAction.runWi > thEvent > (BaseSelectionListenerAction.java:166) > at > org.eclipse.jface.action.ActionContributionItem.handleWi > dgetSelection > (ActionContributionItem.java:915) > at > org.eclipse.jface.action.ActionContributionItem.access$5 > 00 > (ActionContributionItem.java:47) > at > org.eclipse.jface.action.ActionContributionItem$7.handle > Event > (ActionContributionItem.java:785) > at > org.eclipse.swt.widgets.EventTable.sendEvent > (EventTable.java:82) > at org.eclipse.swt.widgets.Widget.sendEvent > (Widget.java:954) > at > org.eclipse.swt.widgets.Display.runDeferredEvents > (Display.java:2595) > at > org.eclipse.swt.widgets.Display.readAndDispatch > (Display.java:2298) > at > org.eclipse.jface.window.Window.runEventLoop > (Window.java:668) > at org.eclipse.jface.window.Window.open > (Window.java:648) > at > org.eclipse.debug.internal.ui.launchConfigurations.Launc > hConfigurationsDialog.o > pen(LaunchConfigurationsDialog.java:419) > at org.eclipse.debug.ui.DebugUITools$1.run > (DebugUITools.java:381) > at > org.eclipse.swt.custom.BusyIndicator.showWhile > (BusyIndicator.java:69) > at > org.eclipse.debug.ui.DebugUITools.openLaunchConfigura > tionDialogOnGroup > (DebugUITools.java:385) > at > org.eclipse.debug.ui.DebugUITools.openLaunchConfigura > tionDialogOnGroup > (DebugUITools.java:327) > at > org.eclipse.debug.ui.actions.OpenLaunchDialogAction.ru > n > (OpenLaunchDialogAction.java:80) > at org.eclipse.jface.action.Action.runWithEvent > (Action.java:881) > at > org.eclipse.jface.action.ActionContributionItem.handleWi > dgetSelection > (ActionContributionItem.java:915) > at > org.eclipse.jface.action.ActionContributionItem.access$5 > 00 > (ActionContributionItem.java:47) > at > org.eclipse.jface.action.ActionContributionItem$7.handle > Event > (ActionContributionItem.java:785) > at > org.eclipse.swt.widgets.EventTable.sendEvent > (EventTable.java:82) > at org.eclipse.swt.widgets.Widget.sendEvent > (Widget.java:954) > at > org.eclipse.swt.widgets.Display.runDeferredEvents > (Display.java:2595) > at > org.eclipse.swt.widgets.Display.readAndDispatch > (Display.java:2298) > at > org.eclipse.ui.internal.Workbench.runEventLoop > (Workbench.java:1377) > at org.eclipse.ui.internal.Workbench.runUI > (Workbench.java:1348) > at > org.eclipse.ui.internal.Workbench.createAndRunWorkben > ch > (Workbench.java:254) > at > org.eclipse.ui.PlatformUI.createAndRunWorkbench > (PlatformUI.java:141) > at org.eclipse.ui.internal.ide.IDEApplication.run > (IDEApplication.java:96) > at > org.eclipse.core.internal.runtime.PlatformActivator$1.run > (PlatformActivator.java:335) > at > org.eclipse.core.runtime.adaptor.EclipseStarter.run > (EclipseStarter.java:273) > at > org.eclipse.core.runtime.adaptor.EclipseStarter.run > (EclipseStarter.java:129) > 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:324) > at org.eclipse.core.launcher.Main.basicRun > (Main.java:185) > at org.eclipse.core.launcher.Main.run > (Main.java:704) > at org.eclipse.core.launcher.Main.main > (Main.java:688) -- 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

16 years, 9 months

1
0
0 / 0

[JBoss JIRA] Closed: (JBIDE-166) exception during refactoring

by Rob Stryker (JIRA)

[ http://jira.jboss.com/jira/browse/JBIDE-166?page=all ] Rob Stryker closed JBIDE-166. ----------------------------- Resolution: Out of Date JIRA cleanup: Closing old bugs jsp editor replaced by wtp > exception during refactoring > ---------------------------- > > Key: JBIDE-166 > URL: http://jira.jboss.com/jira/browse/JBIDE-166 > Project: JBoss Tools > Issue Type: Bug > Environment: eclipse ide 3.1M5a > Reporter: mike andrews > > got a null pointer exception during refactoring. was not using any functionality of jboss plugin. > see original eclipse bug report, which was redirected to jboss: > https://bugs.eclipse.org/bugs/show_bug.cgi?id=89201 -- 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

16 years, 9 months

1
0
0 / 0

[JBoss JIRA] Closed: (JBIDE-213) removing/adding a file from/to the packaging list will NOT rebuild the jar when other dependencies are unchanged AND the jar already exists

by Rob Stryker (JIRA)

[ http://jira.jboss.com/jira/browse/JBIDE-213?page=all ] Rob Stryker closed JBIDE-213. ----------------------------- Resolution: Out of Date JIRA cleanup: Closing old bugs > removing/adding a file from/to the packaging list will NOT rebuild the jar when other dependencies are unchanged AND the jar already exists > ------------------------------------------------------------------------------------------------------------------------------------------- > > Key: JBIDE-213 > URL: http://jira.jboss.com/jira/browse/JBIDE-213 > Project: JBoss Tools > Issue Type: Bug > Affects Versions: 1.5 Milestone 2 > Environment: linux and windows > Reporter: Tom Vijlbrief > > If a file is simply removed/added from/to the packaging list then the resulting war/jar will not be rebuild if it already > exists. The result jar/war has to be deleted first. > This is very confusing when e.g. removing/adding jars from WEB-INF/lib when solving classloaders issues. -- 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

16 years, 9 months

1
0
0 / 0

[JBoss JIRA] Closed: (JBIDE-238) Not possible to add two source archives with the same name

by Rob Stryker (JIRA)

[ http://jira.jboss.com/jira/browse/JBIDE-238?page=all ] Rob Stryker closed JBIDE-238. ----------------------------- Resolution: Done JIRA cleanup: Closing old bugs > Not possible to add two source archives with the same name > ---------------------------------------------------------- > > Key: JBIDE-238 > URL: http://jira.jboss.com/jira/browse/JBIDE-238 > Project: JBoss Tools > Issue Type: Bug > Affects Versions: 1.5 Milestone 2 > Environment: Win XP, Eclipse 3.1, JBoss IDE 1.5M2, JBoss 4.0.2 > Reporter: Der Meister > > For each library jar used within our projects there is a src.zip with the source code in the library's directory. > However, in a JBoss Debug configuration on the source tab it is not possible to add two archives with the same name (e.g. struts/src.zip and commons-beanutils/src.zip), the second one added is just ignored. > The same is true, when trying to add a new source archive during debugging. > The IDE should accept multiple source archives with the same name, but in different directories! -- 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

16 years, 9 months

1
0
0 / 0

[JBoss JIRA] Closed: (JBIDE-238) Not possible to add two source archives with the same name

by Rob Stryker (JIRA)

[ http://jira.jboss.com/jira/browse/JBIDE-238?page=all ] Rob Stryker closed JBIDE-238. ----------------------------- Resolution: Out of Date JIRA cleanup: Closing old bugs > Not possible to add two source archives with the same name > ---------------------------------------------------------- > > Key: JBIDE-238 > URL: http://jira.jboss.com/jira/browse/JBIDE-238 > Project: JBoss Tools > Issue Type: Bug > Affects Versions: 1.5 Milestone 2 > Environment: Win XP, Eclipse 3.1, JBoss IDE 1.5M2, JBoss 4.0.2 > Reporter: Der Meister > > For each library jar used within our projects there is a src.zip with the source code in the library's directory. > However, in a JBoss Debug configuration on the source tab it is not possible to add two archives with the same name (e.g. struts/src.zip and commons-beanutils/src.zip), the second one added is just ignored. > The same is true, when trying to add a new source archive during debugging. > The IDE should accept multiple source archives with the same name, but in different directories! -- 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

16 years, 9 months

1
0
0 / 0

[JBoss JIRA] Closed: (JBIDE-117) JSP editor - block indent

by Rob Stryker (JIRA)

[ http://jira.jboss.com/jira/browse/JBIDE-117?page=all ] Rob Stryker closed JBIDE-117. ----------------------------- Resolution: Done JIRA cleanup: Closing old bugs > JSP editor - block indent > ------------------------- > > Key: JBIDE-117 > URL: http://jira.jboss.com/jira/browse/JBIDE-117 > Project: JBoss Tools > Issue Type: Feature Request > Environment: JBoss IDE v1.4.1 > Reporter: Frank Merenda > Priority: Minor > > Please consider including a block-level indent function in the JSP editor, so several lines can be selected at once, and indented/unindented with the tab key. Right now each line has to be indented individually. -- 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

16 years, 9 months

1
0
0 / 0

[JBoss JIRA] Reopened: (JBIDE-238) Not possible to add two source archives with the same name

by Rob Stryker (JIRA)

[ http://jira.jboss.com/jira/browse/JBIDE-238?page=all ] Rob Stryker reopened JBIDE-238: ------------------------------- > Not possible to add two source archives with the same name > ---------------------------------------------------------- > > Key: JBIDE-238 > URL: http://jira.jboss.com/jira/browse/JBIDE-238 > Project: JBoss Tools > Issue Type: Bug > Affects Versions: 1.5 Milestone 2 > Environment: Win XP, Eclipse 3.1, JBoss IDE 1.5M2, JBoss 4.0.2 > Reporter: Der Meister > > For each library jar used within our projects there is a src.zip with the source code in the library's directory. > However, in a JBoss Debug configuration on the source tab it is not possible to add two archives with the same name (e.g. struts/src.zip and commons-beanutils/src.zip), the second one added is just ignored. > The same is true, when trying to add a new source archive during debugging. > The IDE should accept multiple source archives with the same name, but in different directories! -- 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

16 years, 9 months

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jbosstools-issues October 2007