Joe,
I've verified that the version of the pom in the apache releases repo works
for me (but it still has this issue:
https://issues.apache.org/jira/browse/KAFKA-978).
Thanks,
Jason
On Wed, Jul 24, 2013 at 10:37 AM, Jason Rosenberg wrote:
> Joe,
>
> Unfortunately, I'm not sure I have an easy
Joe,
Unfortunately, I'm not sure I have an easy way to add that repo to our
build system, since we use a proxy for maven resolution. I'm not seeing an
easy way to add that repo, without it overriding everything in maven
central (which maybe is ok, but I'm not sure).
It does look like that versio
For any Ivy people looking for a workaround, here is an ivysettings.xml
that will resolve from Apache repos
https://gist.github.com/mumrah/6070548
On 7/24/13 6:01 AM, Joe Stein wrote:
Hi Jason, can you please try using
https://repository.apache.org/content/repositories/releases as a repositor
Hi Jason, can you please try using
https://repository.apache.org/content/repositories/releases as a repository
until the beta2 release and confirm that works for you so we know the next
beta will fix things before the 0.8.0 release. Thanks!
/***
Joe Stein
Sorry, I realize now what I am observing here was discussed in a previous
thread. Although I'm a bit different, in that I'm just trying to use
straight maven (no sbt or gradle, etc.). Anyway, the pom in maven central
is invalid, and should probably be removed, I should think.
Jason
On Wed, Jul
I have been using a pom file for 0.8.0 that I hand-edited from the one
generated with sbt make:pom. Now that there's a version up on maven
central, I'm trying to use that.
It looks like the pom file hosted now on maven central, is invalid for
maven?
I'm looking at this:
http://search.maven.org/r
