Mailing-List: contact dev-help@accumulo.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@accumulo.apache.org
MIME-Version: 1.0
In-Reply-To: 
 <CAJRvFdowCX6AFm11NApL+1NSvj8nsUt=G50WqfnM-Ryp4VpOaQ@mail.gmail.com>
References: 
 <CAJRvFdowCX6AFm11NApL+1NSvj8nsUt=G50WqfnM-Ryp4VpOaQ@mail.gmail.com>
Date: Fri, 4 Oct 2013 17:51:29 -0400
Message-ID: 
 <CAL5zq9Z5OYNERm+XiAcy_z++VY0fQDXUdD8AQHqnggOQq6GRNQ@mail.gmail.com>
Subject: Re: jenkins deploy snapshots
From: Christopher <ctubbsii@apache.org>
To: Accumulo Dev List <dev@accumulo.apache.org>
Content-Type: text/plain; charset=UTF-8

Just deploy to a staging repo using your Apache credentials, as though
you were building a release candidate (but without promoting it or
calling a vote).

--
Christopher L Tubbs II
http://gravatar.com/ctubbsii


On Wed, Oct 2, 2013 at 6:45 PM, Mike Drob <mdrob@mdrob.com> wrote:
> Can we configure jenkins to deploy snapshots on every build? I assume there
> is an apache snapshots repository that we can use for this purpose. Maybe
> this was previously turned off for some reason that I am not aware of.
>
> It's somewhat annoying to build the whole project when i am making changes
> in just one module because it has sibling dependencies. The only two
> solutions look like deploying snapshots or mvn install, which is bad for a
> variety of other reasons.
>
> Christopher, I know you generally have opinions about maven things, and
> would be interested in your thoughts on this.
>
> Mike