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: 
 <CAJRvFdqb2OagRe1nHTKiL3v_K=4PTj4yY5oGwLu4mAgRCy5U2A@mail.gmail.com>
References: 
 <CAF1jEfB6BwY5_78=9BaUJtSp5bkLCw=rgV84DE9FqADyfxB_=Q@mail.gmail.com>
	<CAJRvFdqb2OagRe1nHTKiL3v_K=4PTj4yY5oGwLu4mAgRCy5U2A@mail.gmail.com>
Date: Fri, 8 Nov 2013 15:16:06 -0500
Message-ID: 
 <CAL5zq9aJagEDOtiO--=1AutcBND2JJvPe7AMbLdO0Us4HJUA1A@mail.gmail.com>
Subject: Re: mvn dependency:analyze
From: Christopher <ctubbsii@apache.org>
To: Accumulo Dev List <dev@accumulo.apache.org>
Content-Type: text/plain; charset=UTF-8

We won't be able to get rid of all the resulting warnings. So,
automating it would probably just encourage people to ignore these
warnings instead of address them. I'd rather just make it a point to
explicitly check during testing before releasing, and to encourage
people to consider dependencies throughout development.

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


On Fri, Nov 8, 2013 at 2:29 PM, Mike Drob <mdrob@mdrob.com> wrote:
> +1
>
> Nobody looks at dependency resolution until it bites you in the rear.
>
> We could conceivably add this to the pom to automate the running, but would
> still need to make sure that somebody reads the output.
>
>
> On Fri, Nov 8, 2013 at 10:37 AM, Billie Rinaldi <billie.rinaldi@gmail.com>wrote:
>
>> I would like to add running mvn dependency:analyze as a step in our release
>> process.  This should be done with both major and minor releases, as it is
>> very easy to add new direct dependencies without realizing it (when they
>> were previously transitive dependencies), or to leave around dependencies
>> that are no longer needed.
>>
>> Billie
>>