run_jetty_run.WEB_CONTEXT_CLASSPATH_NON_CHECKED should store relative paths

[GoogleCodeExporter]

What is the expected output? What do you see instead?

Relative paths should be stored in 
run_jetty_run.WEB_CONTEXT_CLASSPATH_NON_CHECKED in the launch file. With 
projects of multiple developers and the launch file is shared among them, 
absolute paths only work for one person who set up the script.

What steps will reproduce the problem?
1. Configure a launch script
2. Add test classes in Webapp Classpath
3. Open the launch file in a text editor
4. Check paths in the WEB_CONTEXT_CLASSPATH_NON_CHECKED key.

What Eclipse version are you using ?

3.7

What Run-Jetty-Run version are you using?

1.3.3

What OS are you using ? 32bit or 64 bit?

Win7 64-bit

Original issue reported on code.google.com by tiendung.tran on 9 Apr 2012 at 11:47

[GoogleCodeExporter]

I was thinking this issue when I implemented it, 
but it's hard to store as a relative path,
since we have a very dynamic classpath in this case.

We are hard to identify those items without absolute path in currently 
implementation.

A classpath entry could be anything and could be changed from maven or any 
possible container resolver.

The classpath management will not support relative path due to the limitation.

The test-classes one is a reasonable one , that's the only one do some 
assumption,
I will get the "default enable test-classes" option back in next release.

Original comment by tonylovejava on 10 Apr 2012 at 8:44

[GoogleCodeExporter]

But with absolut paths it's not possible to commit the launch config to an VCS 
:-(

Original comment by mattelac...@gmail.com on 24 Jul 2012 at 9:33