Return-Path: 
 <commits-return-2542-apmail-ace-commits-archive=ace.apache.org@ace.apache.org>
X-Original-To: apmail-ace-commits-archive@www.apache.org
Delivered-To: apmail-ace-commits-archive@www.apache.org
Received: from mail.apache.org (hermes.apache.org [140.211.11.3])
	by minotaur.apache.org (Postfix) with SMTP id EBE6BDE02
	for <apmail-ace-commits-archive@www.apache.org>;
 Wed, 23 Jan 2013 11:10:13 +0000 (UTC)
Received: (qmail 45168 invoked by uid 500); 23 Jan 2013 11:10:13 -0000
Delivered-To: apmail-ace-commits-archive@ace.apache.org
Received: (qmail 45116 invoked by uid 500); 23 Jan 2013 11:10:13 -0000
Mailing-List: contact commits-help@ace.apache.org; run by ezmlm
Precedence: bulk
List-Help: <mailto:commits-help@ace.apache.org>
List-Unsubscribe: <mailto:commits-unsubscribe@ace.apache.org>
List-Post: <mailto:commits@ace.apache.org>
List-Id: <commits.ace.apache.org>
Reply-To: dev@ace.apache.org
Delivered-To: mailing list commits@ace.apache.org
Received: (qmail 45095 invoked by uid 99); 23 Jan 2013 11:10:12 -0000
Received: from arcas.apache.org (HELO arcas.apache.org) (140.211.11.28)
    by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 23 Jan 2013 11:10:12 +0000
Date: Wed, 23 Jan 2013 11:10:12 +0000 (UTC)
From: "Marcel Offermans (JIRA)" <jira@apache.org>
To: commits@ace.apache.org
Message-ID: <JIRA.12477362.1287066265256.178368.1358939412921@arcas>
In-Reply-To: <JIRA.12477362.1287066265256@arcas>
References: <JIRA.12477362.1287066265256@arcas>
Subject: [jira] [Closed] (ACE-94) Build requires maven version greater then
  2.0.11 but this is not declared
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394


     [ https://issues.apache.org/jira/browse/ACE-94?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Marcel Offermans closed ACE-94.
-------------------------------

       Resolution: Won't Fix
    Fix Version/s:     (was: 0.8.0-incubator)

No longer relevant.
                
> Build requires maven version greater then  2.0.11 but this is not declared
> --------------------------------------------------------------------------
>
>                 Key: ACE-94
>                 URL: https://issues.apache.org/jira/browse/ACE-94
>             Project: ACE
>          Issue Type: Improvement
>         Environment: Apache Maven 2.0.11 (r909250; 2010-02-12 06:55:50+0100)
> Java version: 1.6.0_21
> Java home: C:\Program Files (x86)\Java\jdk1.6.0_21\jre
> Default locale: nl_NL, platform encoding: Cp1252
> OS name: "windows 7" version: "6.1" arch: "x86" Family: "windows"
>            Reporter: Bram de Kruijff
>            Assignee: Marcel Offermans
>            Priority: Minor
>         Attachments: ACE_maven2011_cleaninstall.txt
>
>
> When you try to build the trunk at r1022542 using Maven 2.0.11 you get the following non-helpfull error right at the start of the build:
> [ERROR] BUILD ERROR
> [INFO] ------------------------------------------------------------------------
> [INFO] Unable to initialise extensions
> Component descriptor role: 'org.apache.maven.wagon.CommandExecutor', implementation: 'org.apache.maven.wagon.providers.ssh.external.ScpExternalCommandExecutor',
>  role hint: 'scpexe' has a hint, but there are other implementations that don't
> It seems the build requires a Maven version greater then 2.0.11 (not sure which one exactly) but this message does not make that clear for the average Jonh Doe. Therefore I suggest adding a small prerequisites section in the root pom that will make people happy. This will still cause the build to fail, but this time with the nice and informative message:
> [ERROR] BUILD FAILURE
> [INFO] ------------------------------------------------------------------------
> [INFO] Unable to build project 'c:\bramk\amdatu\svn\ace-trunk\pom.xml; it requires Maven version 2.2.1 
> The relevant snippet to add would (assuming 2.2.1) be:
>     <prerequisites>
>         <maven>2.2.1</maven>
>     </prerequisites>

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira