Return-Path: X-Original-To: apmail-incubator-cloudstack-dev-archive@minotaur.apache.org Delivered-To: apmail-incubator-cloudstack-dev-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 5D788DD79 for ; Tue, 21 Aug 2012 17:00:16 +0000 (UTC) Received: (qmail 67775 invoked by uid 500); 21 Aug 2012 17:00:16 -0000 Delivered-To: apmail-incubator-cloudstack-dev-archive@incubator.apache.org Received: (qmail 67747 invoked by uid 500); 21 Aug 2012 17:00:16 -0000 Mailing-List: contact cloudstack-dev-help@incubator.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: cloudstack-dev@incubator.apache.org Delivered-To: mailing list cloudstack-dev@incubator.apache.org Received: (qmail 67738 invoked by uid 99); 21 Aug 2012 17:00:16 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 21 Aug 2012 17:00:16 +0000 X-ASF-Spam-Status: No, hits=-1.6 required=5.0 tests=RCVD_IN_DNSWL_MED,SPF_NEUTRAL X-Spam-Check-By: apache.org Received-SPF: neutral (athena.apache.org: local policy) Received: from [74.125.149.246] (HELO na3sys009aog119.obsmtp.com) (74.125.149.246) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 21 Aug 2012 17:00:08 +0000 Received: from mail-vb0-f48.google.com ([209.85.212.48]) (using TLSv1) by na3sys009aob119.postini.com ([74.125.148.12]) with SMTP ID DSNKUDO+ggHektUBXNFvhb1TeNzJ73nybGeY@postini.com; Tue, 21 Aug 2012 09:59:48 PDT Received: by vbme21 with SMTP id e21so27303vbm.7 for ; Tue, 21 Aug 2012 09:59:45 -0700 (PDT) X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=google.com; s=20120113; h=mime-version:date:message-id:subject:from:to:content-type :x-gm-message-state; bh=JTPyUheHOCnDaupGy/Z7NL41rJYvD8TLeCqNhderyRo=; b=db7LMdtDRDSggkukreUnusDWakH02Inc76TGlBsF2BwXWS6FtfMI2/DekTyW2JRel7 HH59lGxGPgDc2rEge8r1q5nlJQ+5ptGBgBkwRXiMHjrSszxBRb1mPiGKxP/vrA0gI8PG ZSdEVi4ljkCisUCoiefPSItwxW1ZRpgbXs4a/5IZA9XpZiM+cugKMPbm3ZKorm8TwDAk z0utaE23lr9SOlXlK2HCgOXf62jM+H8hjxDTz9bExdVUKPb6Pvwhd1Jo7l8pYCDlOCIh m2CcxUIcgiySPPzlLVyyX3YpQj4WgdaUT8EXcOoqzKQPHWmbVT9o0EKfRzlG0KS6S2zC 2++w== MIME-Version: 1.0 Received: by 10.58.0.82 with SMTP id 18mr15425280vec.0.1345568385546; Tue, 21 Aug 2012 09:59:45 -0700 (PDT) Received: by 10.220.9.207 with HTTP; Tue, 21 Aug 2012 09:59:45 -0700 (PDT) Date: Tue, 21 Aug 2012 12:59:45 -0400 Message-ID: Subject: [ASFCS40] Apache Rampart libs From: Chip Childers To: cloudstack-dev@incubator.apache.org Content-Type: text/plain; charset=ISO-8859-1 X-Gm-Message-State: ALoCoQnf+xPUjKQgcnTwPSq18QJ4/32qm1n7u+oLrezaSy0HzCQm8bVsBb2fKuTcFvH7fEtNlOMx X-Virus-Checked: Checked by ClamAV on apache.org All, We have a bunch of jar files in deps/awsapi-lib/rampart-lib, which I understand are needed for the AWS API functionality. For now, I'm going to assume that we'll have to bundle these JARs with our binary distribution, and am therefore adding it to the LICENSE and NOTICE files appropriately. This brought up the question of HOW exactly to do that... include each specific jar file? Or reference the Rampart project itself? I'm going to approach license tracking as if we were simply including the Rampart project itself, and not the individual components that make up that project. This should suffice, but I wanted to give people a heads up on it. Please shout if you disagree! -chip