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: 
 <CABwccFFyA8Fh-ZzE3-PzuKGqzXveBysmOjAO7U1BEZ9e9tJ6kQ@mail.gmail.com>
References: 
 <CAF1jEfBPdVvhYLsG=pJuH55RjoL5aWs0nQerS4VCtrPh=T3rfw@mail.gmail.com>
	<527D312D.7090700@gmail.com>
	<CABwccFFyA8Fh-ZzE3-PzuKGqzXveBysmOjAO7U1BEZ9e9tJ6kQ@mail.gmail.com>
Date: Fri, 8 Nov 2013 15:12:56 -0500
Message-ID: 
 <CAL5zq9Znk4=3gxJCPeuXOxwA886tMOZrw9JvXhwrGd4DrXHowQ@mail.gmail.com>
Subject: Re: [VOTE] add mvn dependency:analyze to release process
From: Christopher <ctubbsii@apache.org>
To: Accumulo Dev List <dev@accumulo.apache.org>
Content-Type: text/plain; charset=UTF-8

+1 for an explicit check to be added to the release process.
(however, these dependency issues should really be regularly checked
and considered throughout development whenever dependencies are
added/removed).

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


On Fri, Nov 8, 2013 at 1:51 PM, Sean Busbey <busbey+ml@clouderagovt.com> wrote:
> On 11/8/13, 1:35 PM, Billie Rinaldi wrote:
>
>>  I would like to add a dependency clean up step (which can be assisted by
>>> running mvn dependency:analyze) to our release process for major and minor
>>> releases, to make sure direct dependencies are declared and any stale
>>> dependencies are removed.
>>>
>>> This vote will end in 72 hours.
>>>
>>> [ ] +1 Add dependency clean up step
>>> [ ] +0
>>> [ ] -1 Do not add dependency clean up because ...
>>>
>>>
> +1 (non-binding)
>
>
> --
> Sean