Return-Path: Delivered-To: apmail-ant-ivy-user-archive@www.apache.org Received: (qmail 54021 invoked from network); 8 May 2009 16:09:07 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.3) by minotaur.apache.org with SMTP; 8 May 2009 16:09:07 -0000 Received: (qmail 55147 invoked by uid 500); 8 May 2009 16:09:06 -0000 Delivered-To: apmail-ant-ivy-user-archive@ant.apache.org Received: (qmail 55111 invoked by uid 500); 8 May 2009 16:09:06 -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 55101 invoked by uid 99); 8 May 2009 16:09:06 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 08 May 2009 16:09:06 +0000 X-ASF-Spam-Status: No, hits=2.2 required=10.0 tests=HTML_MESSAGE,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of garima.bathla@gmail.com designates 209.85.200.170 as permitted sender) Received: from [209.85.200.170] (HELO wf-out-1314.google.com) (209.85.200.170) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 08 May 2009 16:08:57 +0000 Received: by wf-out-1314.google.com with SMTP id 28so1256376wfc.10 for ; Fri, 08 May 2009 09:08:37 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:in-reply-to:references :date:message-id:subject:from:to:content-type; bh=yyLedmsq2DnlOw+0BTtJAcVN2i2s02wdWSOpY3D3w9U=; b=w97jY49+1+hLLcfqGxCSAdLc6TTx8CXVMy7LblG+1N2zzf2e4FQmPRAEqHG+6okC2i xSQcZNOzfg79H/UcTrzOY+W1UKe82zL7mlm+3vqZP0HT+KHN3arfrNE+8Oy4aPgayrqX W05VlhlhItCpHSqRduDAUA7xUFhFttvL2FR9U= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; b=KEHydu+jXnNdf3VLvc9G3ntC5zeBwFSztijlpZVD+lK8LIdHC2iYUpXT+LRHt9tgva VGZt7y1OyNz/qk7xAD1Q8QoayjGC2hM24Y4bysF91y//oLXZW8M6lOTXaRj+vM3Oj48S UYBxZQW/KRaMRxDT/65NVVg0eZNBYVT9yvWic= MIME-Version: 1.0 Received: by 10.142.191.5 with SMTP id o5mr1682071wff.53.1241798917373; Fri, 08 May 2009 09:08:37 -0700 (PDT) In-Reply-To: <65d6a07f0905080425k587cfe0eyb7b36f87cc32e51@mail.gmail.com> References: <65d6a07f0905080425k587cfe0eyb7b36f87cc32e51@mail.gmail.com> Date: Fri, 8 May 2009 09:08:37 -0700 Message-ID: <1fb30820905080908p570d7a79xffd59d46986093c7@mail.gmail.com> Subject: Re: Building a little bit more advanced repository, any tutorial or information out there? From: Garima Bathla To: ivy-user@ant.apache.org Content-Type: multipart/alternative; boundary=000e0cd28df25a40bf046968d7b4 X-Virus-Checked: Checked by ClamAV on apache.org --000e0cd28df25a40bf046968d7b4 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit OK; Seems like a scenario which should be very common? Most of the teams will not want to depend on public repository all the time - what if a developer wants to work offline with no internet access without messing around with settings? I am no IVY expert - but below is a sure shot solution that my colleague has implemented for our team to work in similar model - go to public repository only when it is needed. So we have 3 types of repositories: 1. Thirdparty repositories - where we publish third-party jars that do not exist on any public repository - we convert them to an ivy module and publish. 2. Internal repository - where we publish all our teams specific modules . 3. public repository - used to resolve the rest of the modules ( we depend on spring source repo). So in your case first of all if you can build company repository successfully then I assume you will want Ivy to resolve in below order 1. Try Company repository ( with ibiblio modules and thirdparty modules?) 2. Try ibiblio repository So in your ivysettings you can define new resolvers i.e. Shared resolver using company repository to resolve modules Public resolver using ibiblio to resolve modules and then chain them So you will have to modify ivysettings.xml and not ivy.xml. I hope you do have ivysettings.xml? HTH, Garima. On Fri, May 8, 2009 at 4:25 AM, Kent Larsson wrote: > Hi, > > I have an ivy.xml which looks something like: (for proper formatting: > http://pastebin.com/f21948262 ) > > > xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" > xsi:noNamespaceSchemaLocation="http://ant.apache.org/ivy/schemas/ivy.xsd > "> > organisation="net.mycompany" > module="webcollab" > status="integration"/> > > > > > > rev="1.3.5" > conf="runtime->default;foride->sources,javadoc"> > module="portals-bridges-common"/> > > > conf="runtime->default;foride->sources,javadoc" /> > name="wicket-spring-annot" > rev="1.3.5" conf="runtime->default;foride->sources,javadoc"/> > conf="runtime->default;foride->sources,javadoc"/> > rev="1.5.6" > conf="runtime->default;foride->sources,javadoc"/> > > > > > My current ivy.xml uses the default repository ibiblio in Maven2-mode. > > What I would like is: > > 1. Have a company repository with copies of everything I usually take > from ibiblio. > > 2. Also have some JAR's in that repository which are not in ibiblio, > like JavaMail and Activation, both from Sun. > > 3. In the Ivy resolution on the client machines, try the company > repository first, then try ibiblio. > > Motivation for 3 is that if I add something to my ivy.xml which is > available in ibiblio I could get it directly, while my company > repository might be synchronized with ibiblio once each day. Also if > my company repository is down it might be nice to fall back on ibiblio > for non licensed files (and hope that JavaMail etc is in the local > cache already). > > Is there any information out there for this scenario? It seems like it > would be a common scenario. I can't find any, and I don't know where > to start. If I just can get some more information I'll try to create a > blog post about it or something, in case there is a lack of > information on the net. > > Thank you for reading! I hope you can help me out. Have a nice weekend! > > Best regards, Kent > --000e0cd28df25a40bf046968d7b4--