search

LonoCloud / lein-voom

Tool for generating artifacts versioned on the most recent git commit sha and commit time.
Eclipse Public License 2.0
97 stars 14 forks source link

Voom version detection logic gets confused with datomic-pro #18

Open abrooks opened 10 years ago

abrooks commented 10 years ago

When running lein voom build-deps on a project with this dependency:

[datomic-pro "0.9.4532"]

Yields this error:

Did not find, will build  {:version 0.9.4532, :artifactId datomic-pro, :groupId com.datomic}
Failed to resolve dependency: Not parseable as voom-version: 0.9.4532
{:exception-data
 {:artifact
  {:version "0.9.4532",
   :artifactId "datomic-pro",
   :groupId "com.datomic"}}}
abrooks commented 10 years ago

The com.datomic/datomic-pro "0.9.4532" artifact is present in the ~/.m2/repository and lein deps runs happily.

sradack commented 7 years ago

For what it's worth, I encountered a similar error. It turned out to be a write permission issue in the local .m2 Maven repository for a non-voom package. In other words, it's not really a voom error. I didn't dig into the voom code, but perhaps it's possible that voom is trying to handle the error related to lein's inability to download/write the artifact by treating it like a voom dependency.