Eclipse keeps changing the Targeted Runtimes


Eclipse keeps changing the Targeted Runtimes



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

Run Config




Does Spring-MVC annotation based bean validation support for collection-based property ? (Spring-MVC)

1:



Spring 2 Hibernate Annotation
Changing the target runtime will not change where your run configuration points..
Two approaches of task distribution in a multi tier application
You need to go into your Run/Debug configuration and change the execution environment there to point to the desired target..
What's the most AGILE APPROACH to validate Spring-MVC command (speeds up validation implementation on server side) ? (Spring-MVC)
Personally, I think this behaviour is confusing.


ConstraintViolationException VS DataIntegrityViolationException
I recommend filing a bug against Eclipse to make this easier to use..
Testing an AspectJ Aspect


map url to controller


Can't set LevelRangeFilter for log4j

2:


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..



70 out of 100 based on 80 user ratings 430 reviews