views:

15

answers:

0

Hi all,

I would like to add my Eclipse .launch files for JUnit tests to source control, but it doesn't work because I often checkout the containing project with a different name than it was committed under. The Eclipse .launch files for JUnit tests contain an attribute "org.eclipse.jdt.launching.PROJECT_ATTR", which seems to support no reference to the project containing the .launch file. The External Tool .launch files support this, but apparently Java executables do not. So I am forced to open all my dozens of JUnit .launch files and change the project name to match the project that they are currently sitting in... and of course I have to avoid committing this change, because the value is different for each developer sharing the .launch files.

It really seems like this is a modeling error in Eclipse, to require a hardcoded project name in the .launch file's content. Does anyone know of a way to explain to Eclipse that the project to use is the project that the .launch file is sitting inside of? Thanks for your help.