Mailing-List: contact builds-help@apache.org; run by ezmlm
Precedence: bulk
Reply-To: builds@apache.org
Date: Thu, 20 Aug 2015 12:18:47 +0000 (UTC)
From: "Gavin (JIRA)" <jira@apache.org>
To: builds@apache.org
Message-ID: <JIRA.12856457.1439738693000.118194.1440073127089@Atlassian.JIRA>
In-Reply-To: <JIRA.12856457.1439738693000@Atlassian.JIRA>
References: <JIRA.12856457.1439738693000@Atlassian.JIRA>
 <JIRA.12856457.1439738693956@arcas>
Subject: [jira] [Commented] (BUILDS-106) update Maven version for Maven
 builds
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: quoted-printable


    [ https://issues.apache.org/jira/browse/BUILDS-106?page=3Dcom.atlassian=
.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=3D1470=
4751#comment-14704751 ]=20

Gavin commented on BUILDS-106:
------------------------------

maven-parent-pom: maven 3.0.3 -> maven 3.2.2 :: jdk 1.6.0_24 -> no change :=
: mailto set to notifications@maven.apache.org
ran a build and it passed.

> update Maven version for Maven builds
> -------------------------------------
>
>                 Key: BUILDS-106
>                 URL: https://issues.apache.org/jira/browse/BUILDS-106
>             Project: Infra Build Platform
>          Issue Type: Task
>          Components: Analysis
>            Reporter: Herv=C3=A9 Boutemy
>
> it seems a good number of jobs for Maven run with Maven [3.0,3.0.3], whic=
h fails the build:
> here is the list: https://analysis.apache.org/jenkins/view/maven/
> and one faiklure example: https://analysis.apache.org/jenkins/view/maven/=
job/maven-parent-pom/113/console
> Please update Maven version used to a newer one (3.0.5 or more)
> notice: if build failures could be sent to notifications@maven.apache.org=
, please, this would ease detection of such failing analysis builds by Mave=
n team


--
This message was sent by Atlassian JIRA
(v6.3.4#6332)