Mailing-List: contact dev-help@reef.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@reef.apache.org
MIME-Version: 1.0
In-Reply-To: <568D71F0.3050603@weimo.de>
References: 
 <CAPCBsnN+AAWxAbnJ6Bfu+XMSOyNBsUtStowNY5_Q_nv2tByzQw@mail.gmail.com>
	<568D5D8F.1060805@weimo.de>
	<CAPCBsnM+vo9aBY1Le7AnfsgdJs48X4rtMJ48_vLJQuGJYhW3jw@mail.gmail.com>
	<568D71F0.3050603@weimo.de>
Date: Wed, 6 Jan 2016 15:10:24 -0800
Message-ID: 
 <CAPCBsnOj-v2Ce3v-5N80=3FwBPkw1Ve7b9Lmf+CJtZm2UbmvCg@mail.gmail.com>
Subject: Re: Maven snapshot repo
From: Tobin Baker <tdbaker@cs.washington.edu>
To: dev@reef.apache.org
Content-Type: multipart/alternative; boundary=001a1135fe9a8db71b0528b2756c

--001a1135fe9a8db71b0528b2756c
Content-Type: text/plain; charset=UTF-8

I just want to be sure that we aren't blocked waiting for fixes to be
merged upstream, that's all :) I'm using the technique described here:
http://stackoverflow.com/a/14013645. There's also https://jitpack.io/,
which is actually designed for this purpose (and is free for public repos),
but I'd like to avoid a dependency on a random startup if possible :)


On Wed, Jan 6, 2016 at 11:58 AM, Markus Weimer <markus@weimo.de> wrote:

> On 2016-01-06 10:40, Tobin Baker wrote:
>
>> I've already set up a private maven repo tracking our REEF fork (by
>> abusing the github pages maven plugin).
>>
>
> You have me curious there. What are you doing?
>
> Markus
>

--001a1135fe9a8db71b0528b2756c--