Return-Path: Delivered-To: apmail-ant-notifications-archive@locus.apache.org Received: (qmail 91399 invoked from network); 6 Sep 2008 03:33:35 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 6 Sep 2008 03:33:35 -0000 Received: (qmail 27025 invoked by uid 500); 6 Sep 2008 03:33:33 -0000 Delivered-To: apmail-ant-notifications-archive@ant.apache.org Received: (qmail 26996 invoked by uid 500); 6 Sep 2008 03:33:33 -0000 Mailing-List: contact notifications-help@ant.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@ant.apache.org Delivered-To: mailing list notifications@ant.apache.org Received: (qmail 26987 invoked by uid 99); 6 Sep 2008 03:33:33 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 05 Sep 2008 20:33:33 -0700 X-ASF-Spam-Status: No, hits=-2000.0 required=10.0 tests=ALL_TRUSTED X-Spam-Check-By: apache.org Received: from [140.211.11.140] (HELO brutus.apache.org) (140.211.11.140) by apache.org (qpsmtpd/0.29) with ESMTP; Sat, 06 Sep 2008 03:32:43 +0000 Received: from brutus (localhost [127.0.0.1]) by brutus.apache.org (Postfix) with ESMTP id 2654B234C1D0 for ; Fri, 5 Sep 2008 20:32:44 -0700 (PDT) Message-ID: <2048891944.1220671964142.JavaMail.jira@brutus> Date: Fri, 5 Sep 2008 20:32:44 -0700 (PDT) From: "Nascif Abousalh-Neto (JIRA)" To: notifications@ant.apache.org Subject: [jira] Created: (IVY-897) Add VPF as a reort output feature MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-Virus-Checked: Checked by ClamAV on apache.org Add VPF as a reort output feature --------------------------------- Key: IVY-897 URL: https://issues.apache.org/jira/browse/IVY-897 Project: Ivy Issue Type: New Feature Components: Core Affects Versions: 2.0.0-beta-1 Reporter: Nascif Abousalh-Neto Priority: Minor Fix For: unspecified One of the best practices in the use of Ivy for large organizations is to replace all the revision values in the ivy.xml files with properties. This approach allows an administrator to control all revisions values used by all modules in one single place - a Version Property File (or VPF for short). This way versions can be controlled in a uniform way, with minimum maintenance and reduced chance of error. For example, you can upgrade all your modules dependencies from Log4J 3.5 to 4.0 with one single line change - and be sure that you didn't forget any of them behind. Creating and maintaining VPFs is not trival though. One way to automate the process is to "harvest" the module names and their latest versions from the repository, using the repreport task to create a resolution report for the entire repo and then converting it to a property file format using a XSL spreadsheet (attached). -- This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.