Good to hear!
On Wed, Sep 18, 2013 at 6:10 PM, Daan Hoogland wrote:
> Thanks Dave,
>
> I still had the google docs in the proxy and it has the same id, now
> both the new and the old are in our cache.
>
> regards,
> Daan
>
> On Tue, Sep 17, 2013 at 3:21 AM, Dave Cahill wrote:
> > Daan,
> >
> >
Thanks Dave,
I still had the google docs in the proxy and it has the same id, now
both the new and the old are in our cache.
regards,
Daan
On Tue, Sep 17, 2013 at 3:21 AM, Dave Cahill wrote:
> Daan,
>
> Yes, that's the right location. For example, the client jar file is at:
> http://cs-maven.mi
Daan,
Yes, that's the right location. For example, the client jar file is at:
http://cs-maven.midokura.com/releases/org/midonet/midonet-client/1.1.0/midonet-client-1.1.0.jar
If you add http://cs-maven.midokura.com/releases as a 3rd-party repo in
your Sonar repo, it should work fine.
Thanks,
Dave
http://cs-maven.midokura.com/releases/ is the right location, right? I
get a blank page there (no pom or jar) or is it somewhere else?
On Mon, Sep 16, 2013 at 3:17 PM, Dave Cahill wrote:
> Copying part of the IM conversation just now in case anyone else has the
> same question.
>
> As Prasanna me
Copying part of the IM conversation just now in case anyone else has the
same question.
As Prasanna mentioned in this thread [1]:
"If you are using a nexus proxy in the way of your build, you'll have
to add a 3rd party repo and the jars will be automatically indexed and
downloaded."
Thanks,
Dave.
H Dave,
I noticed some mails on this but did not find a workaround; I am
trying to build master and it looks for midonet-client 1.1.0. I have
removed it from the plugins pom file. Next I do want to test with
midonet however as it touches networks what I am doing. Do you have
some advice on how to
