Support for eclipse 3.1

[raghavendra.vaidya]

Jboss IDE does not work with eclispe 3.1RC1....here is the exception it throws...

java.lang.NoSuchMethodError: org.eclipse.jdt.internal.debug.ui.launcher.LauncherMessages.getString(Ljava/lang/String;)Ljava/lang/String;
at org.jboss.ide.eclipse.launcher.ui.configuration.ServerLaunchArgumentsTab.createControl(ServerLaunchArgumentsTab.java:86)
at org.eclipse.debug.internal.ui.launchConfigurations.LaunchConfigurationTabGroupViewer.showTabsFor(LaunchConfigurationTabGroupViewer.java:720)
at org.eclipse.debug.internal.ui.launchConfigurations.LaunchConfigurationTabGroupViewer.showInstanceTabsFor(LaunchConfigurationTabGroupViewer.java:639)
at org.eclipse.debug.internal.ui.launchConfigurations.LaunchConfigurationTabGroupViewer.displayInstanceTabs(LaunchConfigurationTabGroupViewer.java:519)
at org.eclipse.debug.internal.ui.launchConfigurations.LaunchConfigurationTabGroupViewer$5.run(LaunchConfigurationTabGroupViewer.java:471)
at org.eclipse.swt.custom.BusyIndicator.showWhile(BusyIndicator.java:69)
at org.eclipse.debug.internal.ui.launchConfigurations.LaunchConfigurationTabGroupViewer.inputChanged(LaunchConfigurationTabGroupViewer.java:488)
at org.eclipse.debug.internal.ui.launchConfigurations.LaunchConfigurationTabGroupViewer.setInput(LaunchConfigurationTabGroupViewer.java:452)
at org.eclipse.debug.internal.ui.launchConfigurations.LaunchConfigurationsDialog.handleLaunchConfigurationSelectionChanged(LaunchConfigurationsDialog.java:788)
at org.eclipse.debug.internal.ui.launchConfigurations.LaunchConfigurationsDialog$3.selectionChanged(LaunchConfigurationsDialog.java:600)
at org.eclipse.jface.viewers.StructuredViewer$3.run(StructuredViewer.java:763)
at org.eclipse.core.internal.runtime.InternalPlatform.run(InternalPlatform.java:1038)
at org.eclipse.core.runtime.Platform.run(Platform.java:775)
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.setSelection(StructuredViewer.java:1453)
at org.eclipse.jface.viewers.Viewer.setSelection(Viewer.java:379)
at org.eclipse.debug.internal.ui.launchConfigurations.LaunchConfigurationView.handleConfigurationAdded(LaunchConfigurationView.java:270)
at org.eclipse.debug.internal.ui.launchConfigurations.LaunchConfigurationView.launchConfigurationAdded(LaunchConfigurationView.java:251)
at org.eclipse.debug.internal.core.LaunchManager$ConfigurationNotifier.run(LaunchManager.java:1581)
at org.eclipse.core.internal.runtime.InternalPlatform.run(InternalPlatform.java:1038)
at org.eclipse.core.runtime.Platform.run(Platform.java:775)
at org.eclipse.debug.internal.core.LaunchManager$ConfigurationNotifier.notify(LaunchManager.java:1605)
at org.eclipse.debug.internal.core.LaunchManager.launchConfigurationAdded(LaunchManager.java:806)
at org.eclipse.debug.internal.core.LaunchConfigurationWorkingCopy.writeNewFile(LaunchConfigurationWorkingCopy.java:278)
at org.eclipse.debug.internal.core.LaunchConfigurationWorkingCopy.doSave0(LaunchConfigurationWorkingCopy.java:233)
at org.eclipse.debug.internal.core.LaunchConfigurationWorkingCopy.doSave(LaunchConfigurationWorkingCopy.java:174)
at org.eclipse.debug.internal.ui.launchConfigurations.CreateLaunchConfigurationAction.performAction(CreateLaunchConfigurationAction.java:75)
at org.eclipse.debug.internal.ui.launchConfigurations.AbstractLaunchConfigurationAction$1.run(AbstractLaunchConfigurationAction.java:103)
at org.eclipse.swt.custom.BusyIndicator.showWhile(BusyIndicator.java:69)
at org.eclipse.debug.internal.ui.launchConfigurations.AbstractLaunchConfigurationAction.run(AbstractLaunchConfigurationAction.java:106)
at org.eclipse.debug.internal.ui.launchConfigurations.LaunchConfigurationsDialog$ButtonActionNew.run(LaunchConfigurationsDialog.java:1460)
at org.eclipse.debug.internal.ui.launchConfigurations.LaunchConfigurationsDialog$1.widgetSelected(LaunchConfigurationsDialog.java:1429)
at org.eclipse.swt.widgets.TypedListener.handleEvent(TypedListener.java:89)
at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:66)
at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:844)
at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:2929)
at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:2562)
at org.eclipse.jface.window.Window.runEventLoop(Window.java:809)
at org.eclipse.jface.window.Window.open(Window.java:787)
at org.eclipse.debug.internal.ui.launchConfigurations.LaunchConfigurationsDialog.open(LaunchConfigurationsDialog.java:438)
at org.eclipse.debug.ui.DebugUITools$1.run(DebugUITools.java:356)
at org.eclipse.swt.custom.BusyIndicator.showWhile(BusyIndicator.java:69)
at org.eclipse.debug.ui.DebugUITools.openLaunchConfigurationDialogOnGroup(DebugUITools.java:360)
at org.eclipse.debug.ui.DebugUITools.openLaunchConfigurationDialogOnGroup(DebugUITools.java:302)
at org.jboss.ide.eclipse.launcher.ui.views.ServerNavigator.doConfiguration(ServerNavigator.java:162)
at org.jboss.ide.eclipse.launcher.ui.views.ServerNavigator$10.run(ServerNavigator.java:757)
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:844)
at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:2929)
at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:2562)
at org.eclipse.ui.internal.Workbench.runEventLoop(Workbench.java:1694)
at org.eclipse.ui.internal.Workbench.runUI(Workbench.java:1658)
at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:366)
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:375)
at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:162)
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.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)

!ENTRY org.eclipse.jface 4 2 2005-06-06 11:56:07.625
!MESSAGE Problems occurred when invoking code from plug-in: "org.eclipse.jface".
!STACK 0

[gsaman1234]

This topic is getting old.... any concrete reply from the IDE team?

Thanks,
Sam

[willimur]

I'm sure it'll be done as soon as possible and our nagging only serves to make the developers more stressed-out.

Although if we want to play the role of "pundit" as wager a guess as to the internal plans, I can't help but notice that the Eclipse people have a formal goal of releasing the final release of Eclipse 3.1 the week of June 27th. Between you and me, I'm guessing the JBossIDE developers are going to at least fix the current "broken" issue here by then.

A question I would ask (if any of the developers are out there reading this) would be if the fixes are happening in parallel with the code base for the JBossIDE 1.4 and 1.5 series, and if a developer wanting to do JBoss 4.0.2 / Hibernate3 development (which as you know uses Hibernate3 now) with Eclipse 3.1 should tend toward the 1.4 "stable" series (since that series has the word "stable" attached to it) or the 1.5 "development" series (in case it may be better suited for the Hibernate3 components).

There's actually nothing on the web pages anymore that give a good picture of the difference between 1.4 and 1.5, especially info that might help a user decide which is better suited to his or her needs.

[pgandert]

Hello

I am a bloody newby in the JBoss-stuff and wanted to make a start with JBoss using the IDE; but there is a stop.

Also Problems with JBossIDE in Eclipse 3.1RC1.

1 )When trying to create a new J2EE-Project:

The selected wizard couldnot be started.

Reason:

org.eclipse.jdt.internal.ui.wizards.NewWizardMessages.getString(Ljava/lang/String;)Ljava/lang/String;

2) When trying to enter the Preferences of JBossIDE:

Plug-in org.jboss.ide.eclipse.deployer.ui was unable to load class org.jboss.ide.eclipse.deployer.ui.preferences.MainPreferencePage.

Any tips or tricks there?

Thanks
Peter G.

System:
Eclipse3.1RC1
JDK:1.4.2.03
Windows XP-Home
JBossIDE-1.4.1-jre1.4-e31.zip

[pgandert]

Just for information....

I also have tested the eclipse3.1RC3.
The problem is still the same.

Peter G.

[robdaemon]

"pgandert" wrote:
I also have tested the eclipse3.1RC3.
The problem is still the same.

FYI: The problem is not really JBossIDE's fault. Eclipse changed the API.

As soon as Eclipse WST gets updated, JBossIDE can be updated. Their roadmap says July 1, so after that, JBossIDE can be fixed. See http://www.eclipse.org/webtools/development/planning/milestone_plan_1_0.html for the Eclipse WST roadmap.

No, I don't work for JBoss. I just keep seeing the same post over and over and over and over. I'm betting the reason that you haven't seen an official reply is because there have been a few official replies, and they're getting tired of answering the same question repeatedly.

[pgandert]

Hi robdeamon, Hi all

I have solved the problem by installing eclipse3.1M6; and it works fine... ;-)
This environment is enough for taking my first steps in jBoss.

My research resulted in the cognition, that there was an API-Change in Eclipse starting with 3.1M7. This was in the webtools-module.

I have no problem with that, though eclipse3.1RC3 has some nice enhancements.
And i can understand the jBoss-people, that they are tired of the same question everytime.
I can also understand, that they want to wait for the stable release of Eclipse 3.1/WST, when the API is freezed.

Because of this at jBoss i would take this specific problem into the FAQ, which i have studied before posting; just an idea.... ;-)
I think, most people are studying the FAQ before posting.

But it was still a good point of learning something about the structure of eclipse and the interaction between plugins and the core of eclipse.

Peter G.

[beeblebrox]

Just bump up...

[hrogge]

"robdaemon" wrote:
FYI: The problem is not really JBossIDE's fault. Eclipse changed the API.

If JBoss used an internal API it IS JBoss fault that it is broken now. Internal APIs can change any time because they are not built to be used from outside their plugin.