From ivy-user-return-8000-apmail-ant-ivy-user-archive=ant.apache.org@ant.apache.org Thu Jul 7 15:56:34 2011 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 9B9274344 for ; Thu, 7 Jul 2011 15:56:34 +0000 (UTC) Received: (qmail 10854 invoked by uid 500); 7 Jul 2011 15:56:34 -0000 Delivered-To: apmail-ant-ivy-user-archive@ant.apache.org Received: (qmail 10744 invoked by uid 500); 7 Jul 2011 15:56:33 -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 10736 invoked by uid 99); 7 Jul 2011 15:56:32 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 07 Jul 2011 15:56:32 +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 citizenkahn@gmail.com designates 74.125.82.47 as permitted sender) Received: from [74.125.82.47] (HELO mail-ww0-f47.google.com) (74.125.82.47) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 07 Jul 2011 15:56:25 +0000 Received: by wwf27 with SMTP id 27so887797wwf.16 for ; Thu, 07 Jul 2011 08:56:04 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:date:message-id:subject:from:to:content-type; bh=KPv0/Ex30dY0NXUKra99VkieM5qsZhAhhjCyvtCDEmI=; b=FYEKFWArHYS3pTjz7rN3cYFHvHENmM58rRe7TkmFDpqsUjDRNCF8D9g3u+3cGqTwzM LhwC0iHclrNY3CqDcqAgYFu+Zc8i77jDJqj+gsH/jKbSfrj9CU/ZtdvVy1dofCL0VhCk e+07ZX3tcNJUNO6jau718gkWrZVbtIKIeEO9A= MIME-Version: 1.0 Received: by 10.216.1.200 with SMTP id 50mr7712386wed.33.1310054164536; Thu, 07 Jul 2011 08:56:04 -0700 (PDT) Received: by 10.216.175.149 with HTTP; Thu, 7 Jul 2011 08:56:04 -0700 (PDT) Date: Thu, 7 Jul 2011 11:56:04 -0400 Message-ID: Subject: C, C# and Ivy - Publishing binaries and many supporting files From: Peter Kahn To: ivy-user@ant.apache.org Content-Type: multipart/alternative; boundary=0016364d2c791d1f0604a77cc1f1 X-Virus-Checked: Checked by ClamAV on apache.org --0016364d2c791d1f0604a77cc1f1 Content-Type: text/plain; charset=ISO-8859-1 Hi all, How do you approach publishing a binary library plus a large number of supporting files? Specifically, we have a build that produces a binary DLL + many include files. I'd like to know what's the standard practice and what are the gotchas. I can publish the DLL and a zip containing the include files which forces subscribers to retrieve and unpack prior to build I can publish the DLL and a lose directory of files but I'm concerned about effort required to maintain this over time - do I need to reference each file as a publishable/retrieveable artifact? - do I run into a risk of stale files being used by subscribe builds (foo.h is deleted and published, but foo.h remains on the subscriber build workspace even after retrieve) What approach do you take to keep effort and cleanup risks low? Thanks Peter -- Peter Kahn citizenkahn@gmail.com http://www.google.com/profiles/citizenkahn Awareness - Intention - Action --0016364d2c791d1f0604a77cc1f1--