2

We're using Eclipse 3.4.1 with SpringSource dm Server 1.0. There are two Targeted Runtimes defined (Project / Properties / Targeted Runtimes).

The one we setup is called

SpringSource dm Server (Runtime) v1.0

There is one pre-defined called

SpringSource v1.0

We find that, even though we select SpringSource dm Server (Runtime) v1.0, Eclipse seems to frequently change the Targeted Runtime back to SpringSource v1.0.

Yes, we click Apply and OK on the properties screen.

Anyone seen that before? Any idea how to fix it?

EDIT

Here are images of our Targeted Runtimes and Run Configuration screens.

Targeted Runtime http://johannsen.us/SO/TargetedRuntime.png

Run Config http://johannsen.us/SO/RunConfig.png

Eric J.
  • 147,927
  • 63
  • 340
  • 553
  • Looks a bit similar to http://dev.eclipse.org/newslists/news.eclipse.newcomer/msg29365.html (without any clear solution). Do you have tried with Galileo (eclipse3.5)? – VonC Jul 31 '09 at 18:21

2 Answers2

1

Changing the target runtime will not change where your run configuration points.

You need to go into your Run/Debug configuration and change the execution environment there to point to the desired target.

Personally, I think this behaviour is confusing. I recommend filing a bug against Eclipse to make this easier to use.

Francis Upton IV
  • 19,322
  • 3
  • 53
  • 57
  • Could you clarify where exactly to change the Run/Debug configuration? The only Run configuration I see seems to be pointed to the correct runtime. I have attached screenshots to my original question. – Eric J. Sep 28 '09 at 17:59
  • Oh, actually I was answering a question thinking about the Java JRE instead of the target runtimes. I don't know for sure, but I think the target runtimes have the same issue. Your 2nd screenshot would be where you change it in the drop down list. Are you sure that changing the project preferences is having any effect on the run configuration? I would expect it not to. If it is changing it sometimes and not others, you should file a bug about this. – Francis Upton IV Sep 28 '09 at 18:53
0

The problem was that the POM file specified a name of SpringSource v1.0, while the Eclipse runtime environment only had a server defined with the name SpringSource dm Server (Runtime) - which is the default name suggested by Eclipse when creating the server.

Defining a server with a name of SpringSource v1.0, matching what is stated in the POM, resolved the issue.

Eric J.
  • 147,927
  • 63
  • 340
  • 553