We planned to have a Maven plugin for non-leiningen workflows however the issue is more pressing.
Consider: A->B->C. "A" is a normal project not using voom. Developers using "A" are not using voom. "B" uses voom and points to voom version of "C". With the current model, there's no point for voom to get involved.
If we have a maven plugin, "B" can include that maven plugin and do the right sort of dependency work (build-deps) to get "C".
We planned to have a Maven plugin for non-leiningen workflows however the issue is more pressing.
Consider: A->B->C. "A" is a normal project not using voom. Developers using "A" are not using voom. "B" uses voom and points to voom version of "C". With the current model, there's no point for voom to get involved.
If we have a maven plugin, "B" can include that maven plugin and do the right sort of dependency work (build-deps) to get "C".