Resolving paths from pom project produces wrong result
Description
When resolving a :git/url dependency with :deps/manifest om the resulting vector for aths is a list where the first entry consists of the sourceDirectory of the pom of the dependency. This path is nonexistent since the sourceDirectory is (most likely) relative to the dependency but it is made absolute in the current directory which is in the dependent project.
An example usage of coord-paths to make it more clear:
Here ${project.basedir}/src/main/java is the default value, when no sourceDirectory is specified in the pom.xml. It is clear that that path, which finds it's way into the classpath, is not valid. If a (relative) path would be present in the pom.xml, the first entry of the list could be something like "/path/to/dependent/project/src/main/clojure" which might exist, but is not the path to the sources of the dependency.
Also note that the output of coord-paths is a seq and not a vector.
Major
When resolving a
:git/urldependency with:deps/manifestomthe resulting vector forathsis a list where the first entry consists of thesourceDirectoryof the pom of the dependency. This path is nonexistent since thesourceDirectoryis (most likely) relative to the dependency but it is made absolute in the current directory which is in the dependent project.An example usage of
coord-pathsto make it more clear:Here
${project.basedir}/src/main/javais the default value, when nosourceDirectoryis specified in the pom.xml.It is clear that that path, which finds it's way into the classpath, is not valid. If a (relative) path would be present in the pom.xml, the first entry of the list could be something like
"/path/to/dependent/project/src/main/clojure"which might exist, but is not the path to the sources of the dependency.Also note that the output of
coord-pathsis a seq and not a vector.