Assign and List directive fixes and tests

actually sourcepath in JDT classpathentries always use hard coded paths, even if maven downloads it automatically.
For regular Java projects, this is transparent because classpath entry attributes are stored locally within the maven classpath library. For other kind of projects were the entry shows up directly in the .classpath file, you'll always see hardcoded paths. 

So removing sourcepath from .classpath is better, from a SCM perspective, but then it means developers need some extra discipline to not push .classpath when sourcepaths are modified and deal with merges when necessary.