Return-Path: Delivered-To: apmail-incubator-etch-dev-archive@minotaur.apache.org Received: (qmail 40041 invoked from network); 16 Feb 2009 17:12:56 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 16 Feb 2009 17:12:56 -0000 Received: (qmail 60547 invoked by uid 500); 16 Feb 2009 17:12:56 -0000 Delivered-To: apmail-incubator-etch-dev-archive@incubator.apache.org Received: (qmail 60535 invoked by uid 500); 16 Feb 2009 17:12:56 -0000 Mailing-List: contact etch-dev-help@incubator.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: etch-dev@incubator.apache.org Delivered-To: mailing list etch-dev@incubator.apache.org Received: (qmail 60524 invoked by uid 99); 16 Feb 2009 17:12:56 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 16 Feb 2009 09:12:56 -0800 X-ASF-Spam-Status: No, hits=-4.0 required=10.0 tests=RCVD_IN_DNSWL_MED,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of sccomer@cisco.com designates 171.71.176.117 as permitted sender) Received: from [171.71.176.117] (HELO sj-iport-6.cisco.com) (171.71.176.117) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 16 Feb 2009 17:12:44 +0000 X-IronPort-AV: E=Sophos;i="4.38,217,1233532800"; d="scan'208";a="250455048" Received: from sj-dkim-3.cisco.com ([171.71.179.195]) by sj-iport-6.cisco.com with ESMTP; 16 Feb 2009 17:12:23 +0000 Received: from sj-core-1.cisco.com (sj-core-1.cisco.com [171.71.177.237]) by sj-dkim-3.cisco.com (8.12.11/8.12.11) with ESMTP id n1GHCNsF014880 for ; Mon, 16 Feb 2009 09:12:23 -0800 Received: from xbh-sjc-231.amer.cisco.com (xbh-sjc-231.cisco.com [128.107.191.100]) by sj-core-1.cisco.com (8.13.8/8.13.8) with ESMTP id n1GHCM3v002507 for ; Mon, 16 Feb 2009 17:12:22 GMT Received: from xfe-sjc-212.amer.cisco.com ([171.70.151.187]) by xbh-sjc-231.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); Mon, 16 Feb 2009 09:12:22 -0800 Received: from [127.0.0.1] ([10.89.23.22]) by xfe-sjc-212.amer.cisco.com with Microsoft SMTPSVC(6.0.3790.1830); Mon, 16 Feb 2009 09:12:22 -0800 Message-ID: <49999E7A.302@cisco.com> Date: Mon, 16 Feb 2009 11:12:26 -0600 From: scott comer User-Agent: Thunderbird 2.0.0.19 (Windows/20081209) MIME-Version: 1.0 To: etch-dev@incubator.apache.org Subject: Re: Etch Maven Plugin References: <4C76BEA6DA349A4EBE240D97BBE4546405337FDB@xmb-sjc-22b.amer.cisco.com> In-Reply-To: <4C76BEA6DA349A4EBE240D97BBE4546405337FDB@xmb-sjc-22b.amer.cisco.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-OriginalArrivalTime: 16 Feb 2009 17:12:22.0672 (UTC) FILETIME=[BB5D6900:01C99059] DKIM-Signature: v=1; a=rsa-sha256; q=dns/txt; l=2180; t=1234804343; x=1235668343; c=relaxed/simple; s=sjdkim3002; h=Content-Type:From:Subject:Content-Transfer-Encoding:MIME-Version; d=cisco.com; i=sccomer@cisco.com; z=From:=20scott=20comer=20 |Subject:=20Re=3A=20Etch=20Maven=20Plugin |Sender:=20; bh=7okCsR33GuL9Gvvf6UKOMH3bI58H6T1QB3kJkcFvLwg=; b=BEKsQZq74e/r+rVfwO++uuVIymevi8wI1b0j7d1nxHlGP+YG78u3LiUBTK QIppCcfLvy/Ue4B1aDqSKZrhCyNRmHnHY7C7Ba0bTAMDcqse/BZ9p8mF1Vll 4L+XFtU3A5; Authentication-Results: sj-dkim-3; header.From=sccomer@cisco.com; dkim=pass ( sig from cisco.com/sjdkim3002 verified; ); X-Virus-Checked: Checked by ClamAV on apache.org inline. Rick Bolkey (rbolkey) wrote: > Hi all, > > > > So I've been developing an etch plugin for maven. There are a few use > cases I had in mind in developing the plugin, so I would like to present > those as well as go over the general flow of the plugin. I'd appreciate > some feedback as far as alternative use-cases that could fit within the > scope of the plugin. > > > > I had two use cases directly in mind. > > > > 1) A user has an etch file in their project, and wants to generate > a binding. > a client or a service implementation? > 2) A user has a dependency containing an etch file, and wants to > generate a binding. > a reference client or service? so what is the different action between these two? > > > Use case #2 service the case if you want to publish an etch file in an > artifact, and allow different projects to generate binding for it. > > > > Right now the plugin consists of one goal that does the following: > > > > 1) Scans through all the compile time dependencies of a project. > If a dependency contains an etch file, that file along with any "txt" > files (for inclusions) are extracted to a temporary sandbox under the > target directory. > > 2) Plugin then looks for the etch file specified in the plugin in > the following locations. 1) as an absolute reference, 2) in > "src/main/etch", and 3) in the sandbox where we extracted all the found > etch files. > > 3) Generate the binding based on the resolved etch file. > > > > I think I would like to separate steps 1 and 2 above into separate > goals. Also, the plugin currently suppresses generation when it detects > the binding has already been generated (this can be overridden using a > "force" parameter. > not sure what you mean here. when / why would you want to suppress? > > > Please let me know if you want any more details/description. I need to > run to a meeting. > > > > Thanks > > Rick > > > > Richard R. Bolkey > > Cisco Systems, Inc > > d: +1-512-336-3322 > > e: rbolkey@cisco.com > > > > >