Return-Path: Delivered-To: apmail-ant-notifications-archive@minotaur.apache.org Received: (qmail 55783 invoked from network); 12 Jan 2010 14:46:15 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.3) by minotaur.apache.org with SMTP; 12 Jan 2010 14:46:15 -0000 Received: (qmail 65959 invoked by uid 500); 12 Jan 2010 14:46:15 -0000 Delivered-To: apmail-ant-notifications-archive@ant.apache.org Received: (qmail 65880 invoked by uid 500); 12 Jan 2010 14:46:15 -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 65871 invoked by uid 99); 12 Jan 2010 14:46:15 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 12 Jan 2010 14:46:15 +0000 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; Tue, 12 Jan 2010 14:46:14 +0000 Received: from brutus.apache.org (localhost [127.0.0.1]) by brutus.apache.org (Postfix) with ESMTP id 64970234C045 for ; Tue, 12 Jan 2010 06:45:54 -0800 (PST) Message-ID: <1816187057.182081263307554397.JavaMail.jira@brutus.apache.org> Date: Tue, 12 Jan 2010 14:45:54 +0000 (UTC) From: "Maarten Coene (JIRA)" To: notifications@ant.apache.org Subject: [jira] Resolved: (IVY-1158) Make ivy.xml available In-Reply-To: <997606460.118021262943594388.JavaMail.jira@brutus.apache.org> MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable X-JIRA-FingerPrint: 30527f35849b9dde25b450d4833f0394 [ https://issues.apache.org/jira/browse/IVY-1158?page=3Dcom.atlassian.= jira.plugin.system.issuetabpanels:all-tabpanel ] Maarten Coene resolved IVY-1158. -------------------------------- Resolution: Fixed Fix Version/s: trunk Assignee: Maarten Coene I've implemented your first RFE in trunk. After running the task, the descriptions are availabe as "ivy.= configuration.[config name].desc". Regarding your second RFE, I think this is too specific to add to Ivy. And = you can easily do it with ant-contrib as you illustrated in your example bu= ild.xml, something like this: {noformat} {noformat} But please reopen if you don't agree... Maarten > Make ivy.xml available > ----------------------------------------- > > Key: IVY-1158 > URL: https://issues.apache.org/jira/browse/IVY-1158 > Project: Ivy > Issue Type: New Feature > Components: Ant > Reporter: Jan Mat=C3=A8rne > Assignee: Maarten Coene > Priority: Minor > Fix For: trunk > > > You can (an IMHO should) write an explanation of the configuration in the= ivy file > > > > > > The Ant task makes the names names available, but not the des= criptions.=20 > So the first RFE is making them available (accoding to 'infotest.configur= ations') as 'infotest.configuration.descriptions'. > Another RFE is enhanding to create a describing file in t= he destination directory which contains this information. > E.e. with Ivy pattern lib/[conf]/[artifact].[ext] you would create with <= ivy:retrieve descriptionfile=3D"readme.txt"/> a file lib/runtime/readme.txt= with content "Runtime Libraries". > (!! Recreate old files, but beware that multiple confs could result in th= e same dir if the ivy pattern doesnt contain a [conf]. ) --=20 This message is automatically generated by JIRA. - You can reply to this email to add a comment to the issue online.