Issue pulling from maven

[mrvisser]

It looks like there's an issue when I try and include this into an SBT project:

[warn] io problem while parsing ivy file: https://repo1.maven.org/maven2/com/circonus/metrics-circonus/1.0.0/metrics-circonus-1.0.0.pom: Impossible to load parent for file:/Users/branden/.ivy2/cache/com.circonus/metrics-circonus/ivy-1.0.0.xml.original. Parent=com.circonus#metrics-circonus-parent;1.0.0
[info] Resolving com.circonus#metrics-circonus-parent;1.0.0 ...
[warn] io problem while parsing ivy file: http://maven.openimaj.org/com/circonus/metrics-circonus/1.0.0/metrics-circonus-1.0.0.pom: Impossible to load parent for file:/Users/branden/.ivy2/cache/com.circonus/metrics-circonus/ivy-1.0.0.xml.original. Parent=com.circonus#metrics-circonus-parent;1.0.0
[warn]  module not found: com.circonus#metrics-circonus;1.0.0
[warn] ==== local: tried
[warn]   /Users/branden/.ivy2/local/com.circonus/metrics-circonus-parent/1.0.0/ivys/ivy.xml
[warn] ==== public: tried
[warn]   https://repo1.maven.org/maven2/com/circonus/metrics-circonus-parent/1.0.0/metrics-circonus-parent-1.0.0.pom
[warn] ==== Apache Snapshots: tried
[warn]   https://repository.apache.org/content/groups/snapshots/com/circonus/metrics-circonus-parent/1.0.0/metrics-circonus-parent-1.0.0.pom1.0.0.pom

Does the *-parent need to be published as well somehow? My build.sbt entry looks like this:

"com.circonus" % "metrics-circonus" % "1.0.0"

[mrvisser]

It's possible this is an SBT issue, but since this is a fairly new publish, just wanted to sanity check that things are expected to be working at this point.

[postwait]

I'll take a look. This was my first publish to maven ever. I probably screwed something up.

[mrvisser]

Thanks. This, although and old issue, might be relevant wrt to SBT <-> maven interoperability with parents: sbt/sbt#1690

I'll try a few more things on the sbt side of things.

[mrvisser]

When I install this repo locally, I was able to successfully include metrics-circonus. It found the metrics-circonus-parent POM in my local repository at that point.

So, I think if that POM gets published to sonatype (assuming it was supposed to?) through your publish workflow, then it should resolve the issue.

[postwait]

I just updated this, can you let me know if it is working for you now?