Found this problem testing with the
driver today, when adding a jar dependency to a WAR from a jar within an
EAR (Very common scenario),
Was getting a problem where the ClassPath
entry din't have an absolute path, and was getting jdt exceptions.
This simple fix checks to make sure
the path is absolute before creating these new entries.