classpath resolver fails
Status: Beta
Brought to you by:
thred
the classpath resolver fails if the classpath is combined from multiple sources.
e.g. a templates lies in the target/classes path. it gets loaded and by an url like file://target/classes/whatever. It includes another relative template that lies in a jar file. the resolver can't find it now because it modified the file path instead of the classpath reference.
Tried to fix it, but it still lacks the prove. It's difficult to design a test case for it.