October 2007 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] Closed: (JBIDE-282) Maven pom.xml backed project libraries instead of hardcoded classpath containers

by Rob Stryker (JIRA)

[ http://jira.jboss.com/jira/browse/JBIDE-282?page=all ] Rob Stryker closed JBIDE-282. ----------------------------- Resolution: Out of Date JIRA cleanup: Closing old issues > Maven pom.xml backed project libraries instead of hardcoded classpath containers > -------------------------------------------------------------------------------- > > Key: JBIDE-282 > URL: http://jira.jboss.com/jira/browse/JBIDE-282 > Project: JBoss Tools > Issue Type: Feature Request > Reporter: Tuomas Kiviaho > Priority: Optional > > When usign a IDE plugin project creation there usually will come couple of hardcoded eclipse libraries a.k.a classpath containers that most likely will be referenced by the project. > If the JBoss IDE with all the neccessary plugins are not installed, all of the project dependencies behind plugin spesific classpath will cause project not to compile. In this scenario it's quite hard to backtrack the original packages. When IDE evolves and dependencies change, temporary plugin installation doesn't fix the problem, if original IDE version is not known. Therefore SCM requires additional documentation over how to resolve depencencies. > I have noticed that the next generation JBoss build system package dependency mechanism will be Maven. Instead of hadrcoded... > new IPath[] { > new Path("jboss-aop-jdk50.jar"), new Path("jboss-common.jar"), new Path("qdox.jar"), > new Path("concurrent.jar"), new Path("trove.jar"), new Path("javassist.jar"), > new Path("jboss-aspect-library-jdk50.jar"), new Path("pluggable-instrumentor.jar") > }; > ...the project depencencies could be the same as with original Maven pom.xml of the (JEMS) project against which the plugin is meant. There is a Maven plugin already that makes a virtual eclipse library against the project pom.xml Even without maven plugin installed the depencencies still are self explainatory and there is no need for additional documentation. -- 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-270) Changing Debug configuration name does not update default server preference

by Rob Stryker (JIRA)

[ http://jira.jboss.com/jira/browse/JBIDE-270?page=all ] Rob Stryker closed JBIDE-270. ----------------------------- Resolution: Duplicate Issue JBIDE-211 > Changing Debug configuration name does not update default server preference > --------------------------------------------------------------------------- > > Key: JBIDE-270 > URL: http://jira.jboss.com/jira/browse/JBIDE-270 > Project: JBoss Tools > Issue Type: Bug > Environment: Mac OS X 10.4 > Reporter: Jon Dokulil > > After renaming my JBoss debug configuration name, I get a barrage of Internal Error messages. > The stack trace from my log viewer is as follows: > org.eclipse.debug.core.DebugException: Launch configuration JBoss 4.0.3 at /Users/user/workspace/.metadata/.plugins/org.eclipse.debug.core/.launches/JBoss 4.0.3.launch does not exist. > at org.eclipse.debug.internal.core.LaunchManager.createDebugException(LaunchManager.java:612) > at org.eclipse.debug.internal.core.LaunchManager.getInfo(LaunchManager.java:592) > at org.eclipse.debug.internal.core.LaunchConfiguration.getInfo(LaunchConfiguration.java:349) > at org.eclipse.debug.internal.core.LaunchConfiguration.getAttribute(LaunchConfiguration.java:251) > at org.jboss.ide.eclipse.launcher.core.ServerLaunchManager.isValid(ServerLaunchManager.java:307) > at org.jboss.ide.eclipse.launcher.ui.util.ServerLaunchUIUtil.isLaunchable(ServerLaunchUIUtil.java:268) > at org.jboss.ide.eclipse.launcher.ui.util.ServerLaunchUIUtil.enableServerActions(ServerLaunchUIUtil.java:80) > at org.jboss.ide.eclipse.launcher.ui.actions.StartDefaultServerActionDelegate.enableAction(StartDefaultServerActionDelegate.java:53) > at org.jboss.ide.eclipse.launcher.ui.actions.AbstractDefaultServerActionDelegate.selectionChanged(AbstractDefaultServerActionDelegate.java:110) > at org.eclipse.ui.internal.PluginAction.refreshEnablement(PluginAction.java:200) > at org.eclipse.ui.internal.PluginAction.createDelegate(PluginAction.java:122) > at org.eclipse.ui.internal.WWinPluginAction.refreshActionList(WWinPluginAction.java:160) > at org.eclipse.ui.plugin.AbstractUIPlugin$1.run(AbstractUIPlugin.java:480) > at org.eclipse.swt.widgets.RunnableLock.run(RunnableLock.java:35) > at org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchronizer.java:123) > at org.eclipse.swt.widgets.Display.runAsyncMessages(Display.java:2932) > at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:2715) > at org.eclipse.jface.window.Window.runEventLoop(Window.java:809) > at org.eclipse.jface.window.Window.open(Window.java:787) > at org.eclipse.jface.dialogs.MessageDialog.openError(MessageDialog.java:319) > at org.jboss.ide.eclipse.core.AbstractPlugin.showErrorMessage(AbstractPlugin.java:89) > at org.jboss.ide.eclipse.core.AbstractPlugin.showErrorMessage(AbstractPlugin.java:101) > at org.jboss.ide.eclipse.launcher.ui.actions.ShowLogViewDefaultServerActionDelegate.enableAction(ShowLogViewDefaultServerActionDelegate.java:58) > at org.jboss.ide.eclipse.launcher.ui.actions.AbstractDefaultServerActionDelegate.selectionChanged(AbstractDefaultServerActionDelegate.java:110) > at org.eclipse.ui.internal.PluginAction.refreshEnablement(PluginAction.java:200) > at org.eclipse.ui.internal.PluginAction.createDelegate(PluginAction.java:122) > at org.eclipse.ui.internal.WWinPluginAction.refreshActionList(WWinPluginAction.java:160) > at org.eclipse.ui.plugin.AbstractUIPlugin$1.run(AbstractUIPlugin.java:480) > at org.eclipse.swt.widgets.RunnableLock.run(RunnableLock.java:35) > at org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchronizer.java:123) > at org.eclipse.swt.widgets.Display.runAsyncMessages(Display.java:2932) > at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:2708) > at org.eclipse.jface.window.Window.runEventLoop(Window.java:809) > at org.eclipse.jface.window.Window.open(Window.java:787) > at org.eclipse.jface.dialogs.MessageDialog.openError(MessageDialog.java:319) > at org.eclipse.jface.preference.PreferenceDialog.showPageFlippingAbortDialog(PreferenceDialog.java:1229) > at org.eclipse.jface.preference.PreferenceDialog$8.handleError(PreferenceDialog.java:625) > at org.eclipse.jface.preference.PreferenceDialog$8.selectionChanged(PreferenceDialog.java:640) > at org.eclipse.jface.viewers.StructuredViewer$3.run(StructuredViewer.java:763) > at org.eclipse.core.internal.runtime.InternalPlatform.run(InternalPlatform.java:1044) > at org.eclipse.core.runtime.Platform.run(Platform.java:783) > at org.eclipse.ui.internal.JFaceUtil$1.run(JFaceUtil.java:44) > at org.eclipse.jface.util.SafeRunnable.run(SafeRunnable.java:148) > at org.eclipse.jface.viewers.StructuredViewer.firePostSelectionChanged(StructuredViewer.java:761) > at org.eclipse.jface.viewers.StructuredViewer.handlePostSelect(StructuredViewer.java:1042) > at org.eclipse.jface.viewers.StructuredViewer$5.widgetSelected(StructuredViewer.java:1062) > at org.eclipse.jface.util.OpenStrategy.firePostSelectionEvent(OpenStrategy.java:231) > at org.eclipse.jface.util.OpenStrategy.access$4(OpenStrategy.java:226) > at org.eclipse.jface.util.OpenStrategy$3.run(OpenStrategy.java:392) > at org.eclipse.swt.widgets.RunnableLock.run(RunnableLock.java:35) > at org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchronizer.java:123) > at org.eclipse.swt.widgets.Display.runAsyncMessages(Display.java:2932) > at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:2708) > at org.eclipse.jface.window.Window.runEventLoop(Window.java:809) > at org.eclipse.jface.window.Window.open(Window.java:787) > at org.eclipse.ui.internal.OpenPreferencesAction.run(OpenPreferencesAction.java:66) > at org.eclipse.jface.action.Action.runWithEvent(Action.java:996) > at org.eclipse.jface.action.ActionContributionItem.handleWidgetSelection(ActionContributionItem.java:538) > at org.eclipse.jface.action.ActionContributionItem.access$2(ActionContributionItem.java:488) > at org.eclipse.jface.action.ActionContributionItem$5.handleEvent(ActionContributionItem.java:400) > at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:66) > at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1380) > at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1404) > at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1389) > at org.eclipse.swt.widgets.Widget.notifyListeners(Widget.java:1237) > at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3060) > at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:2712) > at org.eclipse.ui.internal.Workbench.runEventLoop(Workbench.java:1699) > at org.eclipse.ui.internal.Workbench.runUI(Workbench.java:1663) > at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:367) > at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:143) > at org.eclipse.ui.internal.ide.IDEApplication.run(IDEApplication.java:103) > at org.eclipse.core.internal.runtime.PlatformActivator$1.run(PlatformActivator.java:226) > at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:376) > at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:163) > 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:585) > at org.eclipse.core.launcher.Main.invokeFramework(Main.java:334) > at org.eclipse.core.launcher.Main.basicRun(Main.java:278) > at org.eclipse.core.launcher.Main.run(Main.java:973) > at org.eclipse.core.launcher.Main.main(Main.java:948) -- 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-246) XDoclet 4.0.x not auto-generating getters and setters for CMP fields

by Rob Stryker (JIRA)

[ http://jira.jboss.com/jira/browse/JBIDE-246?page=all ] Rob Stryker closed JBIDE-246. ----------------------------- Resolution: Out of Date JIRA cleanup: Closing old issues > XDoclet 4.0.x not auto-generating getters and setters for CMP fields > -------------------------------------------------------------------- > > Key: JBIDE-246 > URL: http://jira.jboss.com/jira/browse/JBIDE-246 > Project: JBoss Tools > Issue Type: Bug > Affects Versions: 1.5 Release Candidate 1 > Environment: Windows XP, JBoss-IDE 1.5RC1, Eclipse 3.1.1 > Reporter: Samuel Richter > > Setting the jboss.net xdoclet module version to version 4.0.x under Window->Preferences->JBoss-IDE->XDoclet breaks the auto-generation of the getters and setters for CMP fields into the local interface. This behavior is not observable for version 3.2.x. -- 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-126) Eclipse IDE fails to recognize XDoclet 1.2.2 doclet subtask

by Rob Stryker (JIRA)

[ http://jira.jboss.com/jira/browse/JBIDE-126?page=all ] Rob Stryker closed JBIDE-126. ----------------------------- Resolution: Out of Date JIRA cleanup: Closing old issues > Eclipse IDE fails to recognize XDoclet 1.2.2 doclet subtask > ----------------------------------------------------------- > > Key: JBIDE-126 > URL: http://jira.jboss.com/jira/browse/JBIDE-126 > Project: JBoss Tools > Issue Type: Bug > Environment: linux Eclipse 3.0.1 JBoss-IDE 1.4.1 > Reporter: Rainer Bieniek > Priority: Minor > > After importing the XDoclet 1.2.2 distribution from sourceforge and installing it into JBoss-IDE (as described in the Wiki page) certain subtasks of the webdoclet task (strutsdynaformvalidation for example) did not show up in the package configuration. > Additionally, declared tags from various subtask didn't show up in the constent assist. > It apperars the subtasks get completely ignored by the JBoss IDE -- 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-202) "Tutorial does not exist"

by Rob Stryker (JIRA)

[ http://jira.jboss.com/jira/browse/JBIDE-202?page=all ] Rob Stryker closed JBIDE-202. ----------------------------- Resolution: Out of Date JIRA Cleanup: Closing Old Bugs > "Tutorial does not exist" > ------------------------- > > Key: JBIDE-202 > URL: http://jira.jboss.com/jira/browse/JBIDE-202 > Project: JBoss Tools > Issue Type: Bug > Affects Versions: 1.5 Milestone 1 > Environment: Problem found on Windows and Linux versions of JBoss IDE 1.5 Milestone 1 > Reporter: Matthew Sell > Priority: Minor > > Attempting to work through the JBoss IDE Tutorial, Selecting new J2EE 1.4 (also happens with 1.3) Project, entering "Tutorial" for the project name (doesn't matter - any name fails), the IDE returns with the following error: > "Error while initializing project - Tutorial does not exist" > Any name, and both the J2EE 1.3 and 1.4 Project wizards fail with this error. -- 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-172) Eclipse crashes when adding a method in FiboBean (tutorial)

by Rob Stryker (JIRA)

[ http://jira.jboss.com/jira/browse/JBIDE-172?page=all ] Rob Stryker closed JBIDE-172. ----------------------------- Resolution: Out of Date JIRA Cleanup: Closing Old Bugs > Eclipse crashes when adding a method in FiboBean (tutorial) > ----------------------------------------------------------- > > Key: JBIDE-172 > URL: http://jira.jboss.com/jira/browse/JBIDE-172 > Project: JBoss Tools > Issue Type: Bug > Environment: Java version: 1.4.2_07,Sun Microsystems Inc. > Java VM: Java HotSpot(TM) Server VM 1.4.2_07-b05,Sun Microsystems Inc. > OS-System: Linux 2.6.8.1-12mdksmp,i386 (Mandrake 10) > HW: Dual channel 2.8Ghz Intel Pentium 4 > 2GB memory > JBoss Eclipse plugin 1.4.1.e31-jre15 > Reporter: vidar haakestad > Priority: Critical > > Are trying the example from JBossIDE Tutorial 'An introduction and walkthrough of JBossIDE 1.4', chapter 4, creating business logic. I get the wizard 'EJB Business Method' launched ok, and starts to fill the wizard with data. > I MISS COMPREHENDING PUSHING THE ADD BUTTON to add a parameter, and just activates the 'Parameters' (text?) box by clicking it with the mouse cursor. Then I start writing exactly what the tutorial specifies in the picture (including the square brackets) and hits the 'Return' key. Then Eclipse crashes whith a dialog specifying the parameters used when it was started (no core file). -- 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-235) Project Packaging - User defined target names

by Rob Stryker (JIRA)

[ http://jira.jboss.com/jira/browse/JBIDE-235?page=all ] Rob Stryker closed JBIDE-235. ----------------------------- Resolution: Done JIRA Cleanup: Closing Old Bugs > Project Packaging - User defined target names > --------------------------------------------- > > Key: JBIDE-235 > URL: http://jira.jboss.com/jira/browse/JBIDE-235 > Project: JBoss Tools > Issue Type: Feature Request > Affects Versions: 1.5 Milestone 2 > Reporter: Gray > > Currently the packaging build feature generates target names in the packaging_build.xml file that are meaningless numbers e.g. N10004 > Not only this but everytime you change any aspect of your project packaging the numbers get regenerated. > This makes it useless for allowing user written ant builds to use these targets. > Please make so that in the Project Packaging settings you can assign a user target name to each artifact. That way any user written ant file can refer to them via a sensible name that does not change each time. -- 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-235) Project Packaging - User defined target names

by Rob Stryker (JIRA)

[ http://jira.jboss.com/jira/browse/JBIDE-235?page=all ] Rob Stryker reopened JBIDE-235: ------------------------------- > Project Packaging - User defined target names > --------------------------------------------- > > Key: JBIDE-235 > URL: http://jira.jboss.com/jira/browse/JBIDE-235 > Project: JBoss Tools > Issue Type: Feature Request > Affects Versions: 1.5 Milestone 2 > Reporter: Gray > > Currently the packaging build feature generates target names in the packaging_build.xml file that are meaningless numbers e.g. N10004 > Not only this but everytime you change any aspect of your project packaging the numbers get regenerated. > This makes it useless for allowing user written ant builds to use these targets. > Please make so that in the Project Packaging settings you can assign a user target name to each artifact. That way any user written ant file can refer to them via a sensible name that does not change each time. -- 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] Resolved: (JBIDE-235) Project Packaging - User defined target names

by Rob Stryker (JIRA)

[ http://jira.jboss.com/jira/browse/JBIDE-235?page=all ] Rob Stryker resolved JBIDE-235. ------------------------------- Resolution: Out of Date JIRA Cleanup: Closing Old Bugs > Project Packaging - User defined target names > --------------------------------------------- > > Key: JBIDE-235 > URL: http://jira.jboss.com/jira/browse/JBIDE-235 > Project: JBoss Tools > Issue Type: Feature Request > Affects Versions: 1.5 Milestone 2 > Reporter: Gray > > Currently the packaging build feature generates target names in the packaging_build.xml file that are meaningless numbers e.g. N10004 > Not only this but everytime you change any aspect of your project packaging the numbers get regenerated. > This makes it useless for allowing user written ant builds to use these targets. > Please make so that in the Project Packaging settings you can assign a user target name to each artifact. That way any user written ant file can refer to them via a sensible name that does not change each time. -- 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-227) Cookbook: Create examples that are specific to JBoss

by Rob Stryker (JIRA)

[ http://jira.jboss.com/jira/browse/JBIDE-227?page=all ] Rob Stryker closed JBIDE-227. ----------------------------- Resolution: Done JIRA cleanup: Closing old bugs > Cookbook: Create examples that are specific to JBoss > ---------------------------------------------------- > > Key: JBIDE-227 > URL: http://jira.jboss.com/jira/browse/JBIDE-227 > Project: JBoss Tools > Issue Type: Feature Request > Reporter: Marshall Culpepper > > Overall, I find the target of this cookbook to be too generic. Its fine as background for the jboss plugins, but What I was looking for is how to extend the JBossIDE functions. > Some simple example plugins that could be covered include: > - jndi viewer for a jboss server > - jmx viewer for a jboss server > - jndi.properties editor for ejb/ejb3 projects -- 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