Return-Path: X-Original-To: apmail-ace-users-archive@minotaur.apache.org Delivered-To: apmail-ace-users-archive@minotaur.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id A5045119AD for ; Mon, 30 Jun 2014 13:06:00 +0000 (UTC) Received: (qmail 13690 invoked by uid 500); 30 Jun 2014 13:06:00 -0000 Delivered-To: apmail-ace-users-archive@ace.apache.org Received: (qmail 13664 invoked by uid 500); 30 Jun 2014 13:06:00 -0000 Mailing-List: contact users-help@ace.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: users@ace.apache.org Delivered-To: mailing list users@ace.apache.org Received: (qmail 13652 invoked by uid 99); 30 Jun 2014 13:06:00 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 30 Jun 2014 13:06:00 +0000 X-ASF-Spam-Status: No, hits=1.5 required=5.0 tests=HTML_MESSAGE,RCVD_IN_DNSWL_LOW,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of paul.bakker.nl@gmail.com designates 209.85.220.53 as permitted sender) Received: from [209.85.220.53] (HELO mail-pa0-f53.google.com) (209.85.220.53) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 30 Jun 2014 13:05:55 +0000 Received: by mail-pa0-f53.google.com with SMTP id ey11so8516787pad.26 for ; Mon, 30 Jun 2014 06:05:35 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:sender:in-reply-to:references:date:message-id:subject :from:to:content-type; bh=YiL7rjVh131Mn2sY8cGSO+nGbGLGquwTMzAJh0WCBzk=; b=aEOy5AgNxKV0udVYjl9T50oA2O6E0hv37UbaudflFaZAOUTyWnqFIYvWgdHf/NLtAi XdSLM6f7V7Y5rAodGCtDFHKXydbPtwA9rkuVTXJJkAabP2qf01/qS0uFZw4otYyJGNw5 DxFP3+eeWE3+dLJUoLSHscyS8v7VRT6ATopDv2GNBqA9U3w3KX73b7kmXg5cobJclFu1 n6fn4mE4HWjJpHVQcqiYdaR1sq+e/JKtkhgP/bNGbFn2Mlla2rCOSLlh/R5FABc2aPOv +uXcbfbbID0PbpBLvkfkQJobK/8RebNlkPGD8DkJEzTZilse3f8umF6fxQjBROVVOCpt mXUQ== MIME-Version: 1.0 X-Received: by 10.69.31.193 with SMTP id ko1mr51999462pbd.40.1404133535221; Mon, 30 Jun 2014 06:05:35 -0700 (PDT) Sender: paul.bakker.nl@gmail.com Received: by 10.70.51.138 with HTTP; Mon, 30 Jun 2014 06:05:35 -0700 (PDT) In-Reply-To: <1910959217.112388.1404132128681.JavaMail.apache@mail72.abv.bg> References: <1910959217.112388.1404132128681.JavaMail.apache@mail72.abv.bg> Date: Mon, 30 Jun 2014 15:05:35 +0200 X-Google-Sender-Auth: fDWWYyn7LbUNPNxYKm27qkO5sqs Message-ID: Subject: Re: To what extend can Apache Ace deal with .zip Archives From: Paul Bakker To: users@ace.apache.org Content-Type: multipart/alternative; boundary=001a11365b3e95922b04fd0d508e X-Virus-Checked: Checked by ClamAV on apache.org --001a11365b3e95922b04fd0d508e Content-Type: text/plain; charset=UTF-8 Hi M.D, This is possible by implementing a custom resource processor. On the target's side the resource processor will let you do pretty much everything you like with a certain resource type. There is some documentation about this on the website, did you see that already? http://ace.apache.org/dev-doc/adding-custom-artifact-types.html Cheers, Paul On Mon, Jun 30, 2014 at 2:42 PM, M. D. wrote: > Hello, > > In order to supply our clients with the latest hotfixes and updates for > our software, the company I'm working for is developing an Update Service > which will perform automatic updates and version monitoring. > > I'm part of a research group that is responsible for developing this > Update Service. > As the Apache Ace seems a very promising solution, I believe that it may > come to a great help for achieving our company's purposes. > > Although Apache Ace's documentation is very rich, I wasn't able to find > much information about support of no-OSGi artifacts / targets. > As my company's software is not fully OSGi compliant and most of our > hotfixes/updates are distributed through MFTs(Managed file transfer) as > .zip files, I was curious to what extend is Apache Ace capable of dealing > with .zip artifacts? > Our goal is to have our MFT act as an artifact repository. Apache Ace will > then be the linking node in the communication between the MFT and our > clients. > > Please help me understand if this is even doable and approximately how > much effort would that be. > > Thanks in advance! > > > Best regards, > M.D > --001a11365b3e95922b04fd0d508e--