I'm doing it for 1.6.0. Rather, I've done it once already, and am willing
to do it again after the other patches / bug fixes are in.
On Fri, Nov 8, 2013 at 7:44 AM, Sean Busbey <[EMAIL PROTECTED]> wrote:
> Sounds reasonable. I presume this wouldn't apply to 1.6.0 since it's in
> progress? John could still opt to do it.
> We should include example text of necessary follow-on actions based on
> results of analyze.
> Call a vote?
> On Nov 8, 2013 9:38 AM, "Billie Rinaldi" <[EMAIL PROTECTED]> wrote:
> > I would like to add running mvn dependency:analyze as a step in our
> > process. This should be done with both major and minor releases, as it
> > 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