Return-Path: X-Original-To: apmail-maven-users-archive@www.apache.org Delivered-To: apmail-maven-users-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 6CF8971C0 for ; Fri, 2 Sep 2011 14:58:56 +0000 (UTC) Received: (qmail 89019 invoked by uid 500); 2 Sep 2011 14:58:53 -0000 Delivered-To: apmail-maven-users-archive@maven.apache.org Received: (qmail 88943 invoked by uid 500); 2 Sep 2011 14:58:53 -0000 Mailing-List: contact users-help@maven.apache.org; run by ezmlm Precedence: bulk List-Unsubscribe: List-Help: List-Post: List-Id: "Maven Users List" Reply-To: "Maven Users List" Delivered-To: mailing list users@maven.apache.org Received: (qmail 88929 invoked by uid 99); 2 Sep 2011 14:58:52 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 02 Sep 2011 14:58:52 +0000 X-ASF-Spam-Status: No, hits=1.5 required=5.0 tests=FREEMAIL_FROM,HTML_MESSAGE,RCVD_IN_DNSWL_LOW,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of sshock@gmail.com designates 74.125.82.171 as permitted sender) Received: from [74.125.82.171] (HELO mail-wy0-f171.google.com) (74.125.82.171) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 02 Sep 2011 14:58:46 +0000 Received: by wyh13 with SMTP id 13so2905545wyh.30 for ; Fri, 02 Sep 2011 07:58:25 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :content-type; bh=oB27Boqw9iLOoCX1sTpVkDMxn9wNaZxJoZ47YE3Z5Jg=; b=I4snezEd1GhuixGntLXGFvMRXdoMex64LB2NlUc4P0UF/3rlCi7UNto0KLMD9U9kmG 3/4cLC9NYj5zwWE3LdfhKpkqDFp+rAm2pThy3N2y1wG9NfpoiskD3OjZT7eoWU+l0944 rjzh99/IZdVwsGZ3Q4WVMv9EOnz75wg3HtDuU= Received: by 10.216.155.130 with SMTP id j2mr1164351wek.58.1314975505187; Fri, 02 Sep 2011 07:58:25 -0700 (PDT) MIME-Version: 1.0 Received: by 10.216.12.66 with HTTP; Fri, 2 Sep 2011 07:58:05 -0700 (PDT) In-Reply-To: References: From: Phillip Hellewell Date: Fri, 2 Sep 2011 08:58:05 -0600 Message-ID: Subject: Re: Set read-only flag on unpacked dependencies To: Maven Users List Content-Type: multipart/alternative; boundary=0016e6570edae0033c04abf69744 --0016e6570edae0033c04abf69744 Content-Type: text/plain; charset=UTF-8 I take it I need to write a little plugin :) BTW, for any who are curious, the purpose is that because some of our components are C++, they deliver both dlls and headers for the interface, so unlike C# and other languages where interfaces are binary too, we have the problem where we might accidentally modify a header file not realizing it came from a dependency, and never find out about it until it breaks someone else. Hence, the idea we came up with was to automatically flag the dependency files as read-only after unpacking. Phillip On Mon, Aug 29, 2011 at 12:22 PM, Phillip Hellewell wrote: > When using dependency:unpack-dependencies, I would like to flag all the > unpacked files as read-only. I don't see a parameter to do that. Is there > a separate plugin out there that I could use? So after unpacking it would > flag all files below target\dependency as read-only. > > Well, if worst comes to worst, I know I can write my own little plugin to > do this quite easily... > > Thanks, > Phillip > --0016e6570edae0033c04abf69744--