From ivy-user-return-4117-apmail-ant-ivy-user-archive=ant.apache.org@ant.apache.org Mon Oct 20 13:07:33 2008 Return-Path: Delivered-To: apmail-ant-ivy-user-archive@www.apache.org Received: (qmail 91200 invoked from network); 20 Oct 2008 13:07:33 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 20 Oct 2008 13:07:33 -0000 Received: (qmail 1296 invoked by uid 500); 20 Oct 2008 13:07:34 -0000 Delivered-To: apmail-ant-ivy-user-archive@ant.apache.org Received: (qmail 1271 invoked by uid 500); 20 Oct 2008 13:07:34 -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 1260 invoked by uid 99); 20 Oct 2008 13:07:34 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 20 Oct 2008 06:07:34 -0700 X-ASF-Spam-Status: No, hits=2.0 required=10.0 tests=HTML_MESSAGE,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: local policy) Received: from [194.76.29.67] (HELO ns2.msg.de) (194.76.29.67) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 20 Oct 2008 13:06:24 +0000 Received: from ssc1.msg.de (msgs133i.msg.de [193.29.27.101]) by ns2.msg.de (Postfix) with ESMTP id C91D62817B for ; Mon, 20 Oct 2008 15:07:00 +0200 (CEST) Received: from localhost (localhost [127.0.0.1]) by ssc1.msg.de (Postfix) with ESMTP id C211E7026F85 for ; Mon, 20 Oct 2008 15:07:00 +0200 (CEST) X-Virus-Scanned: amavisd-new at msg.de Received: from ssc1.msg.de ([127.0.0.1]) by localhost (mail.msg.de [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id OpqGaGJSdFEK for ; Mon, 20 Oct 2008 15:06:55 +0200 (CEST) Received: from msgc2i.msg.de (msgc2i.msg.de [193.29.27.205]) by ssc1.msg.de (Postfix) with ESMTP id 8F0A67016A3D for ; Mon, 20 Oct 2008 15:06:55 +0200 (CEST) In-Reply-To: To: ivy-user@ant.apache.org Subject: Antwort: Re: Patterns for artifacts MIME-Version: 1.0 X-Mailer: Lotus Notes Release 7.0.2 September 26, 2006 Message-ID: From: Jens Borrmann Date: Mon, 20 Oct 2008 15:06:53 +0200 X-MIMETrack: Serialize by Router on msgc2i/msg(Release 7.0.3FP1|February 24, 2008) at 20.10.2008 15:06:55, Serialize complete at 20.10.2008 15:06:55 Content-Type: multipart/alternative; boundary="=_alternative 00480A77C12574E8_=" X-Virus-Checked: Checked by ClamAV on apache.org --=_alternative 00480A77C12574E8_= Content-Type: text/plain; charset="US-ASCII" Thanks, that helped. Somehow I must have missed the obvious fact that there can be several patterns per resolver. Instead I tried to find a more esoteric solution ;-) --- Jens "Gilles Scokart" 20.10.2008 12:42 Bitte antworten an ivy-user@ant.apache.org An ivy-user@ant.apache.org Kopie Thema Re: Patterns for artifacts In a resolver configuration, you can specify multiple ivy & artefact pattern. 2008/10/20 Jens Borrmann : > Hello, > > is there a chance to configure ivy to use patterns when resolving modules. > Our use case is that we want to set up a binary repository for all OSGi > bundles we use in our company. Unfortunately, there are two main types of > naming conventions for publicly available bundles - one using > underscores, one using hyphens. > [artifact]_[revision].[ext] vs. > [artifact]-[revision].[ext] > > To ease updates in the future we want to change as little as possible when > taking bundles into our repository. I did not find a way to apply > matchers or a similar solution to this problem. Can anybody help? > > Regards, > Jens -- Gilles Scokart --=_alternative 00480A77C12574E8_=--