No complaints requiring 3.0.5 instead of 3.0.4 (pretty ancient versions at this point).

A table tracking minVers would be nice as Sean says.

On 4/3/18 9:55 AM, Sean Busbey wrote:
a table listing would be nice, if we end up using different versions
of maven on different release lines. otherwise, I think having a
minimum version in the pom is sufficient beyond making sure we have a
call out about needing maven 3.

What's the downside to keeping our requirement at 3.0.5? do we have
actual test coverage that 3.0.5 works? I know there's definitely been
stuff in the past where I had to work around differences in minor
maven versions (wrt handling the shading stuff, IIRC).

Supporting javas newer than java 8 will presumably require us to bump
the maven version?

On Mon, Apr 2, 2018 at 7:10 PM, Mike Drob <[email protected]> wrote:
According to the book at http://hbase.apache.org/book.html#build.basic our
minimum maven version is currently 3.0.4

However, after HBASE-20212 introduced the warbucks plugin we require 3.0.5

I'm not against bumping the minimum here when there is value added, but we
should take this opportunity to examine if it makes sense to bump further?
I couldn't tell which release lines are still supported by the maven
community aside from the latest.

Should we include a nice table listing hbase version with minimum maven for
building?

Mike

Reply via email to