Cannot launch JBoss in Eclipse 3.1M7

[mazz]

Eclipse 3.1M7 was just released tonight. I installed and when I tried to launch a JBoss instance via JBoss Eclipse IDE (from the Debug drop down button), I get the following error and JBoss does not start:

java.lang.NoSuchMethodError: org.eclipse.jdt.internal.launching.LaunchingMessages.getString(Ljava/lang/String;)Ljava/lang/String;
 at org.jboss.ide.eclipse.launcher.core.configuration.ServerLaunchConfigurationDelegate.launchInternal(ServerLaunchConfigurationDelegate.java:148)
 at org.jboss.ide.eclipse.launcher.core.configuration.ServerLaunchConfigurationDelegate.launch(ServerLaunchConfigurationDelegate.java:102)
 at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:590)
 at org.eclipse.debug.internal.core.LaunchConfiguration.launch(LaunchConfiguration.java:515)
 at org.eclipse.debug.internal.ui.DebugUIPlugin.buildAndLaunch(DebugUIPlugin.java:734)
 at org.eclipse.debug.internal.ui.DebugUIPlugin$6.run(DebugUIPlugin.java:932)
 at org.eclipse.core.internal.jobs.Worker.run(Worker.java:67)

Looks like they changed something on you.

[maxandersen]

yeah we love them.

[tbech]

quick patch possible?

[maxandersen]

yes - install M6 ;)

[squeak]

In all seriousness, are you looking to put a patch out for M7, or are you going to wait the 6 weeks for the final candidate to come out?

[maxandersen]

since we are now dependent on WTP we cannot just put out a simple patch since WTP only works on M6 for now.

[squeak]

Ok, makes sense. If I stick with M7, guess I will try to build my own launch config with the right jars in the classpath (always fun!).

Thanks

[tbech]

Maybe we can use this:
- Eclipse plan for 3.1 says that M6 is the milestone with API freeze;
- so obviously they broke the API in M7 (or Jboss IDE uses something undocumented, or wrongly the API - I doubt in it)

They (eclipse) plans are: 27 May Fri 00:10 EDT Release Candidate 1 build

So someone from officials from JBoss can issue serious anomaly and maybe hopefully it will be fixed on 27 (or sooner in night/integration eclipse build).

What you think?

[maxandersen]

both jboss ide and WTP uses internal api's of Eclipse 3.1 .... thats unfortunately life at the moment.

[tbech]

ok, I didn't know.
Ahh, I like M7 for its perfomance, but it is life...

[tbech]

I did quick patch, see:
http://sourceforge.net/tracker/index.php?func=detail&aid=1204122&group_id=22866&atid=376687

I just use 'Server Navigator' view from IDE, so patch is only for it.

[maxandersen]

We will do a JBossIDE M6 release soon as WTP is dependent on.

ASAP after that we hope we can start doing daily builds which hopefully quickly can get up to M7 performance heaven ;)

Thanks for the patch, but please also provide the source and put it in our JBoss JIRA (patches and bugtracker at sf.net are closed)

[jmendez]

Patch does not work...

[mmindenhall]

The patch worked for me. You need to CREATE your Default Server configuration (in the Debug menu) using M6 (hopefully you haven't deleted it yet!). Once you have it working the way you want in M6, then switch over to M7 using the same location for your eclipse workspace. Now you should be able to launch from within M7. However, you still can't go edit your debug configuration, or any of the JBoss IDE preferences. The patch only works for the Default Server buttons on the toolbar and the Server Navigator view.

[rupert]

"tbech" wrote:
I did quick patch, see:
http://sourceforge.net/tracker/index.php?func=detail&aid=1204122&group_id=22866&atid=376687

I just use 'Server Navigator' view from IDE, so patch is only for it.

Bless you my son! Works a treat in RC1.

If you don't want to keep M6-- anround, it's simple enough to copy/edit/adapt the .launch configuration in <eclipse_workspace>\.metadata\.plugins\org.eclipse.debug.core\.launches (I tend to copy these over manually in any case, each time I upgrade to a newer version...).