op.apache.org>; hdfs-...@hadoop.apache.org
<mailto:hdfs-...@hadoop.apache.org>; yarn-...@hadoop.apache.org
<mailto:yarn-...@hadoop.apache.org>; mapreduce-...@hadoop.apache.org
<mailto:mapreduce-...@hadoop.apache.org>
Subject: Re: Upgrading minimum version of Maven to 3.1
op.apache.org
<mailto:mapreduce-...@hadoop.apache.org>
Subject: Re: Upgrading minimum version of Maven to 3.1 from 3.0
As I mentioned in YARN-6421. I'm +1 for upgrading to 3.1+ because
the latest version of Maven 3.0.x is quite old. (4 years ago)
We need to update dev
oop.apache.org
> Subject: Re: Upgrading minimum version of Maven to 3.1 from 3.0
>
> As I mentioned in YARN-6421. I'm +1 for upgrading to 3.1+ because
> the latest version of Maven 3.0.x is quite old. (4 years ago)
>
> We need to update dev-support/docker/Dockerfile to enable Ma
t: Re: Upgrading minimum version of Maven to 3.1 from 3.0
As I mentioned in YARN-6421. I'm +1 for upgrading to 3.1+ because
the latest version of Maven 3.0.x is quite old. (4 years ago)
We need to update dev-support/docker/Dockerfile to enable Maven 3.1+ for
precommit Jenkins job.
Regards,
As I mentioned in YARN-6421. I'm +1 for upgrading to 3.1+ because
the latest version of Maven 3.0.x is quite old. (4 years ago)
We need to update dev-support/docker/Dockerfile to enable Maven 3.1+ for
precommit Jenkins job.
Regards,
Akira
On 2017/04/03 18:49, Sunil G wrote:
Hi Folks,
Recent
Hi Folks,
Recently we were doing build framework up-gradation for Yarn Ui. In order
to compile yarn-ui on various architectures, we were using
frontend-maven-plugin 0.0.22 version.
However build is failing in *ppc64le.* If we could use latest version of
frontend-maven-plugin, we could resolve this
