Return-Path: X-Original-To: apmail-ant-ivy-user-archive@www.apache.org Delivered-To: apmail-ant-ivy-user-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 275179989 for ; Wed, 5 Oct 2011 15:09:53 +0000 (UTC) Received: (qmail 48261 invoked by uid 500); 5 Oct 2011 15:09:52 -0000 Delivered-To: apmail-ant-ivy-user-archive@ant.apache.org Received: (qmail 48236 invoked by uid 500); 5 Oct 2011 15:09:52 -0000 Mailing-List: contact ivy-user-help@ant.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: ivy-user@ant.apache.org Delivered-To: mailing list ivy-user@ant.apache.org Received: (qmail 48228 invoked by uid 99); 5 Oct 2011 15:09:52 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 05 Oct 2011 15:09:52 +0000 X-ASF-Spam-Status: No, hits=1.5 required=5.0 tests=FREEMAIL_FROM,HTML_MESSAGE,RCVD_IN_DNSWL_LOW,SPF_PASS,T_TO_NO_BRKTS_FREEMAIL X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of archie.cobbs@gmail.com designates 209.85.220.45 as permitted sender) Received: from [209.85.220.45] (HELO mail-dy0-f45.google.com) (209.85.220.45) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 05 Oct 2011 15:09:44 +0000 Received: by dyf17 with SMTP id 17so99725dyf.4 for ; Wed, 05 Oct 2011 08:09:24 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:sender:in-reply-to:references:from:date :x-google-sender-auth:message-id:subject:to:content-type; bh=NIoEPxO4R7W9Iv1l5k6V7MdEtSPcfDMWgDTZ6vsfhPs=; b=GYNPMcZWWDxlUy4/j0FWWwFzVqhWAIAI5Y8VkgbLb+GFPLQqfw3ZOVGUb/LtezzAZc tUNY6iF1++QW9fX7JQHQdMw10KV+SWJYjn9Leb+UlD44vF7rofOY7o5D6pI0PmZshP/B 3JkCzOH3TXEIPvcEONBQnlq+9fCKll58mzJwA= Received: by 10.223.23.142 with SMTP id r14mr3731996fab.60.1317827364293; Wed, 05 Oct 2011 08:09:24 -0700 (PDT) MIME-Version: 1.0 Sender: archie.cobbs@gmail.com Received: by 10.152.24.136 with HTTP; Wed, 5 Oct 2011 08:09:04 -0700 (PDT) In-Reply-To: References: From: Archie Cobbs Date: Wed, 5 Oct 2011 10:09:04 -0500 X-Google-Sender-Auth: bGvLpJ2Hckp2ZfCYQOXJopt2pGk Message-ID: Subject: Re: Publication Question: reference globs in artifact list To: ivy-user@ant.apache.org Content-Type: multipart/alternative; boundary=00151747b5a2ec8c6204ae8e9776 X-Virus-Checked: Checked by ClamAV on apache.org --00151747b5a2ec8c6204ae8e9776 Content-Type: text/plain; charset=ISO-8859-1 I don't think there's any way to define "wildcard" artifacts. So either define a single large artifact that the user is required to unpack, or else have the packager resolver unpack it. In the latter case, you must update the ivy.xml file (and possibly the packager.xml file too) when a new version is added that contains different artifacts. We do this all the time in Ivy RoundUp and it's not a big deal unless the people publishing the thing are releasing and changing things around like crazy. -Archie On Wed, Oct 5, 2011 at 9:50 AM, Peter Kahn wrote: > Hi all, > > Is the right approach for ivy modules with variable or unknown content to > list an single archive file as a publications artifact and have the build > expand it after the ivy retrieve? > > I'm trying to use ivy to deliver a 3rd part tool (NSIS installer) and > ideally I'd like the ivy+packager fetch the zip, deliver it do the > workspace > and expand it. I can have packager expand the zip and deliver all items I > listed in the ivy module's publish section but this is fragile there are > 50+ files and they may change over time. > > Is there a way to fee the artifact an ant glob / fileset or should I be > handing an archive file to the subscribe build and have it's build.xml > unzip > it? > > Thanks > > Peter > > > -- > Peter Kahn > citizenkahn@gmail.com > http://www.google.com/profiles/citizenkahn > Awareness - Intention - Action > -- Archie L. Cobbs --00151747b5a2ec8c6204ae8e9776--