From kaitlyn70@example.org Wed Apr 01 12:13:56 2009 Return-Path: <kaitlyn70@example.org> Delivered-To: kaitlyn70@example.org Received: (qmail 75400 invoked from network); 1 Apr 2009 12:13:56 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (83.161.120.155) by minotaur.apache.org with SMTP; 1 Apr 2009 12:13:56 -0000 Received: (qmail 81032 invoked by uid 500); 1 Apr 2009 12:13:55 -0000 Delivered-To: kaitlyn70@example.org Received: (qmail 80981 invoked by uid 500); 1 Apr 2009 12:13:55 -0000 Mailing-List: contact kaitlyn70@example.org; run by ezmlm Precedence: bulk List-Help: <mailto:kaitlyn70@example.org> List-Unsubscribe: <mailto:kaitlyn70@example.org> List-Post: <mailto:kaitlyn70@example.org> List-Id: <ivy-user.ant.apache.org> Reply-To: kaitlyn70@example.org Delivered-To: mailing list kaitlyn70@example.org Delivered-To: moderator for kaitlyn70@example.org Received: (qmail 57125 invoked by uid 99); 1 Apr 2009 04:05:48 -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 kaitlyn70@example.org designates 83.161.120.155 as permitted sender) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:sender:received:in-reply-to :references:date:x-google-sender-auth:message-id:subject:from:to :content-type; bh=BtkV/WtfGk6PUO2Coucy3pZo87UISQsXTp/C6Cy+JQY=; b=AWFvVMjhdvJKMIciFClyHD2NbLGm1y1uG1IVQ02wqG3SW2LI5s4VpfVsm8hlxSBZBu XhSxz7HDXEG+D6Txan5tg0bIHaXk0dxoYnH4oo+GCocNvjbuUcNlEtvOqxptDosUbCf+ KgqY8M1sHcSEVLZ/kw9rLhL9iuH8ZZuCP1HGE= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:content-type; b=xRJqVfUYKz75UU2frlup1n7DUPNdmgtAijlmRTgspLwWFWz44ym0ReAowkgHffneEg +6hh/Q0hs4iPXDrYJxVCyS+rM/uVB1QQ8qfRHD3DFVkCO+f8rktLPsQPeD77KlEIGzed XLwRGXebivwZk5sHvawzxqEaUyi4r9/Tp+d9g= MIME-Version: 1.0 Sender: kaitlyn70@example.org In-Reply-To: <1238543731.11826.18.camel@phil-desktop> References: <1238543731.11826.18.camel@phil-desktop> Date: Tue, 31 Mar 2009 23:05:21 -0500 X-Google-Sender-Auth: 207e619841a77aa6 Message-ID: <kaitlyn70@example.org> Subject: Re: Problem with IvyDE retrieve ? From: OsoRojo <kaitlyn70@example.org> To: kaitlyn70@example.org Content-Type: multipart/alternative; boundary=0016368e1d5f9d78d60466766c1b X-Virus-Checked: Checked by ClamAV on apache.org --0016368e1d5f9d78d60466766c1b Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit 2 Things to check, one obvious and one less so: 1) Make sure your using either workspace default settings configured via the preferences page OR project specific settings via right click on the ivy library in the project and selecting properties. I toyed with workspace settings longer than I care to admit before I realized I had at some point enabled project settings which overrode them. (on a side note, it would be much easier to configure IvyDE settings via the PROJECT properties and not the libraries properties. Remembering where that was took me awhile and is very non standard) 2) On the retrieve tab, make sure you specify which artifacts you want to download by type. So in the types field, remove the asterisk and specify jar (or whatever your artifact is). The default 'all' using asterisk currently doesn't work. There's a bug somewhere on point 2 but I don't remember if it's resolved and not released, resurfaced or what. I do know that my retrieve doesn't work unless I specify the artifact type though. Hope this helps. OsoRojo On Tue, Mar 31, 2009 at 6:55 PM, Phil Beiler <kaitlyn70@example.org>wrote: > This seems too obvious to be a problem, but I cannot get the "retrieve" > option to work what so ever. This sounds pretty simple; I have Ivy > working perfectly from Ant, but the Eclipse plug-in has always been a > little more challenging (SSL, authentication, fake certs)... I'm using > Eclipse 3.4 with the 2.0.0beta1 plug-in. My configuration is pretty > simple, three configs [compile, runtime, debug]. I have made the > setting look exactly like the documentation page, trying different > combinations on the retrieve and advanced tabs with nothing ever > happening, nothing in the Ivy console. > > I am able to use the plug-in successfully in Eclipse without doing a > resolve, those projects are fine. I am trying to use the ORACLE > Enterprise Pack plug-in to deploy my Weblogic server. Unfortunately, it > does not pick up the ivy managed libraries on the buildpath (nor does > tomcat for that matter), so my plan was to "retrieve" them into the > WEB-INF/lib directory... > > Unfortunately, I cannot get the retrieve to work in any Eclipse project, > simple java or dynamic web? > > Any ideas? Thanks. Phil > > --0016368e1d5f9d78d60466766c1b-- From kaitlyn70@example.org Wed Apr 01 12:22:11 2009 Return-Path: <kaitlyn70@example.org> Delivered-To: kaitlyn70@example.org Received: (qmail 81984 invoked from network); 1 Apr 2009 12:22:11 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (83.161.120.155) by minotaur.apache.org with SMTP; 1 Apr 2009 12:22:11 -0000 Received: (qmail 93211 invoked by uid 500); 1 Apr 2009 12:22:10 -0000 Delivered-To: kaitlyn70@example.org Received: (qmail 93154 invoked by uid 500); 1 Apr 2009 12:22:10 -0000 Mailing-List: contact kaitlyn70@example.org; run by ezmlm Precedence: bulk List-Help: <mailto:kaitlyn70@example.org> List-Unsubscribe: <mailto:kaitlyn70@example.org> List-Post: <mailto:kaitlyn70@example.org> List-Id: <ivy-user.ant.apache.org> Reply-To: kaitlyn70@example.org Delivered-To: mailing list kaitlyn70@example.org Received: (qmail 93144 invoked by uid 99); 1 Apr 2009 12:22:10 -0000 Received: from nike.apache.org (HELO nike.apache.org) (83.161.120.155) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 01 Apr 2009 12:22:10 +0000 X-ASF-Spam-Status: No, hits=-1.0 required=10.0 tests=RCVD_IN_DNSWL_LOW,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: local policy) Received: from [83.161.120.155] (HELO eir.is.scarlet.be) (83.161.120.155) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 01 Apr 2009 12:22:00 +0000 Received: from mail.harfang.homelinux.org (ip-213-49-239-135.dsl.scarlet.be [83.161.120.155]) by eir.is.scarlet.be (8.14.2/8.14.2) with ESMTP id n31CLcS0015358 for <kaitlyn70@example.org>; Wed, 1 Apr 2009 14:21:39 +0200 Received: from localhost (mail.harfang.homelinux.org [83.161.120.155]) by mail.harfang.homelinux.org (Postfix) with ESMTP id 79C97617B0 for <kaitlyn70@example.org>; Wed, 1 Apr 2009 14:32:03 +0200 (CEST) Received: from mail.harfang.homelinux.org ([83.161.120.155]) by localhost (mail.harfang.homelinux.org [83.161.120.155]) (amavisd-new, port 10024) with ESMTP id jV3o9g+4RHEg for <kaitlyn70@example.org>; Wed, 1 Apr 2009 14:32:01 +0200 (CEST) Received: from dusk.harfang.homelinux.org (mail.harfang.homelinux.org [83.161.120.155]) by mail.harfang.homelinux.org (Postfix) with ESMTP id 0851261772 for <kaitlyn70@example.org>; Wed, 1 Apr 2009 14:32:00 +0200 (CEST) Received: from eran by dusk.harfang.homelinux.org with local (Exim 4.69) (envelope-from <kaitlyn70@example.org>) id 1Lozbs-0007aH-RC for kaitlyn70@example.org; Wed, 01 Apr 2009 14:32:00 +0200 Date: Wed, 1 Apr 2009 14:31:58 +0200 From: Gilles Sadowski <kaitlyn70@example.org> To: kaitlyn70@example.org Subject: Re: Problem with authentication [SOLVED] Message-ID: <kaitlyn70@example.org> References: <kaitlyn70@example.org> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <kaitlyn70@example.org> X-Operating-System: Tiny Tux X-PGP-Key-Fingerprint: 53B9 972E C2E6 B93C BEAD 7092 09E6 AF46 51D0 5641 User-Agent: Mutt/1.5.18 (2008-05-17) X-DCC-scarlet.be-Metrics: eir 20001; Body=1 Fuz1=1 Fuz2=1 X-Virus-Checked: Checked by ClamAV on apache.org Hi. Replying to my own question: > In particular, in the above log excerpt, I can't understand the lines saying: > > authentication: k='Sonatype Nexus Repository kaitlyn70@example.org' c='null' This was indeed the problem. The "Sonatype Nexus Repository Manager" string indicated above *must* be set as the "realm" attribute in <credentials>. I think that it would be worth mentioning such pitfalls in the documentation... Gilles From kaitlyn70@example.org Wed Apr 01 14:17:01 2009 Return-Path: <kaitlyn70@example.org> Delivered-To: kaitlyn70@example.org Received: (qmail 65457 invoked from network); 1 Apr 2009 14:17:01 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (83.161.120.155) by minotaur.apache.org with SMTP; 1 Apr 2009 14:17:01 -0000 Received: (qmail 5856 invoked by uid 500); 1 Apr 2009 14:17:00 -0000 Delivered-To: kaitlyn70@example.org Received: (qmail 5818 invoked by uid 500); 1 Apr 2009 14:17:00 -0000 Mailing-List: contact kaitlyn70@example.org; run by ezmlm Precedence: bulk List-Help: <mailto:kaitlyn70@example.org> List-Unsubscribe: <mailto:kaitlyn70@example.org> List-Post: <mailto:kaitlyn70@example.org> List-Id: <ivy-user.ant.apache.org> Reply-To: kaitlyn70@example.org Delivered-To: mailing list kaitlyn70@example.org Received: (qmail 5808 invoked by uid 99); 1 Apr 2009 14:17:00 -0000 Received: from nike.apache.org (HELO nike.apache.org) (83.161.120.155) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 01 Apr 2009 14:17:00 +0000 X-ASF-Spam-Status: No, hits=-1.8 required=10.0 tests=HTML_MESSAGE,RCVD_IN_DNSWL_MED,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of kaitlyn70@example.org designates 83.161.120.155 as permitted sender) Received: from [83.161.120.155] (HELO osprey.verisign.com) (83.161.120.155) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 01 Apr 2009 14:16:50 +0000 Received: from dul1wnexcn02.vcorp.ad.vrsn.com (dul1wnexcn02.vcorp.ad.vrsn.com [83.161.120.155]) by osprey.verisign.com (8.13.6/8.13.4) with ESMTP id n31E7j6q003149 for <kaitlyn70@example.org>; Wed, 1 Apr 2009 10:07:45 -0400 Received: from DUL1WNEXMB05.vcorp.ad.vrsn.com ([83.161.120.155]) by dul1wnexcn02.vcorp.ad.vrsn.com with Microsoft SMTPSVC+1-903-265-8362); Wed, 1 Apr 2009 10:16:29 -0400 x-mimeole: Produced By Microsoft Exchange V6.5 Content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----_=_NextPart_001_01C9B2D4.733A4295" Subject: Are IVY Default Repositories Mandatory? Date: Wed, 1 Apr 2009 10:16:26 -0400 Message-ID: <kaitlyn70@example.org> X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: Are IVY Default Repositories Mandatory? Thread-Index: Acmy1HGhEM0Z5leqSRC1UZ+yHFZlEQ== From: "Buck, Robert" <kaitlyn70@example.org> To: <kaitlyn70@example.org> X-OriginalArrivalTime: 01 Apr 2009 14:16:29.0689 (UTC) FILETIME=[7378FE90:01C9B2D4] X-Virus-Checked: Checked by ClamAV on apache.org ------_=_NextPart_001_01C9B2D4.733A4295 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Good morning, =20 The documentation states: =20 "This default settings mainly consist of 3 kind of repositories... First, several repositories uses the same root in your filesystem. Referenced as ${ivy.default.ivy.user.dir}, this is by default the directory .ivy2 in your user home." =20 Is this to imply that the local, shared, and public repositories are mandatory? =20 >From my use it seems that local is mandatory since though I set up my own custom resolvers, caches, and repositories, I still get stuff in ${user.home}. =20 Bob ------_=_NextPart_001_01C9B2D4.733A4295-- From kaitlyn70@example.org Wed Apr 01 14:29:02 2009 Return-Path: <kaitlyn70@example.org> Delivered-To: kaitlyn70@example.org Received: (qmail 76197 invoked from network); 1 Apr 2009 14:29:01 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (83.161.120.155) by minotaur.apache.org with SMTP; 1 Apr 2009 14:29:01 -0000 Received: (qmail 34387 invoked by uid 500); 1 Apr 2009 14:28:58 -0000 Delivered-To: kaitlyn70@example.org Received: (qmail 34289 invoked by uid 500); 1 Apr 2009 14:28:57 -0000 Mailing-List: contact kaitlyn70@example.org; run by ezmlm Precedence: bulk List-Help: <mailto:kaitlyn70@example.org> List-Unsubscribe: <mailto:kaitlyn70@example.org> List-Post: <mailto:kaitlyn70@example.org> List-Id: <ivy-user.ant.apache.org> Reply-To: kaitlyn70@example.org Delivered-To: mailing list kaitlyn70@example.org Received: (qmail 34240 invoked by uid 99); 1 Apr 2009 14:28:47 -0000 Received: from nike.apache.org (HELO nike.apache.org) (83.161.120.155) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 01 Apr 2009 14:28:47 +0000 X-ASF-Spam-Status: No, hits=-0.0 required=10.0 tests=SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: local policy) Received: from [83.161.120.155] (HELO mail.writingshow.com) (83.161.120.155) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 01 Apr 2009 14:28:38 +0000 Received: from cpe-98-149-75-20.socal.res.rr.com ([83.161.120.155] helo=[83.161.120.155]) by mail.writingshow.com with esmtpsa (TLS-1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.67) (envelope-from <kaitlyn70@example.org>) id 1Lp1Xc-0007Mg-Ba for kaitlyn70@example.org; Wed, 01 Apr 2009 09:35:44 -0500 Message-ID: <kaitlyn70@example.org> Date: Wed, 01 Apr 2009 07:28:04 -0700 From: Alan Chaney <kaitlyn70@example.org> Reply-To: kaitlyn70@example.org Organization: The Writing Show User-Agent: Thunderbird 83.161.120.155 (X11/20090107) MIME-Version: 1.0 To: kaitlyn70@example.org Subject: Re: Are IVY Default Repositories Mandatory? References: <kaitlyn70@example.org> In-Reply-To: <kaitlyn70@example.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Checked: Checked by ClamAV on apache.org Hi Robert I don' think that they are mandatory - its just that the recommended 3 repository approach is what is pre-defined in the ivy settings in the ivy jar. I found the documentation quite confusing over this, and had to experiment a lot, but I have separate repositories defined outside of ${user.home}/.ivy2 Which repository you publish to or resolve from is entirely up to you. I've a set of repositories that I use for testing the dependency management and another one that I use for team work, and I select the set of repositories by having a master property which chooses which one to use. Also, the default Ivy cache is in ${user.home}/.ivy2 - maybe that's what you are seeing (just a guess) Regards Alan Chaney Buck, Robert wrote: > Good morning, > > The documentation states: > > "This default settings mainly consist of 3 kind of repositories... > First, several repositories uses the same root in your filesystem. > Referenced as ${ivy.default.ivy.user.dir}, this is by default the > directory .ivy2 in your user home." > > Is this to imply that the local, shared, and public repositories are > mandatory? > > From my use it seems that local is mandatory since though I set up my > own custom resolvers, caches, and repositories, I still get stuff in > ${user.home}. > > Bob > > > !DSPAM:49d37936281076141877730! > > From kaitlyn70@example.org Wed Apr 01 14:49:22 2009 Return-Path: <kaitlyn70@example.org> Delivered-To: kaitlyn70@example.org Received: (qmail 88849 invoked from network); 1 Apr 2009 14:49:22 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (83.161.120.155) by minotaur.apache.org with SMTP; 1 Apr 2009 14:49:22 -0000 Received: (qmail 83874 invoked by uid 500); 1 Apr 2009 14:49:21 -0000 Delivered-To: kaitlyn70@example.org Received: (qmail 83852 invoked by uid 500); 1 Apr 2009 14:49:21 -0000 Mailing-List: contact kaitlyn70@example.org; run by ezmlm Precedence: bulk List-Help: <mailto:kaitlyn70@example.org> List-Unsubscribe: <mailto:kaitlyn70@example.org> List-Post: <mailto:kaitlyn70@example.org> List-Id: <ivy-user.ant.apache.org> Reply-To: kaitlyn70@example.org Delivered-To: mailing list kaitlyn70@example.org Received: (qmail 83805 invoked by uid 99); 1 Apr 2009 14:49:21 -0000 Received: from nike.apache.org (HELO nike.apache.org) (83.161.120.155) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 01 Apr 2009 14:49:21 +0000 X-ASF-Spam-Status: No, hits=-2.5 required=10.0 tests=RCVD_IN_DNSWL_MED,SPF_PASS,WEIRD_PORT X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of kaitlyn70@example.org designates 83.161.120.155 as permitted sender) Received: from [83.161.120.155] (HELO peregrine.verisign.com) (83.161.120.155) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 01 Apr 2009 14:49:13 +0000 Received: from dul1wnexcn01.vcorp.ad.vrsn.com (dul1wnexcn01.vcorp.ad.vrsn.com [83.161.120.155]) by peregrine.verisign.com (8.13.6/8.13.4) with ESMTP id n31Ef22f024498; Wed, 1 Apr 2009 10:41:02 -0400 Received: from DUL1WNEXMB05.vcorp.ad.vrsn.com ([83.161.120.155]) by dul1wnexcn01.vcorp.ad.vrsn.com with Microsoft SMTPSVC+1-903-265-8362); Wed, 1 Apr 2009 10:48:51 -0400 x-mimeole: Produced By Microsoft Exchange V6.5 Content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Subject: RE: Are IVY Default Repositories Mandatory? Date: Wed, 1 Apr 2009 10:48:46 -0400 Message-ID: <kaitlyn70@example.org> In-Reply-To: <kaitlyn70@example.org> X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: Are IVY Default Repositories Mandatory? Thread-Index: Acmy1jLe4y0angWOQamY/AW/Mofc4QAATiMQ From: "Buck, Robert" <kaitlyn70@example.org> To: <kaitlyn70@example.org>, <kaitlyn70@example.org> X-OriginalArrivalTime: 01 Apr 2009 14:48:51.0694 (UTC) FILETIME=[F8FF70E0:01C9B2D8] X-Virus-Checked: Checked by ClamAV on apache.org Alan, I appreciate your response. Can I ask one more question, while providing a little bit more detail? Yes, the default cache is what I am stumbling over. I thought I took care of that by eliminating it entirely until I ran into a rather nasty little issue in the build environment when the default cache had references to older third-party libraries than my build area ivy.xml files referenced. If someone said, though shalt always use "local", then I'd be happy to tweak it so it exists in my build area rather than ${user.home}. But it was my expectation that we could define an entirely different set of repositories, caches, and resolvers and would never need to use "local", and nor would any artifacts be written to a location other than in my custom definitions. So how do I disable all use of the "local" by IVY? Here are my convoluted definitions and Ant use: <?xml version=3D"1.0"?> <ivysettings> <settings defaultResolver=3D"default-chain"/> <property name=3D"ivy.volatile.repository" value=3D"${workspace.root}/ivy/repos/volatile" override=3D"false"/> <property name=3D"ivy.isolated.repository" value=3D"${sandbox.root}/ivy/repos/isolated" override=3D"false"/> <caches useOrigin=3D"true" resolutionCacheDir=3D"${workspace.root}/ivy/cache/resolution" repositoryCacheDir=3D"${workspace.root}/ivy/cache/repository"> <cache name=3D"download-cache" lockStrategy=3D"artifact-lock" basedir=3D"${sandbox.root}/ivy/cache/download" defaultTTL=3D"0ms"/> </caches> <resolvers> <filesystem name=3D"volatile-resolver"> <ivy pattern=3D"${ivy.volatile.repository}/[organisation]/[module]/[revision]/= i vys/ivy-[revision].xml"/> <artifact pattern=3D"${ivy.volatile.repository}/[organisation]/[module]/[revision]/= [ type]s/[artifact].[ext]"/> <artifact pattern=3D"${ivy.volatile.repository}/[organisation]/[module]/[revision]/= [ type]s/[artifact]-[revision].[ext]"/> </filesystem> <filesystem name=3D"isolated-resolver"> <ivy pattern=3D"${ivy.isolated.repository}/[organisation]/[module]/[revision]/= i vys/ivy-[revision].xml"/> <artifact pattern=3D"${ivy.isolated.repository}/[organisation]/[module]/[revision]/= [ type]s/[artifact].[ext]"/> <artifact pattern=3D"${ivy.isolated.repository}/[organisation]/[module]/[revision]/= [ type]s/[artifact]-[revision].[ext]"/> </filesystem> <url name=3D"download-resolver" cache=3D"download-cache"> <ivy pattern=3D"http://localhost:37373/ivyrep/[organisation]/[module]/[revisio= n ]/ivys/ivy-[revision].xml"/> <artifact pattern=3D"http://localhost:37373/ivyrep/[organisation]/[module]/[revisio= n ]/[type]s/[artifact].[ext]"/> <artifact pattern=3D"http://localhost:37373/ivyrep/[organisation]/[module]/[revisio= n ]/[type]s/[artifact]-[revision].[ext]"/> </url> <chain name=3D"default-chain" returnFirst=3D"true"> <resolver ref=3D"volatile-resolver"/> PUBLISH TO HERE LOCAL ARTIFACTS, IVYS, JARS, ETC <resolver ref=3D"isolated-resolver"/> WHERE "resolved-*.xml" and "resolved-*.properties" files go <resolver ref=3D"download-resolver"/> DOWNLOADS FROM SECURED VERISIGN IVYREP </chain> </resolvers> </ivysettings> <pathconvert property=3D"ivy.default.ivy.user.dir"> <<< NASTY = PROBLEM HERE, I THINK <path location=3D"${user.home}/.ivy"/> </pathconvert> <pathconvert property=3D"ivy.resolution.cache"> <path location=3D"${workspace.root}/ivy/cache/resolution"/> </pathconvert> <pathconvert property=3D"ivy.repository.cache"> <path location=3D"${workspace.root}/ivy/cache/repository"/> </pathconvert> <pathconvert property=3D"ivy.volatile.repos"> <path location=3D"${workspace.root}/ivy/repos/volatile"/> </pathconvert> <ivy:settings file=3D"${ivy.default.conf.dir}/ivysettings.xml"/> <target name=3D"--buildmagic-ivy-retrieve" depends=3D"--buildmagic-ivy-init" unless=3D"ivy.disable"> <ivy:retrieve pattern=3D"${ivy.local.default.root}/[organisation]/[module]/[revision]/[= a rtifact].[ext]"/> </target> <target name=3D"--buildmagic-ivy-resolve" depends=3D"--buildmagic-ivy-init,module-resolve" unless=3D"default.resolve.disable"> <ivy:resolve file=3D"${module.root}/build/ivy.xml"/> <ivy:cachepath pathid=3D"cache.classpath"/> </target> <target name=3D"--buildmagic-ivy-publish" depends=3D"module-publish" unless=3D"default.publish.disable"> <ivy:publish artifactspattern=3D"${module.output}/lib/[artifact].[ext]" resolver=3D"volatile-resolver" pubrevision=3D"${version.number}" overwrite=3D"true"/> </target>=20 -----Original Message----- From: Alan Chaney [mailto:kaitlyn70@example.org]=20 Sent: Wednesday, April 01, 2009 10:28 AM To: kaitlyn70@example.org Subject: Re: Are IVY Default Repositories Mandatory? Hi Robert I don' think that they are mandatory - its just that the recommended 3 repository approach is what is pre-defined in the ivy settings in the ivy jar. I found the documentation quite confusing over this, and had to experiment a lot, but I have separate repositories defined outside of ${user.home}/.ivy2 Which repository you publish to or resolve from is entirely up to you.=20 I've a set of repositories that I use for testing the dependency management and another one that I use for team work, and I select the set of repositories by having a master property which chooses which one to use. Also, the default Ivy cache is in ${user.home}/.ivy2 - maybe that's what you are seeing (just a guess) Regards Alan Chaney Buck, Robert wrote: > Good morning, > =20 > The documentation states: > =20 > "This default settings mainly consist of 3 kind of repositories... > First, several repositories uses the same root in your filesystem. > Referenced as ${ivy.default.ivy.user.dir}, this is by default the=20 > directory .ivy2 in your user home." > =20 > Is this to imply that the local, shared, and public repositories are=20 > mandatory? > =20 > From my use it seems that local is mandatory since though I set up my=20 > own custom resolvers, caches, and repositories, I still get stuff in=20 > ${user.home}. > =20 > Bob > > > !DSPAM:49d37936281076141877730! > > =20 From kaitlyn70@example.org Wed Apr 01 14:56:36 2009 Return-Path: <kaitlyn70@example.org> Delivered-To: kaitlyn70@example.org Received: (qmail 92777 invoked from network); 1 Apr 2009 14:56:35 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (83.161.120.155) by minotaur.apache.org with SMTP; 1 Apr 2009 14:56:35 -0000 Received: (qmail 9487 invoked by uid 500); 1 Apr 2009 14:56:35 -0000 Delivered-To: kaitlyn70@example.org Received: (qmail 9463 invoked by uid 500); 1 Apr 2009 14:56:35 -0000 Mailing-List: contact kaitlyn70@example.org; run by ezmlm Precedence: bulk List-Help: <mailto:kaitlyn70@example.org> List-Unsubscribe: <mailto:kaitlyn70@example.org> List-Post: <mailto:kaitlyn70@example.org> List-Id: <ivy-user.ant.apache.org> Reply-To: kaitlyn70@example.org Delivered-To: mailing list kaitlyn70@example.org Received: (qmail 9453 invoked by uid 99); 1 Apr 2009 14:56:35 -0000 Received: from athena.apache.org (HELO athena.apache.org) (83.161.120.155) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 01 Apr 2009 14:56:35 +0000 X-ASF-Spam-Status: No, hits=3.7 required=10.0 tests=HTML_MESSAGE,SPF_PASS,WEIRD_PORT X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of kaitlyn70@example.org designates 83.161.120.155 as permitted sender) Received: from [83.161.120.155] (HELO mail-ew0-f169.google.com) (83.161.120.155) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 01 Apr 2009 14:56:28 +0000 Received: by ewy17 with SMTP id 17so69433ewy.28 for <kaitlyn70@example.org>; Wed, 01 Apr 2009 07:56:06 -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=hfuZnrwK2p3FAZxDI8MrHwv3cDNSuASGa+wLFs3foPI=; b=k68O7WwmRLdbs5skycB/j2M06StCFFyqAHteyN6UVHJ53jV9deH+GVMdpkQBMn4BoG XToLEXhM6DXLU8TIJh2ZeI9dwf/57AMLhe2iLX236RZxAMFqsMjJv73EiSIUvRd0hH30 n8A9IOJBzYck04KYqpgHA0sb/gDXAdqg3EvvU= 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=Z0VDwCVWR8CyAiceMR+89sezZJ/B8lnjqILIhJdpddKHnv9miW0pE2qauyBdaGWq9h 9jFkHJevws6wK3R/d/WM4plg0KDHFhQ66DLHBTJryUswPlnhQTZ8qyffB39RnuxjtJsV smzMY+FWSzl4KK3E20WUV//kFB/h8odjcmftk= MIME-Version: 1.0 Received: by 83.161.120.155 with SMTP id t11mr3436248vcl.108.1238597766001; Wed, 01 Apr 2009 07:56:06 -0700 (PDT) In-Reply-To: <kaitlyn70@example.org> References: <kaitlyn70@example.org> <kaitlyn70@example.org> Date: Wed, 1 Apr 2009 10:56:05 -0400 Message-ID: <kaitlyn70@example.org> Subject: Re: Are IVY Default Repositories Mandatory? From: Sam Berlin <kaitlyn70@example.org> To: kaitlyn70@example.org Content-Type: multipart/alternative; boundary=0016e64eae66dd421504667f8318 X-Virus-Checked: Checked by ClamAV on apache.org --0016e64eae66dd421504667f8318 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Robert, I'm not sure if this is related, but I noticed a bug not so long ago with the <caches> element. I wanted to use: <caches repositoryCacheDir="${ivy.default.ivy.user.dir}/repositoryCache" resolutionCacheDir="${project.home}/.ivy2/resolutionCache" lockStrategy="artifact-lock" useOrigin="true"/> but for some reason Ivy refused to pickup the repositoryCacheDir. After changing <caches> to include a defaultCacheDir, the repositoryCacheDir was used. My <caches> element now reads: <caches defaultCacheDir="${ivy.default.ivy.user.dir}/defaultCache" repositoryCacheDir="${ivy.default.ivy.user.dir}/repositoryCache" resolutionCacheDir="${project.home}/.ivy2/resolutionCache" lockStrategy="artifact-lock" useOrigin="true"/> the defaultCacheDir is completely unused, because both repositoryCacheDir & resolutionCacheDir was specified, but it seemed to be required in order to make use of the repositoryCacheDir. Sam On Wed, Apr 1, 2009 at 10:48 AM, Buck, Robert <kaitlyn70@example.org> wrote: > Alan, I appreciate your response. Can I ask one more question, while > providing a little bit more detail? > > > Yes, the default cache is what I am stumbling over. I thought I took > care of that by eliminating it entirely until I ran into a rather nasty > little issue in the build environment when the default cache had > references to older third-party libraries than my build area ivy.xml > files referenced. > > If someone said, though shalt always use "local", then I'd be happy to > tweak it so it exists in my build area rather than ${user.home}. But it > was my expectation that we could define an entirely different set of > repositories, caches, and resolvers and would never need to use "local", > and nor would any artifacts be written to a location other than in my > custom definitions. > > So how do I disable all use of the "local" by IVY? > > Here are my convoluted definitions and Ant use: > > <?xml version="1.0"?> > <ivysettings> > <settings defaultResolver="default-chain"/> > <property name="ivy.volatile.repository" > value="${workspace.root}/ivy/repos/volatile" override="false"/> > <property name="ivy.isolated.repository" > value="${sandbox.root}/ivy/repos/isolated" override="false"/> > <caches useOrigin="true" > resolutionCacheDir="${workspace.root}/ivy/cache/resolution" > repositoryCacheDir="${workspace.root}/ivy/cache/repository"> > <cache name="download-cache" lockStrategy="artifact-lock" > basedir="${sandbox.root}/ivy/cache/download" defaultTTL="0ms"/> > </caches> > <resolvers> > <filesystem name="volatile-resolver"> > <ivy > pattern="${ivy.volatile.repository}/[organisation]/[module]/[revision]/i > vys/ivy-[revision].xml"/> > <artifact > pattern="${ivy.volatile.repository}/[organisation]/[module]/[revision]/[ > type]s/[artifact].[ext]"/> > <artifact > pattern="${ivy.volatile.repository}/[organisation]/[module]/[revision]/[ > type]s/[artifact]-[revision].[ext]"/> > </filesystem> > <filesystem name="isolated-resolver"> > <ivy > pattern="${ivy.isolated.repository}/[organisation]/[module]/[revision]/i > vys/ivy-[revision].xml"/> > <artifact > pattern="${ivy.isolated.repository}/[organisation]/[module]/[revision]/[ > type]s/[artifact].[ext]"/> > <artifact > pattern="${ivy.isolated.repository}/[organisation]/[module]/[revision]/[ > type]s/[artifact]-[revision].[ext]"/> > </filesystem> > <url name="download-resolver" cache="download-cache"> > <ivy > pattern="http://localhost:37373/ivyrep/[organisation]/[module]/[revision<http://localhost:37373/ivyrep/%5Borganisation%5D/%5Bmodule%5D/%5Brevision> > ]/ivys/ivy-[revision].xml"/> > <artifact > pattern="http://localhost:37373/ivyrep/[organisation]/[module]/[revision<http://localhost:37373/ivyrep/%5Borganisation%5D/%5Bmodule%5D/%5Brevision> > ]/[type]s/[artifact].[ext]"/> > <artifact > pattern="http://localhost:37373/ivyrep/[organisation]/[module]/[revision<http://localhost:37373/ivyrep/%5Borganisation%5D/%5Bmodule%5D/%5Brevision> > ]/[type]s/[artifact]-[revision].[ext]"/> > </url> > <chain name="default-chain" returnFirst="true"> > <resolver ref="volatile-resolver"/> PUBLISH TO HERE LOCAL > ARTIFACTS, IVYS, JARS, ETC > <resolver ref="isolated-resolver"/> WHERE "resolved-*.xml" and > "resolved-*.properties" files go > <resolver ref="download-resolver"/> DOWNLOADS FROM SECURED > VERISIGN IVYREP > </chain> > </resolvers> > </ivysettings> > > <pathconvert property="ivy.default.ivy.user.dir"> <<< NASTY PROBLEM > HERE, I THINK > <path location="${user.home}/.ivy"/> > </pathconvert> > <pathconvert property="ivy.resolution.cache"> > <path location="${workspace.root}/ivy/cache/resolution"/> > </pathconvert> > <pathconvert property="ivy.repository.cache"> > <path location="${workspace.root}/ivy/cache/repository"/> > </pathconvert> > <pathconvert property="ivy.volatile.repos"> > <path location="${workspace.root}/ivy/repos/volatile"/> > </pathconvert> > <ivy:settings file="${ivy.default.conf.dir}/ivysettings.xml"/> > > <target name="--buildmagic-ivy-retrieve" > depends="--buildmagic-ivy-init" unless="ivy.disable"> > <ivy:retrieve > pattern="${ivy.local.default.root}/[organisation]/[module]/[revision]/[a > rtifact].[ext]"/> > </target> > > <target name="--buildmagic-ivy-resolve" > depends="--buildmagic-ivy-init,module-resolve" > unless="default.resolve.disable"> > <ivy:resolve file="${module.root}/build/ivy.xml"/> > <ivy:cachepath pathid="cache.classpath"/> > </target> > > <target name="--buildmagic-ivy-publish" depends="module-publish" > unless="default.publish.disable"> > <ivy:publish > artifactspattern="${module.output}/lib/[artifact].[ext]" > resolver="volatile-resolver" pubrevision="${version.number}" > overwrite="true"/> > </target> > > -----Original Message----- > From: Alan Chaney [mailto:kaitlyn70@example.org] > Sent: Wednesday, April 01, 2009 10:28 AM > To: kaitlyn70@example.org > Subject: Re: Are IVY Default Repositories Mandatory? > > Hi Robert > > I don' think that they are mandatory - its just that the recommended 3 > repository approach is what is pre-defined in the ivy settings in the > ivy jar. > > I found the documentation quite confusing over this, and had to > experiment a lot, but I have separate repositories defined outside of > ${user.home}/.ivy2 > > Which repository you publish to or resolve from is entirely up to you. > I've a set of repositories that I use for testing the dependency > management and another one that I use for team work, and I select the > set of repositories by having a master property which chooses which one > to use. > > Also, the default Ivy cache is in ${user.home}/.ivy2 - maybe that's what > you are seeing (just a guess) > > Regards > > Alan Chaney > > > > Buck, Robert wrote: > > Good morning, > > > > The documentation states: > > > > "This default settings mainly consist of 3 kind of repositories... > > First, several repositories uses the same root in your filesystem. > > Referenced as ${ivy.default.ivy.user.dir}, this is by default the > > directory .ivy2 in your user home." > > > > Is this to imply that the local, shared, and public repositories are > > mandatory? > > > > From my use it seems that local is mandatory since though I set up my > > own custom resolvers, caches, and repositories, I still get stuff in > > ${user.home}. > > > > Bob > > > > > > !DSPAM:49d37936281076141877730! > > > > > > --0016e64eae66dd421504667f8318-- From kaitlyn70@example.org Wed Apr 01 14:58:28 2009 Return-Path: <kaitlyn70@example.org> Delivered-To: kaitlyn70@example.org Received: (qmail 93431 invoked from network); 1 Apr 2009 14:58:28 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (83.161.120.155) by minotaur.apache.org with SMTP; 1 Apr 2009 14:58:28 -0000 Received: (qmail 12833 invoked by uid 500); 1 Apr 2009 14:58:27 -0000 Delivered-To: kaitlyn70@example.org Received: (qmail 12809 invoked by uid 500); 1 Apr 2009 14:58:27 -0000 Mailing-List: contact kaitlyn70@example.org; run by ezmlm Precedence: bulk List-Help: <mailto:kaitlyn70@example.org> List-Unsubscribe: <mailto:kaitlyn70@example.org> List-Post: <mailto:kaitlyn70@example.org> List-Id: <ivy-user.ant.apache.org> Reply-To: kaitlyn70@example.org Delivered-To: mailing list kaitlyn70@example.org Received: (qmail 12799 invoked by uid 99); 1 Apr 2009 14:58:27 -0000 Received: from athena.apache.org (HELO athena.apache.org) (83.161.120.155) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 01 Apr 2009 14:58:27 +0000 X-ASF-Spam-Status: No, hits=-0.0 required=10.0 tests=SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of kaitlyn70@example.org designates 83.161.120.155 as permitted sender) Received: from [83.161.120.155] (HELO mail.softec.sk) (83.161.120.155) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 01 Apr 2009 14:58:20 +0000 Received: from postak.softec.sk (83.161.120.155) by mail.softec.sk (83.161.120.155) with Microsoft SMTP Server (TLS) id 8.1.358.0; Wed, 1 Apr 2009 16:57:56 +0200 Received: from postak.softec.sk ([83.161.120.155]) by postak.softec.sk ([83.161.120.155]) with mapi; Wed, 1 Apr 2009 16:57:58 +0200 From: =?iso-8859-2?Q?Bl=B9t=E1k_Peter?= <kaitlyn70@example.org> To: "kaitlyn70@example.org" <kaitlyn70@example.org> Date: Wed, 1 Apr 2009 16:57:57 +0200 Subject: Getting source files for transitive dependencies from maven2 ??? Thread-Topic: Getting source files for transitive dependencies from maven2 ??? Thread-Index: Acmy1jLe4y0angWOQamY/AW/Mofc4QAATiMQAACBwuA= Message-ID: <kaitlyn70@example.org> References: <kaitlyn70@example.org> <kaitlyn70@example.org> In-Reply-To: <kaitlyn70@example.org> Accept-Language: en-US, sk-SK Content-Language: en-US X-MS-Has-Attach: X-MS-TNEF-Correlator: acceptlanguage: en-US, sk-SK Content-Type: text/plain; charset="iso-8859-2" Content-Transfer-Encoding: quoted-printable MIME-Version: 1.0 X-Virus-Checked: Checked by ClamAV on apache.org Hi Is it possible to get source files for transitive dependencies from maven2 = repositories ??? I have tried IvyDE to download my dependency "org.apache.tapestry#tapestry-= core;83.161.120.155" I have got sources for tapestry-core but not for its dependencies (like tap= estry-ioc, ....). Is there any option to make it work ? Thanks Peter Blstak From kaitlyn70@example.org Wed Apr 01 15:04:46 2009 Return-Path: <kaitlyn70@example.org> Delivered-To: kaitlyn70@example.org Received: (qmail 97204 invoked from network); 1 Apr 2009 15:04:45 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (83.161.120.155) by minotaur.apache.org with SMTP; 1 Apr 2009 15:04:45 -0000 Received: (qmail 37695 invoked by uid 500); 1 Apr 2009 15:04:45 -0000 Delivered-To: kaitlyn70@example.org Received: (qmail 37656 invoked by uid 500); 1 Apr 2009 15:04:45 -0000 Mailing-List: contact kaitlyn70@example.org; run by ezmlm Precedence: bulk List-Help: <mailto:kaitlyn70@example.org> List-Unsubscribe: <mailto:kaitlyn70@example.org> List-Post: <mailto:kaitlyn70@example.org> List-Id: <ivy-user.ant.apache.org> Reply-To: kaitlyn70@example.org Delivered-To: mailing list kaitlyn70@example.org Received: (qmail 37646 invoked by uid 99); 1 Apr 2009 15:04:45 -0000 Received: from athena.apache.org (HELO athena.apache.org) (83.161.120.155) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 01 Apr 2009 15:04:45 +0000 X-ASF-Spam-Status: No, hits=1.5 required=10.0 tests=SPF_PASS,WEIRD_PORT X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: local policy) Received: from [83.161.120.155] (HELO mail.writingshow.com) (83.161.120.155) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 01 Apr 2009 15:04:37 +0000 Received: from cpe-98-149-75-20.socal.res.rr.com ([83.161.120.155] helo=[83.161.120.155]) by mail.writingshow.com with esmtpsa (TLS-1.0:DHE_RSA_AES_256_CBC_SHA1:32) (Exim 4.67) (envelope-from <kaitlyn70@example.org>) id 1Lp26Q-0007YM-Ee for kaitlyn70@example.org; Wed, 01 Apr 2009 10:11:42 -0500 Message-ID: <kaitlyn70@example.org> Date: Wed, 01 Apr 2009 08:04:06 -0700 From: Alan Chaney <kaitlyn70@example.org> Reply-To: kaitlyn70@example.org Organization: The Writing Show User-Agent: Thunderbird 83.161.120.155 (X11/20090107) MIME-Version: 1.0 To: kaitlyn70@example.org Subject: Re: Are IVY Default Repositories Mandatory? References: <kaitlyn70@example.org> <kaitlyn70@example.org> <kaitlyn70@example.org> In-Reply-To: <kaitlyn70@example.org> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Checked: Checked by ClamAV on apache.org Sam and Robert Sam Berlin wrote: > Robert, ... > > > On Wed, Apr 1, 2009 at 10:48 AM, Buck, Robert <kaitlyn70@example.org> wrote: > > >> Yes, the default cache is what I am stumbling over. I thought I took >> care of that by eliminating it entirely until I ran into a rather nasty >> little issue in the build environment when the default cache had >> references to older third-party libraries than my build area ivy.xml >> files referenced. >> >> Ok - I think that Sam's comments may be the relevant ones here. I've never bothered to move my cache from the default location. Your original question was about the 'local' repository - presumably this is now where you wanted it to be? As a further comment to your point above the general problem with any cache is knowing when to flush it! It may be that Sam's comments would move the cache location properly. However, I have also found it necessary to add a task to my ant build which allows me to flush the cache and rebuild everything, which is often necessary after modifications to the build structure or extensive changes to the build files. I seem to remember other discussions on this list about caching which it might be good to look at. Regards Alan >> If someone said, though shalt always use "local", then I'd be happy to >> tweak it so it exists in my build area rather than ${user.home}. But it >> was my expectation that we could define an entirely different set of >> repositories, caches, and resolvers and would never need to use "local", >> and nor would any artifacts be written to a location other than in my >> custom definitions. >> >> So how do I disable all use of the "local" by IVY? >> >> Here are my convoluted definitions and Ant use: >> >> <?xml version="1.0"?> >> <ivysettings> >> <settings defaultResolver="default-chain"/> >> <property name="ivy.volatile.repository" >> value="${workspace.root}/ivy/repos/volatile" override="false"/> >> <property name="ivy.isolated.repository" >> value="${sandbox.root}/ivy/repos/isolated" override="false"/> >> <caches useOrigin="true" >> resolutionCacheDir="${workspace.root}/ivy/cache/resolution" >> repositoryCacheDir="${workspace.root}/ivy/cache/repository"> >> <cache name="download-cache" lockStrategy="artifact-lock" >> basedir="${sandbox.root}/ivy/cache/download" defaultTTL="0ms"/> >> </caches> >> <resolvers> >> <filesystem name="volatile-resolver"> >> <ivy >> pattern="${ivy.volatile.repository}/[organisation]/[module]/[revision]/i >> vys/ivy-[revision].xml"/> >> <artifact >> pattern="${ivy.volatile.repository}/[organisation]/[module]/[revision]/[ >> type]s/[artifact].[ext]"/> >> <artifact >> pattern="${ivy.volatile.repository}/[organisation]/[module]/[revision]/[ >> type]s/[artifact]-[revision].[ext]"/> >> </filesystem> >> <filesystem name="isolated-resolver"> >> <ivy >> pattern="${ivy.isolated.repository}/[organisation]/[module]/[revision]/i >> vys/ivy-[revision].xml"/> >> <artifact >> pattern="${ivy.isolated.repository}/[organisation]/[module]/[revision]/[ >> type]s/[artifact].[ext]"/> >> <artifact >> pattern="${ivy.isolated.repository}/[organisation]/[module]/[revision]/[ >> type]s/[artifact]-[revision].[ext]"/> >> </filesystem> >> <url name="download-resolver" cache="download-cache"> >> <ivy >> pattern="http://localhost:37373/ivyrep/[organisation]/[module]/[revision<http://localhost:37373/ivyrep/%5Borganisation%5D/%5Bmodule%5D/%5Brevision> >> ]/ivys/ivy-[revision].xml"/> >> <artifact >> pattern="http://localhost:37373/ivyrep/[organisation]/[module]/[revision<http://localhost:37373/ivyrep/%5Borganisation%5D/%5Bmodule%5D/%5Brevision> >> ]/[type]s/[artifact].[ext]"/> >> <artifact >> pattern="http://localhost:37373/ivyrep/[organisation]/[module]/[revision<http://localhost:37373/ivyrep/%5Borganisation%5D/%5Bmodule%5D/%5Brevision> >> ]/[type]s/[artifact]-[revision].[ext]"/> >> </url> >> <chain name="default-chain" returnFirst="true"> >> <resolver ref="volatile-resolver"/> PUBLISH TO HERE LOCAL >> ARTIFACTS, IVYS, JARS, ETC >> <resolver ref="isolated-resolver"/> WHERE "resolved-*.xml" and >> "resolved-*.properties" files go >> <resolver ref="download-resolver"/> DOWNLOADS FROM SECURED >> VERISIGN IVYREP >> </chain> >> </resolvers> >> </ivysettings> >> >> <pathconvert property="ivy.default.ivy.user.dir"> <<< NASTY PROBLEM >> HERE, I THINK >> <path location="${user.home}/.ivy"/> >> </pathconvert> >> <pathconvert property="ivy.resolution.cache"> >> <path location="${workspace.root}/ivy/cache/resolution"/> >> </pathconvert> >> <pathconvert property="ivy.repository.cache"> >> <path location="${workspace.root}/ivy/cache/repository"/> >> </pathconvert> >> <pathconvert property="ivy.volatile.repos"> >> <path location="${workspace.root}/ivy/repos/volatile"/> >> </pathconvert> >> <ivy:settings file="${ivy.default.conf.dir}/ivysettings.xml"/> >> >> <target name="--buildmagic-ivy-retrieve" >> depends="--buildmagic-ivy-init" unless="ivy.disable"> >> <ivy:retrieve >> pattern="${ivy.local.default.root}/[organisation]/[module]/[revision]/[a >> rtifact].[ext]"/> >> </target> >> >> <target name="--buildmagic-ivy-resolve" >> depends="--buildmagic-ivy-init,module-resolve" >> unless="default.resolve.disable"> >> <ivy:resolve file="${module.root}/build/ivy.xml"/> >> <ivy:cachepath pathid="cache.classpath"/> >> </target> >> >> <target name="--buildmagic-ivy-publish" depends="module-publish" >> unless="default.publish.disable"> >> <ivy:publish >> artifactspattern="${module.output}/lib/[artifact].[ext]" >> resolver="volatile-resolver" pubrevision="${version.number}" >> overwrite="true"/> >> </target> >> >> -----Original Message----- >> From: Alan Chaney [mailto:kaitlyn70@example.org] >> Sent: Wednesday, April 01, 2009 10:28 AM >> To: kaitlyn70@example.org >> Subject: Re: Are IVY Default Repositories Mandatory? >> >> Hi Robert >> >> I don' think that they are mandatory - its just that the recommended 3 >> repository approach is what is pre-defined in the ivy settings in the >> ivy jar. >> >> I found the documentation quite confusing over this, and had to >> experiment a lot, but I have separate repositories defined outside of >> ${user.home}/.ivy2 >> >> Which repository you publish to or resolve from is entirely up to you. >> I've a set of repositories that I use for testing the dependency >> management and another one that I use for team work, and I select the >> set of repositories by having a master property which chooses which one >> to use. >> >> Also, the default Ivy cache is in ${user.home}/.ivy2 - maybe that's what >> you are seeing (just a guess) >> >> Regards >> >> Alan Chaney >> >> >> >> Buck, Robert wrote: >> >>> Good morning, >>> >>> The documentation states: >>> >>> "This default settings mainly consist of 3 kind of repositories... >>> First, several repositories uses the same root in your filesystem. >>> Referenced as ${ivy.default.ivy.user.dir}, this is by default the >>> directory .ivy2 in your user home." >>> >>> Is this to imply that the local, shared, and public repositories are >>> mandatory? >>> >>> From my use it seems that local is mandatory since though I set up my >>> own custom resolvers, caches, and repositories, I still get stuff in >>> ${user.home}. >>> >>> Bob >>> >>> >>> >>> >>> >>> >> > > > !DSPAM:49d38278289041381456296! > > From kaitlyn70@example.org Wed Apr 01 15:57:41 2009 Return-Path: <kaitlyn70@example.org> Delivered-To: kaitlyn70@example.org Received: (qmail 20378 invoked from network); 1 Apr 2009 15:57:41 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (83.161.120.155) by minotaur.apache.org with SMTP; 1 Apr 2009 15:57:41 -0000 Received: (qmail 62097 invoked by uid 500); 1 Apr 2009 15:57:41 -0000 Delivered-To: kaitlyn70@example.org Received: (qmail 62039 invoked by uid 500); 1 Apr 2009 15:57:40 -0000 Mailing-List: contact kaitlyn70@example.org; run by ezmlm Precedence: bulk List-Help: <mailto:kaitlyn70@example.org> List-Unsubscribe: <mailto:kaitlyn70@example.org> List-Post: <mailto:kaitlyn70@example.org> List-Id: <ivy-user.ant.apache.org> Reply-To: kaitlyn70@example.org Delivered-To: mailing list kaitlyn70@example.org Received: (qmail 62028 invoked by uid 99); 1 Apr 2009 15:57:40 -0000 Received: from athena.apache.org (HELO athena.apache.org) (83.161.120.155) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 01 Apr 2009 15:57:40 +0000 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 (athena.apache.org: domain of kaitlyn70@example.org designates 83.161.120.155 as permitted sender) Received: from [83.161.120.155] (HELO osprey.verisign.com) (83.161.120.155) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 01 Apr 2009 15:57:34 +0000 Received: from dul1wnexcn03.vcorp.ad.vrsn.com (dul1wnexcn03.vcorp.ad.vrsn.com [83.161.120.155]) by osprey.verisign.com (8.13.6/8.13.4) with ESMTP id n31FmSqe008631 for <kaitlyn70@example.org>; Wed, 1 Apr 2009 11:48:28 -0400 Received: from DUL1WNEXMB05.vcorp.ad.vrsn.com ([83.161.120.155]) by dul1wnexcn03.vcorp.ad.vrsn.com with Microsoft SMTPSVC+1-903-265-8362); Wed, 1 Apr 2009 16:57:12 +0100 x-mimeole: Produced By Microsoft Exchange V6.5 Content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Subject: IVY Default Properties and Descriptions Date: Wed, 1 Apr 2009 11:57:09 -0400 Message-ID: <kaitlyn70@example.org> In-Reply-To: <kaitlyn70@example.org> X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: IVY Default Properties and Descriptions Thread-Index: Acmy2zKRr01k6vRlQc+Pq7Zolzyk8wABlDag From: "Buck, Robert" <kaitlyn70@example.org> To: <kaitlyn70@example.org> X-OriginalArrivalTime: 01 Apr 2009 15:57:12.0502 (UTC) FILETIME=[85451560:01C9B2E2] X-Virus-Checked: Checked by ClamAV on apache.org It would seem there is little documentation that I can find on the default IVY properties. Or is there? Here are a few key properties it would seem: * ivy.default.conf.dir - WHAT IS THIS??? * ivy.default.settings.dir - a variable which is always set to the place where ivy default settings files are * ivy.default.ivy.user.dir - the root in your filesystem used for several default repositories including local, shared and public; defaults to ${user.home}/.ivy2 * ???OTHERS??? Are there any other properties out there that people should be aware of? Bob From kaitlyn70@example.org Wed Apr 01 16:04:45 2009 Return-Path: <kaitlyn70@example.org> Delivered-To: kaitlyn70@example.org Received: (qmail 23682 invoked from network); 1 Apr 2009 16:04:43 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (83.161.120.155) by minotaur.apache.org with SMTP; 1 Apr 2009 16:04:43 -0000 Received: (qmail 76791 invoked by uid 500); 1 Apr 2009 16:04:43 -0000 Delivered-To: kaitlyn70@example.org Received: (qmail 76761 invoked by uid 500); 1 Apr 2009 16:04:43 -0000 Mailing-List: contact kaitlyn70@example.org; run by ezmlm Precedence: bulk List-Help: <mailto:kaitlyn70@example.org> List-Unsubscribe: <mailto:kaitlyn70@example.org> List-Post: <mailto:kaitlyn70@example.org> List-Id: <ivy-user.ant.apache.org> Reply-To: kaitlyn70@example.org Delivered-To: mailing list kaitlyn70@example.org Received: (qmail 76751 invoked by uid 99); 1 Apr 2009 16:04:43 -0000 Received: from athena.apache.org (HELO athena.apache.org) (83.161.120.155) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 01 Apr 2009 16:04:43 +0000 X-ASF-Spam-Status: No, hits=-2.5 required=10.0 tests=RCVD_IN_DNSWL_MED,SPF_PASS,WEIRD_PORT X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of kaitlyn70@example.org designates 83.161.120.155 as permitted sender) Received: from [83.161.120.155] (HELO osprey.verisign.com) (83.161.120.155) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 01 Apr 2009 16:04:36 +0000 Received: from dul1wnexcn03.vcorp.ad.vrsn.com (dul1wnexcn03.vcorp.ad.vrsn.com [83.161.120.155]) by osprey.verisign.com (8.13.6/8.13.4) with ESMTP id n31FtVVc008947; Wed, 1 Apr 2009 11:55:31 -0400 Received: from DUL1WNEXMB05.vcorp.ad.vrsn.com ([83.161.120.155]) by dul1wnexcn03.vcorp.ad.vrsn.com with Microsoft SMTPSVC+1-903-265-8362); Wed, 1 Apr 2009 17:04:15 +0100 x-mimeole: Produced By Microsoft Exchange V6.5 Content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: quoted-printable Subject: RE: Are IVY Default Repositories Mandatory? Date: Wed, 1 Apr 2009 12:04:12 -0400 Message-ID: <kaitlyn70@example.org> In-Reply-To: <kaitlyn70@example.org> X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: Are IVY Default Repositories Mandatory? Thread-Index: Acmy2zKRr01k6vRlQc+Pq7Zolzyk8wAB8HnA From: "Buck, Robert" <kaitlyn70@example.org> To: <kaitlyn70@example.org>, <kaitlyn70@example.org> X-OriginalArrivalTime: 01 Apr 2009 16:04:15.0726 (UTC) FILETIME=[8187F0E0:01C9B2E3] X-Virus-Checked: Checked by ClamAV on apache.org Alan and Sam, Thank you so much! Adding this definition to Ant resolved this: <pathconvert property=3D"ivy.default.ivy.user.dir"> <path location=3D"${workspace.root}/ivy"/> </pathconvert> And in combination with a "clobber" target that not only deletes build artifacts but also deletes the ${workspace.root}/ivy directory entirely, each workspace (multiple: release, instrumented) within a sandbox (all sharing a common branch spec) can run entirely concurrently with respect to one another. This change fixed my issues. Woohoo! <caches useOrigin=3D"true" resolutionCacheDir=3D"${workspace.root}/ivy/cache/resolution" repositoryCacheDir=3D"${workspace.root}/ivy/cache/repository"> <cache name=3D"download-cache" lockStrategy=3D"artifact-lock" basedir=3D"${sandbox.root}/ivy/cache/download" defaultTTL=3D"0ms"/> </caches> Are there any recommendations for properties such as defaultTTL (or others I failed to set) that I should consider setting them to? Again, thanks, Bob -----Original Message----- From: Alan Chaney [mailto:kaitlyn70@example.org]=20 Sent: Wednesday, April 01, 2009 11:04 AM To: kaitlyn70@example.org Subject: Re: Are IVY Default Repositories Mandatory? Sam and Robert Sam Berlin wrote: > Robert, ... > =20 > > On Wed, Apr 1, 2009 at 10:48 AM, Buck, Robert <kaitlyn70@example.org> wrote: > > =20 >> Yes, the default cache is what I am stumbling over. I thought I took=20 >> care of that by eliminating it entirely until I ran into a rather=20 >> nasty little issue in the build environment when the default cache=20 >> had references to older third-party libraries than my build area=20 >> ivy.xml files referenced. >> >> =20 Ok - I think that Sam's comments may be the relevant ones here. I've never bothered to move my cache from the default location. Your original question was about the 'local' repository - presumably this is now where you wanted it to be? As a further comment to your point above the general problem with any cache is knowing when to flush it! It may be that Sam's comments would move the cache location properly. However, I have also found it necessary to add a task to my ant build which allows me to flush the cache and rebuild everything, which is often necessary after modifications to the build structure or extensive changes to the build files. I seem to remember other discussions on this list about caching which it might be good to look at. Regards Alan >> If someone said, though shalt always use "local", then I'd be happy=20 >> to tweak it so it exists in my build area rather than ${user.home}.=20 >> But it was my expectation that we could define an entirely different=20 >> set of repositories, caches, and resolvers and would never need to=20 >> use "local", and nor would any artifacts be written to a location=20 >> other than in my custom definitions. >> >> So how do I disable all use of the "local" by IVY? >> >> Here are my convoluted definitions and Ant use: >> >> <?xml version=3D"1.0"?> >> <ivysettings> >> <settings defaultResolver=3D"default-chain"/> <property=20 >> name=3D"ivy.volatile.repository" >> value=3D"${workspace.root}/ivy/repos/volatile" override=3D"false"/> =20 >> <property name=3D"ivy.isolated.repository" >> value=3D"${sandbox.root}/ivy/repos/isolated" override=3D"false"/> =20 >> <caches useOrigin=3D"true" >> resolutionCacheDir=3D"${workspace.root}/ivy/cache/resolution" >> repositoryCacheDir=3D"${workspace.root}/ivy/cache/repository"> >> <cache name=3D"download-cache" lockStrategy=3D"artifact-lock" >> basedir=3D"${sandbox.root}/ivy/cache/download" defaultTTL=3D"0ms"/> =20 >> </caches> <resolvers> >> <filesystem name=3D"volatile-resolver"> >> <ivy >> = pattern=3D"${ivy.volatile.repository}/[organisation]/[module]/[revision >> ]/i >> vys/ivy-[revision].xml"/> >> <artifact >> = pattern=3D"${ivy.volatile.repository}/[organisation]/[module]/[revision >> ]/[ >> type]s/[artifact].[ext]"/> >> <artifact >> = pattern=3D"${ivy.volatile.repository}/[organisation]/[module]/[revision >> ]/[ type]s/[artifact]-[revision].[ext]"/> >> </filesystem> >> <filesystem name=3D"isolated-resolver"> >> <ivy >> = pattern=3D"${ivy.isolated.repository}/[organisation]/[module]/[revision >> ]/i >> vys/ivy-[revision].xml"/> >> <artifact >> = pattern=3D"${ivy.isolated.repository}/[organisation]/[module]/[revision >> ]/[ >> type]s/[artifact].[ext]"/> >> <artifact >> = pattern=3D"${ivy.isolated.repository}/[organisation]/[module]/[revision >> ]/[ type]s/[artifact]-[revision].[ext]"/> >> </filesystem> >> <url name=3D"download-resolver" cache=3D"download-cache"> >> <ivy >> = pattern=3D"http://localhost:37373/ivyrep/[organisation]/[module]/[revis >> ion<http://localhost:37373/ivyrep/%5Borganisation%5D/%5Bmodule%5D/%5B >> revision> >> ]/ivys/ivy-[revision].xml"/> >> <artifact >> = pattern=3D"http://localhost:37373/ivyrep/[organisation]/[module]/[revis >> ion<http://localhost:37373/ivyrep/%5Borganisation%5D/%5Bmodule%5D/%5B >> revision> >> ]/[type]s/[artifact].[ext]"/> >> <artifact >> = pattern=3D"http://localhost:37373/ivyrep/[organisation]/[module]/[revis >> ion<http://localhost:37373/ivyrep/%5Borganisation%5D/%5Bmodule%5D/%5B >> revision> ]/[type]s/[artifact]-[revision].[ext]"/> >> </url> >> <chain name=3D"default-chain" returnFirst=3D"true"> >> <resolver ref=3D"volatile-resolver"/> PUBLISH TO HERE LOCAL=20 >> ARTIFACTS, IVYS, JARS, ETC >> <resolver ref=3D"isolated-resolver"/> WHERE "resolved-*.xml" = and=20 >> "resolved-*.properties" files go >> <resolver ref=3D"download-resolver"/> DOWNLOADS FROM SECURED=20 >> VERISIGN IVYREP >> </chain> >> </resolvers> >> </ivysettings> >> >> <pathconvert property=3D"ivy.default.ivy.user.dir"> <<< NASTY=20 >> PROBLEM HERE, I THINK >> <path location=3D"${user.home}/.ivy"/> >> </pathconvert> >> <pathconvert property=3D"ivy.resolution.cache"> >> <path location=3D"${workspace.root}/ivy/cache/resolution"/> >> </pathconvert> >> <pathconvert property=3D"ivy.repository.cache"> >> <path location=3D"${workspace.root}/ivy/cache/repository"/> >> </pathconvert> >> <pathconvert property=3D"ivy.volatile.repos"> >> <path location=3D"${workspace.root}/ivy/repos/volatile"/> >> </pathconvert> >> <ivy:settings file=3D"${ivy.default.conf.dir}/ivysettings.xml"/> >> >> <target name=3D"--buildmagic-ivy-retrieve" >> depends=3D"--buildmagic-ivy-init" unless=3D"ivy.disable"> >> <ivy:retrieve >> = pattern=3D"${ivy.local.default.root}/[organisation]/[module]/[revision] >> /[a >> rtifact].[ext]"/> >> </target> >> >> <target name=3D"--buildmagic-ivy-resolve" >> depends=3D"--buildmagic-ivy-init,module-resolve" >> unless=3D"default.resolve.disable"> >> <ivy:resolve file=3D"${module.root}/build/ivy.xml"/> >> <ivy:cachepath pathid=3D"cache.classpath"/> </target> >> >> <target name=3D"--buildmagic-ivy-publish" depends=3D"module-publish" >> unless=3D"default.publish.disable"> >> <ivy:publish >> artifactspattern=3D"${module.output}/lib/[artifact].[ext]" >> resolver=3D"volatile-resolver" pubrevision=3D"${version.number}" >> overwrite=3D"true"/> >> </target> >> >> -----Original Message----- >> From: Alan Chaney [mailto:kaitlyn70@example.org] >> Sent: Wednesday, April 01, 2009 10:28 AM >> To: kaitlyn70@example.org >> Subject: Re: Are IVY Default Repositories Mandatory? >> >> Hi Robert >> >> I don' think that they are mandatory - its just that the recommended=20 >> 3 repository approach is what is pre-defined in the ivy settings in=20 >> the ivy jar. >> >> I found the documentation quite confusing over this, and had to=20 >> experiment a lot, but I have separate repositories defined outside of >> ${user.home}/.ivy2 >> >> Which repository you publish to or resolve from is entirely up to you. >> I've a set of repositories that I use for testing the dependency=20 >> management and another one that I use for team work, and I select the >> set of repositories by having a master property which chooses which=20 >> one to use. >> >> Also, the default Ivy cache is in ${user.home}/.ivy2 - maybe that's=20 >> what you are seeing (just a guess) >> >> Regards >> >> Alan Chaney >> >> >> >> Buck, Robert wrote: >> =20 >>> Good morning, >>> >>> The documentation states: >>> >>> "This default settings mainly consist of 3 kind of repositories... >>> First, several repositories uses the same root in your filesystem. >>> Referenced as ${ivy.default.ivy.user.dir}, this is by default the=20 >>> directory .ivy2 in your user home." >>> >>> Is this to imply that the local, shared, and public repositories are >>> mandatory? >>> >>> From my use it seems that local is mandatory since though I set up=20 >>> my own custom resolvers, caches, and repositories, I still get stuff >>> in ${user.home}. >>> >>> Bob >>> >>> >>> >>> >>> >>> =20 >> =20 > > > !DSPAM:49d38278289041381456296! > > =20 From kaitlyn70@example.org Wed Apr 01 16:09:01 2009 Return-Path: <kaitlyn70@example.org> Delivered-To: kaitlyn70@example.org Received: (qmail 25402 invoked from network); 1 Apr 2009 16:09:01 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (83.161.120.155) by minotaur.apache.org with SMTP; 1 Apr 2009 16:09:01 -0000 Received: (qmail 89685 invoked by uid 500); 1 Apr 2009 16:09:00 -0000 Delivered-To: kaitlyn70@example.org Received: (qmail 89665 invoked by uid 500); 1 Apr 2009 16:09:00 -0000 Mailing-List: contact kaitlyn70@example.org; run by ezmlm Precedence: bulk List-Help: <mailto:kaitlyn70@example.org> List-Unsubscribe: <mailto:kaitlyn70@example.org> List-Post: <mailto:kaitlyn70@example.org> List-Id: <ivy-user.ant.apache.org> Reply-To: kaitlyn70@example.org Delivered-To: mailing list kaitlyn70@example.org Received: (qmail 89655 invoked by uid 99); 1 Apr 2009 16:09:00 -0000 Received: from nike.apache.org (HELO nike.apache.org) (83.161.120.155) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 01 Apr 2009 16:09:00 +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 (nike.apache.org: domain of kaitlyn70@example.org designates 83.161.120.155 as permitted sender) Received: from [83.161.120.155] (HELO wf-out-1314.google.com) (83.161.120.155) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 01 Apr 2009 16:08:52 +0000 Received: by wf-out-1314.google.com with SMTP id 28so110187wfc.10 for <kaitlyn70@example.org>; Wed, 01 Apr 2009 09:08:31 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:sender:received:in-reply-to :references:date:x-google-sender-auth:message-id:subject:from:to :content-type; bh=B93JK/vukYNugPKAUYpMr8yM2ogE1ClJPNh5Na/4FJI=; b=pnCol+OU9UkWduS1n5M/ruQS7habCQTQsynCnkfh28JVRybftNwEx+41kzlX0iPIRT IP6GneKYAPtgHQBc8Uj/AlwLV1pDy3EFjo8hZeQRiQ08JUW3RQiNmzuTXia10tuUy36X 1uYYOyz/JJp60VIzQ8C8Kx77FXPzf/LnxFffM= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:sender:in-reply-to:references:date :x-google-sender-auth:message-id:subject:from:to:content-type; b=vsmDzOZhH0jteH69GNJqKa537+m29cw4eFK3vwZvT89dbDOMSqe+QSqQaP18S1oG90 Eh0b1pij9aFL3E7SyRzfnIKOpeMwPF+r9alX5nHnSQZo+5PpQeMquCfTJZw8CuQpFEun hgB+nAn0A7RKYWzB0S5Iy2Q5dtQFr5LyCxQ6s= MIME-Version: 1.0 Sender: kaitlyn70@example.org Received: by 83.161.120.155 with SMTP id c20mr3179658wff.174.1238602111612; Wed, 01 Apr 2009 09:08:31 -0700 (PDT) In-Reply-To: <kaitlyn70@example.org> References: <kaitlyn70@example.org> <kaitlyn70@example.org> Date: Wed, 1 Apr 2009 09:08:31 -0700 X-Google-Sender-Auth: 0331dc88c28cd404 Message-ID: <kaitlyn70@example.org> Subject: Re: IVY Default Properties and Descriptions From: Joshua Tharp <kaitlyn70@example.org> To: kaitlyn70@example.org Content-Type: multipart/alternative; boundary=000e0cd1744ee179f204668086ff X-Virus-Checked: Checked by ClamAV on apache.org --000e0cd1744ee179f204668086ff Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit I used the optional Ant task echoproperties to get a complete list. It doesn't tell you where they are used, but most of those I could guess from the name of the property. On Wed, Apr 1, 2009 at 8:57 AM, Buck, Robert <kaitlyn70@example.org> wrote: > It would seem there is little documentation that I can find on the > default IVY properties. Or is there? > > Here are a few key properties it would seem: > > * ivy.default.conf.dir - WHAT IS THIS??? > * ivy.default.settings.dir - a variable which is always set to the > place where ivy default settings files are > * ivy.default.ivy.user.dir - the root in your filesystem used for > several default repositories including local, shared and public; > defaults to ${user.home}/.ivy2 > * ???OTHERS??? > > Are there any other properties out there that people should be aware of? > > Bob > --000e0cd1744ee179f204668086ff-- From kaitlyn70@example.org Fri Apr 03 03:44:37 2009 Return-Path: <kaitlyn70@example.org> Delivered-To: kaitlyn70@example.org Received: (qmail 89974 invoked from network); 3 Apr 2009 03:44:37 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (83.161.120.155) by minotaur.apache.org with SMTP; 3 Apr 2009 03:44:37 -0000 Received: (qmail 9959 invoked by uid 500); 3 Apr 2009 03:44:37 -0000 Delivered-To: kaitlyn70@example.org Received: (qmail 9901 invoked by uid 500); 3 Apr 2009 03:44:37 -0000 Mailing-List: contact kaitlyn70@example.org; run by ezmlm Precedence: bulk List-Help: <mailto:kaitlyn70@example.org> List-Unsubscribe: <mailto:kaitlyn70@example.org> List-Post: <mailto:kaitlyn70@example.org> List-Id: <ivy-user.ant.apache.org> Reply-To: kaitlyn70@example.org Delivered-To: mailing list kaitlyn70@example.org Delivered-To: moderator for kaitlyn70@example.org Received: (qmail 40890 invoked by uid 99); 2 Apr 2009 18:06:05 -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 kaitlyn70@example.org designates 83.161.120.155 as permitted sender) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=domainkey-signature:mime-version:received:date:message-id:subject :from:to:content-type; bh=bt0U1Jjz0dJCqEgtd7Jm4lrDlzSjKocId23//dP8WUY=; b=nufDemilldd6TZ8Coj41EqZB39knOt5vSAFv26tbU2FWLIbZ7wNE6WdT/v/rRAwS3S yMBUcWjbMs4mgsDlYH6ZlG2rJSfzgwwGq0y/bnvWBg5hAO3GXMUPjOgPH7Nkr5uAa7z5 lv57mrV1qej3wNjIEmpk6agZxItMvQKunU0uE= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=mime-version:date:message-id:subject:from:to:content-type; b=b4AS5/uTw+/gT9DkLsJgdDLysr1z9lk1ar2BkTlhCIPBxh1spRYYuo0Ihu1aT/Fshw s+BBu6bT+4Mpi20m7KFDzaECg/+HjgBW+YMXwEC4M7zpBKM+6Z8Z6ha/3NP0MHb6nymu AzZvm/Q4TpSxfH1j6Rx3l+sq1D0pTeTXk/dxg= MIME-Version: 1.0 Date: Thu, 2 Apr 2009 11:05:37 -0700 Message-ID: <kaitlyn70@example.org> Subject: Unresolved Dependencies - What Am I Doing Wrong? From: Gordon Leland Hempton <kaitlyn70@example.org> To: kaitlyn70@example.org Content-Type: multipart/alternative; boundary=001636e90cdd81d6b5046696471a X-Virus-Checked: Checked by ClamAV on apache.org --001636e90cdd81d6b5046696471a Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit I am trying to incorporate ivy as the dependency manager for our project. I have created my own repository using the ivy install command, however when I try and add my own modules to the repository I get the following error when another module depends on them: [ivy:resolve] WARN: 888a:dbb7:2d49:b3f6:8605:bf4e:caed:e5a4888a:dbb7:2d49:b3f6:8605:bf4e:caed:e5a4888a:dbb7:2d49:b3f6:8605:bf4e:caed:e5a4888a:dbb7:2d49:b3f6:8605:bf4e:caed:e5a4888a:dbb7:2d49:b3f6:8605:bf4e:caed:e5a4888a:dbb7:2d49:b3f6:8605:bf4e:caed:e5a4888a:dbb7:2d49:b3f6:8605:bf4e:caed:e5a4888a:dbb7:2d49:b3f6:8605:bf4e:caed:e5a4888a:dbb7:2d49:b3f6:8605:bf4e:caed:e5a4888a:dbb7:2d49:b3f6:8605:bf4e:caed:e5a4888a:dbb7:2d49:b3f6:8605:bf4e:caed:e5a4888a:dbb7:2d49:b3f6:8605:bf4e:caed:e5a4888a:dbb7:2d49:b3f6:8605:bf4e:caed:e5a4888a:dbb7:2d49:b3f6:8605:bf4e:caed:e5a4888a:dbb7:2d49:b3f6:8605:bf4e:caed:e5a4888a:dbb7:2d49:b3f6:8605:bf4e:caed:e5a4888a:dbb7:2d49:b3f6:8605:bf4e:caed:e5a4888a:dbb7:2d49:b3f6:8605:bf4e:caed:e5a4888a:dbb7:2d49:b3f6:8605:bf4e:caed:e5a4888a:dbb7:2d49:b3f6:8605:bf4e:caed:e5a4888a:dbb7:2d49:b3f6:8605:bf4e:caed:e5a4888a:dbb7:2d49:b3f6:8605:bf4e:caed:e5a4888a:dbb7:2d49:b3f6:8605:bf4e:caed:e5a4 [ivy:resolve] WARN: 888a:dbb7:2d49:b3f6:8605:bf4e:caed:e5a4 UNRESOLVED DEPENDENCIES 888a:dbb7:2d49:b3f6:8605:bf4e:caed:e5a4 [ivy:resolve] WARN: 888a:dbb7:2d49:b3f6:8605:bf4e:caed:e5a4888a:dbb7:2d49:b3f6:8605:bf4e:caed:e5a4888a:dbb7:2d49:b3f6:8605:bf4e:caed:e5a4888a:dbb7:2d49:b3f6:8605:bf4e:caed:e5a4888a:dbb7:2d49:b3f6:8605:bf4e:caed:e5a4888a:dbb7:2d49:b3f6:8605:bf4e:caed:e5a4888a:dbb7:2d49:b3f6:8605:bf4e:caed:e5a4888a:dbb7:2d49:b3f6:8605:bf4e:caed:e5a4888a:dbb7:2d49:b3f6:8605:bf4e:caed:e5a4888a:dbb7:2d49:b3f6:8605:bf4e:caed:e5a4888a:dbb7:2d49:b3f6:8605:bf4e:caed:e5a4888a:dbb7:2d49:b3f6:8605:bf4e:caed:e5a4888a:dbb7:2d49:b3f6:8605:bf4e:caed:e5a4888a:dbb7:2d49:b3f6:8605:bf4e:caed:e5a4888a:dbb7:2d49:b3f6:8605:bf4e:caed:e5a4888a:dbb7:2d49:b3f6:8605:bf4e:caed:e5a4888a:dbb7:2d49:b3f6:8605:bf4e:caed:e5a4888a:dbb7:2d49:b3f6:8605:bf4e:caed:e5a4888a:dbb7:2d49:b3f6:8605:bf4e:caed:e5a4888a:dbb7:2d49:b3f6:8605:bf4e:caed:e5a4888a:dbb7:2d49:b3f6:8605:bf4e:caed:e5a4888a:dbb7:2d49:b3f6:8605:bf4e:caed:e5a4888a:dbb7:2d49:b3f6:8605:bf4e:caed:e5a4 [ivy:resolve] WARN: 888a:dbb7:2d49:b3f6:8605:bf4e:caed:e5a4 net.jthink#jaudiotagger;1.0.9: kaitlyn70@example.org(Unknown Source) [ivy:resolve] WARN: 888a:dbb7:2d49:b3f6:8605:bf4e:caed:e5a4888a:dbb7:2d49:b3f6:8605:bf4e:caed:e5a4888a:dbb7:2d49:b3f6:8605:bf4e:caed:e5a4888a:dbb7:2d49:b3f6:8605:bf4e:caed:e5a4888a:dbb7:2d49:b3f6:8605:bf4e:caed:e5a4888a:dbb7:2d49:b3f6:8605:bf4e:caed:e5a4888a:dbb7:2d49:b3f6:8605:bf4e:caed:e5a4888a:dbb7:2d49:b3f6:8605:bf4e:caed:e5a4888a:dbb7:2d49:b3f6:8605:bf4e:caed:e5a4888a:dbb7:2d49:b3f6:8605:bf4e:caed:e5a4888a:dbb7:2d49:b3f6:8605:bf4e:caed:e5a4888a:dbb7:2d49:b3f6:8605:bf4e:caed:e5a4888a:dbb7:2d49:b3f6:8605:bf4e:caed:e5a4888a:dbb7:2d49:b3f6:8605:bf4e:caed:e5a4888a:dbb7:2d49:b3f6:8605:bf4e:caed:e5a4888a:dbb7:2d49:b3f6:8605:bf4e:caed:e5a4888a:dbb7:2d49:b3f6:8605:bf4e:caed:e5a4888a:dbb7:2d49:b3f6:8605:bf4e:caed:e5a4888a:dbb7:2d49:b3f6:8605:bf4e:caed:e5a4888a:dbb7:2d49:b3f6:8605:bf4e:caed:e5a4888a:dbb7:2d49:b3f6:8605:bf4e:caed:e5a4888a:dbb7:2d49:b3f6:8605:bf4e:caed:e5a4888a:dbb7:2d49:b3f6:8605:bf4e:caed:e5a4 [ivy:resolve] report for com.designbyparts#oakland-site;working@ghempton-desktop default produced in C:\Users\Gordon\.ivy2\cache\com.designbyparts-oakland-site-default.xml [ivy:resolve] resolve done (1189ms resolve - 96ms download) [ivy:resolve] 888a:dbb7:2d49:b3f6:8605:bf4e:caed:e5a4 problems summary 888a:dbb7:2d49:b3f6:8605:bf4e:caed:e5a4 [ivy:resolve] 888a:dbb7:2d49:b3f6:8605:bf4e:caed:e5a4888a:dbb7:2d49:b3f6:8605:bf4e:caed:e5a4 WARNINGS [ivy:resolve] 888a:dbb7:2d49:b3f6:8605:bf4e:caed:e5a4888a:dbb7:2d49:b3f6:8605:bf4e:caed:e5a4888a:dbb7:2d49:b3f6:8605:bf4e:caed:e5a4888a:dbb7:2d49:b3f6:8605:bf4e:caed:e5a4888a:dbb7:2d49:b3f6:8605:bf4e:caed:e5a4888a:dbb7:2d49:b3f6:8605:bf4e:caed:e5a4888a:dbb7:2d49:b3f6:8605:bf4e:caed:e5a4888a:dbb7:2d49:b3f6:8605:bf4e:caed:e5a4888a:dbb7:2d49:b3f6:8605:bf4e:caed:e5a4888a:dbb7:2d49:b3f6:8605:bf4e:caed:e5a4888a:dbb7:2d49:b3f6:8605:bf4e:caed:e5a4888a:dbb7:2d49:b3f6:8605:bf4e:caed:e5a4888a:dbb7:2d49:b3f6:8605:bf4e:caed:e5a4888a:dbb7:2d49:b3f6:8605:bf4e:caed:e5a4888a:dbb7:2d49:b3f6:8605:bf4e:caed:e5a4888a:dbb7:2d49:b3f6:8605:bf4e:caed:e5a4888a:dbb7:2d49:b3f6:8605:bf4e:caed:e5a4888a:dbb7:2d49:b3f6:8605:bf4e:caed:e5a4888a:dbb7:2d49:b3f6:8605:bf4e:caed:e5a4888a:dbb7:2d49:b3f6:8605:bf4e:caed:e5a4888a:dbb7:2d49:b3f6:8605:bf4e:caed:e5a4888a:dbb7:2d49:b3f6:8605:bf4e:caed:e5a4888a:dbb7:2d49:b3f6:8605:bf4e:caed:e5a4 [ivy:resolve] 888a:dbb7:2d49:b3f6:8605:bf4e:caed:e5a4 UNRESOLVED DEPENDENCIES 888a:dbb7:2d49:b3f6:8605:bf4e:caed:e5a4 [ivy:resolve] 888a:dbb7:2d49:b3f6:8605:bf4e:caed:e5a4888a:dbb7:2d49:b3f6:8605:bf4e:caed:e5a4888a:dbb7:2d49:b3f6:8605:bf4e:caed:e5a4888a:dbb7:2d49:b3f6:8605:bf4e:caed:e5a4888a:dbb7:2d49:b3f6:8605:bf4e:caed:e5a4888a:dbb7:2d49:b3f6:8605:bf4e:caed:e5a4888a:dbb7:2d49:b3f6:8605:bf4e:caed:e5a4888a:dbb7:2d49:b3f6:8605:bf4e:caed:e5a4888a:dbb7:2d49:b3f6:8605:bf4e:caed:e5a4888a:dbb7:2d49:b3f6:8605:bf4e:caed:e5a4888a:dbb7:2d49:b3f6:8605:bf4e:caed:e5a4888a:dbb7:2d49:b3f6:8605:bf4e:caed:e5a4888a:dbb7:2d49:b3f6:8605:bf4e:caed:e5a4888a:dbb7:2d49:b3f6:8605:bf4e:caed:e5a4888a:dbb7:2d49:b3f6:8605:bf4e:caed:e5a4888a:dbb7:2d49:b3f6:8605:bf4e:caed:e5a4888a:dbb7:2d49:b3f6:8605:bf4e:caed:e5a4888a:dbb7:2d49:b3f6:8605:bf4e:caed:e5a4888a:dbb7:2d49:b3f6:8605:bf4e:caed:e5a4888a:dbb7:2d49:b3f6:8605:bf4e:caed:e5a4888a:dbb7:2d49:b3f6:8605:bf4e:caed:e5a4888a:dbb7:2d49:b3f6:8605:bf4e:caed:e5a4888a:dbb7:2d49:b3f6:8605:bf4e:caed:e5a4 [ivy:resolve] 888a:dbb7:2d49:b3f6:8605:bf4e:caed:e5a4 net.jthink#jaudiotagger;1.0.9: kaitlyn70@example.org(Unknown Source) BUILD FAILED C:\projects\oakland\branches\prototype\site\build.xml:119: impossible to resolve dependencies: resolve failed - see output for kaitlyn70@example.org(IvyResolve.java:315) at org.apache.ivy.ant.IvyTask.execute(IvyTask.java:277) at org.apache.tools.ant.UnknownElement.execute(UnknownElement.java:288) at sun.reflect.GeneratedMethodAccessor1.invoke(Unknown Source) ... My ivy file for the module is as follows: <?xml version="1.0" encoding="UTF-8"?> <ivy-module version="2.0" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:noNamespaceSchemaLocation= "http://ant.apache.org/ivy/schemas/ivy.xsd"> <info organisation="net.jthink" module="jaudiotagger" revision="1.0.9"> <description homepage="http://www.jthink.net/jaudiotagger/"> Audio tagging library </description> </info> <configurations> <conf name="default" visibility="public" /> <conf name="sources" visibility="public" /> </configurations> <publications> <artifact name="jaudiotagger" type="jar" ext="jar" conf="default" /> <artifact name="jaudiotagger" type="source" ext="jar" conf="sources" /> </publications> </ivy-module> And the repository pattern matches up with the resolver and is the same as all of the other modules which I installed through the ivy install task. One thing this module doesn't have is the md5 and sha1 checksums, does that matter? Am I missing anything? I am using Ivy 2.0.0. Thanks for your help, Gordon --001636e90cdd81d6b5046696471a-- From kaitlyn70@example.org Fri Apr 03 03:44:46 2009 Return-Path: <kaitlyn70@example.org> Delivered-To: kaitlyn70@example.org Received: (qmail 90015 invoked from network); 3 Apr 2009 03:44:46 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (83.161.120.155) by minotaur.apache.org with SMTP; 3 Apr 2009 03:44:46 -0000 Received: (qmail 10287 invoked by uid 500); 3 Apr 2009 03:44:46 -0000 Delivered-To: kaitlyn70@example.org Received: (qmail 10251 invoked by uid 500); 3 Apr 2009 03:44:46 -0000 Mailing-List: contact kaitlyn70@example.org; run by ezmlm Precedence: bulk List-Help: <mailto:kaitlyn70@example.org> List-Unsubscribe: <mailto:kaitlyn70@example.org> List-Post: <mailto:kaitlyn70@example.org> List-Id: <ivy-user.ant.apache.org> Reply-To: kaitlyn70@example.org Delivered-To: mailing list kaitlyn70@example.org Delivered-To: moderator for kaitlyn70@example.org Received: (qmail 19206 invoked by uid 99); 2 Apr 2009 20:58:37 -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 (nike.apache.org: domain of kaitlyn70@example.org designates 83.161.120.155 as permitted sender) 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=/2ZZGfsAUDtaQlp/yU7gFz6ci+Wyb8viEp0R527kR1Q=; b=heyPQu+tCpN5yXhP2usQun39mELTEOuIKPKIPOnqSbIWq0dJVbhVgqKZAFGH8mBmSG 4RZXAEtWJhQCI3IJrPk7vKT64p1YSHBZYXwCwxYbxyF4nDPH9PTFF19i4d4FhFo2eA1L 8AU2ruSC9uinpdcTIkU+ENg2zYFCOouydxfFs= 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=v7fyIRRm5dPH6bo757o5jUKmGmHjQOey5KdjaBaojCQocxUJJ6XgwUZoJkJqaP59Xz t0F0UJp+s6u6SrTG3mZnlzMVd7OIgjkxcxbI30oLBtRUtRxYm2gLaJSWp6Vsd5vXBZ98 cs4KnJUA7QA3SLhEgJhL3UMJo2+xFtf6k4ybk= MIME-Version: 1.0 In-Reply-To: <kaitlyn70@example.org> References: <kaitlyn70@example.org> Date: Thu, 2 Apr 2009 13:58:05 -0700 Message-ID: <kaitlyn70@example.org> Subject: Re: Unresolved Dependencies - What Am I Doing Wrong? From: Gordon Leland Hempton <kaitlyn70@example.org> To: kaitlyn70@example.org Content-Type: multipart/alternative; boundary=001636e907294f98ba046698b00c X-Virus-Checked: Checked by ClamAV on apache.org --001636e907294f98ba046698b00c Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit FYI, I fixed the issue by putting the module in the repository using the ivy:publish task instead of doing it manually. It seems to have an identical effect on the repository except for the inclusion of the md5 and sha1 checksums, so I assume they are required. -Gordon On Thu, Apr 2, 2009 at 11:05 AM, Gordon Leland Hempton <kaitlyn70@example.org>wrote: > I am trying to incorporate ivy as the dependency manager for our project. I > have created my own repository using the ivy install command, however when I > try and add my own modules to the repository I get the following error when > another module depends on them: > [ivy:resolve] WARN: 888a:dbb7:2d49:b3f6:8605:bf4e:caed:e5a4888a:dbb7:2d49:b3f6:8605:bf4e:caed:e5a4888a:dbb7:2d49:b3f6:8605:bf4e:caed:e5a4888a:dbb7:2d49:b3f6:8605:bf4e:caed:e5a4888a:dbb7:2d49:b3f6:8605:bf4e:caed:e5a4888a:dbb7:2d49:b3f6:8605:bf4e:caed:e5a4888a:dbb7:2d49:b3f6:8605:bf4e:caed:e5a4888a:dbb7:2d49:b3f6:8605:bf4e:caed:e5a4888a:dbb7:2d49:b3f6:8605:bf4e:caed:e5a4888a:dbb7:2d49:b3f6:8605:bf4e:caed:e5a4888a:dbb7:2d49:b3f6:8605:bf4e:caed:e5a4888a:dbb7:2d49:b3f6:8605:bf4e:caed:e5a4888a:dbb7:2d49:b3f6:8605:bf4e:caed:e5a4888a:dbb7:2d49:b3f6:8605:bf4e:caed:e5a4888a:dbb7:2d49:b3f6:8605:bf4e:caed:e5a4888a:dbb7:2d49:b3f6:8605:bf4e:caed:e5a4888a:dbb7:2d49:b3f6:8605:bf4e:caed:e5a4888a:dbb7:2d49:b3f6:8605:bf4e:caed:e5a4888a:dbb7:2d49:b3f6:8605:bf4e:caed:e5a4888a:dbb7:2d49:b3f6:8605:bf4e:caed:e5a4888a:dbb7:2d49:b3f6:8605:bf4e:caed:e5a4888a:dbb7:2d49:b3f6:8605:bf4e:caed:e5a4888a:dbb7:2d49:b3f6:8605:bf4e:caed:e5a4 > [ivy:resolve] WARN: 888a:dbb7:2d49:b3f6:8605:bf4e:caed:e5a4 UNRESOLVED DEPENDENCIES 888a:dbb7:2d49:b3f6:8605:bf4e:caed:e5a4 > [ivy:resolve] WARN: 888a:dbb7:2d49:b3f6:8605:bf4e:caed:e5a4888a:dbb7:2d49:b3f6:8605:bf4e:caed:e5a4888a:dbb7:2d49:b3f6:8605:bf4e:caed:e5a4888a:dbb7:2d49:b3f6:8605:bf4e:caed:e5a4888a:dbb7:2d49:b3f6:8605:bf4e:caed:e5a4888a:dbb7:2d49:b3f6:8605:bf4e:caed:e5a4888a:dbb7:2d49:b3f6:8605:bf4e:caed:e5a4888a:dbb7:2d49:b3f6:8605:bf4e:caed:e5a4888a:dbb7:2d49:b3f6:8605:bf4e:caed:e5a4888a:dbb7:2d49:b3f6:8605:bf4e:caed:e5a4888a:dbb7:2d49:b3f6:8605:bf4e:caed:e5a4888a:dbb7:2d49:b3f6:8605:bf4e:caed:e5a4888a:dbb7:2d49:b3f6:8605:bf4e:caed:e5a4888a:dbb7:2d49:b3f6:8605:bf4e:caed:e5a4888a:dbb7:2d49:b3f6:8605:bf4e:caed:e5a4888a:dbb7:2d49:b3f6:8605:bf4e:caed:e5a4888a:dbb7:2d49:b3f6:8605:bf4e:caed:e5a4888a:dbb7:2d49:b3f6:8605:bf4e:caed:e5a4888a:dbb7:2d49:b3f6:8605:bf4e:caed:e5a4888a:dbb7:2d49:b3f6:8605:bf4e:caed:e5a4888a:dbb7:2d49:b3f6:8605:bf4e:caed:e5a4888a:dbb7:2d49:b3f6:8605:bf4e:caed:e5a4888a:dbb7:2d49:b3f6:8605:bf4e:caed:e5a4 > [ivy:resolve] WARN: 888a:dbb7:2d49:b3f6:8605:bf4e:caed:e5a4 net.jthink#jaudiotagger;1.0.9: > kaitlyn70@example.org(Unknown Source) > [ivy:resolve] WARN: 888a:dbb7:2d49:b3f6:8605:bf4e:caed:e5a4888a:dbb7:2d49:b3f6:8605:bf4e:caed:e5a4888a:dbb7:2d49:b3f6:8605:bf4e:caed:e5a4888a:dbb7:2d49:b3f6:8605:bf4e:caed:e5a4888a:dbb7:2d49:b3f6:8605:bf4e:caed:e5a4888a:dbb7:2d49:b3f6:8605:bf4e:caed:e5a4888a:dbb7:2d49:b3f6:8605:bf4e:caed:e5a4888a:dbb7:2d49:b3f6:8605:bf4e:caed:e5a4888a:dbb7:2d49:b3f6:8605:bf4e:caed:e5a4888a:dbb7:2d49:b3f6:8605:bf4e:caed:e5a4888a:dbb7:2d49:b3f6:8605:bf4e:caed:e5a4888a:dbb7:2d49:b3f6:8605:bf4e:caed:e5a4888a:dbb7:2d49:b3f6:8605:bf4e:caed:e5a4888a:dbb7:2d49:b3f6:8605:bf4e:caed:e5a4888a:dbb7:2d49:b3f6:8605:bf4e:caed:e5a4888a:dbb7:2d49:b3f6:8605:bf4e:caed:e5a4888a:dbb7:2d49:b3f6:8605:bf4e:caed:e5a4888a:dbb7:2d49:b3f6:8605:bf4e:caed:e5a4888a:dbb7:2d49:b3f6:8605:bf4e:caed:e5a4888a:dbb7:2d49:b3f6:8605:bf4e:caed:e5a4888a:dbb7:2d49:b3f6:8605:bf4e:caed:e5a4888a:dbb7:2d49:b3f6:8605:bf4e:caed:e5a4888a:dbb7:2d49:b3f6:8605:bf4e:caed:e5a4 > [ivy:resolve] report for > com.designbyparts#oakland-site;working@ghempton-desktop default produced > in C:\Users\Gordon\.ivy2\cache\com.designbyparts-oakland-site-default.xml > [ivy:resolve] resolve done (1189ms resolve - 96ms download) > [ivy:resolve] 888a:dbb7:2d49:b3f6:8605:bf4e:caed:e5a4 problems summary 888a:dbb7:2d49:b3f6:8605:bf4e:caed:e5a4 > [ivy:resolve] 888a:dbb7:2d49:b3f6:8605:bf4e:caed:e5a4888a:dbb7:2d49:b3f6:8605:bf4e:caed:e5a4 WARNINGS > [ivy:resolve] 888a:dbb7:2d49:b3f6:8605:bf4e:caed:e5a4888a:dbb7:2d49:b3f6:8605:bf4e:caed:e5a4888a:dbb7:2d49:b3f6:8605:bf4e:caed:e5a4888a:dbb7:2d49:b3f6:8605:bf4e:caed:e5a4888a:dbb7:2d49:b3f6:8605:bf4e:caed:e5a4888a:dbb7:2d49:b3f6:8605:bf4e:caed:e5a4888a:dbb7:2d49:b3f6:8605:bf4e:caed:e5a4888a:dbb7:2d49:b3f6:8605:bf4e:caed:e5a4888a:dbb7:2d49:b3f6:8605:bf4e:caed:e5a4888a:dbb7:2d49:b3f6:8605:bf4e:caed:e5a4888a:dbb7:2d49:b3f6:8605:bf4e:caed:e5a4888a:dbb7:2d49:b3f6:8605:bf4e:caed:e5a4888a:dbb7:2d49:b3f6:8605:bf4e:caed:e5a4888a:dbb7:2d49:b3f6:8605:bf4e:caed:e5a4888a:dbb7:2d49:b3f6:8605:bf4e:caed:e5a4888a:dbb7:2d49:b3f6:8605:bf4e:caed:e5a4888a:dbb7:2d49:b3f6:8605:bf4e:caed:e5a4888a:dbb7:2d49:b3f6:8605:bf4e:caed:e5a4888a:dbb7:2d49:b3f6:8605:bf4e:caed:e5a4888a:dbb7:2d49:b3f6:8605:bf4e:caed:e5a4888a:dbb7:2d49:b3f6:8605:bf4e:caed:e5a4888a:dbb7:2d49:b3f6:8605:bf4e:caed:e5a4888a:dbb7:2d49:b3f6:8605:bf4e:caed:e5a4 > [ivy:resolve] 888a:dbb7:2d49:b3f6:8605:bf4e:caed:e5a4 UNRESOLVED DEPENDENCIES 888a:dbb7:2d49:b3f6:8605:bf4e:caed:e5a4 > [ivy:resolve] 888a:dbb7:2d49:b3f6:8605:bf4e:caed:e5a4888a:dbb7:2d49:b3f6:8605:bf4e:caed:e5a4888a:dbb7:2d49:b3f6:8605:bf4e:caed:e5a4888a:dbb7:2d49:b3f6:8605:bf4e:caed:e5a4888a:dbb7:2d49:b3f6:8605:bf4e:caed:e5a4888a:dbb7:2d49:b3f6:8605:bf4e:caed:e5a4888a:dbb7:2d49:b3f6:8605:bf4e:caed:e5a4888a:dbb7:2d49:b3f6:8605:bf4e:caed:e5a4888a:dbb7:2d49:b3f6:8605:bf4e:caed:e5a4888a:dbb7:2d49:b3f6:8605:bf4e:caed:e5a4888a:dbb7:2d49:b3f6:8605:bf4e:caed:e5a4888a:dbb7:2d49:b3f6:8605:bf4e:caed:e5a4888a:dbb7:2d49:b3f6:8605:bf4e:caed:e5a4888a:dbb7:2d49:b3f6:8605:bf4e:caed:e5a4888a:dbb7:2d49:b3f6:8605:bf4e:caed:e5a4888a:dbb7:2d49:b3f6:8605:bf4e:caed:e5a4888a:dbb7:2d49:b3f6:8605:bf4e:caed:e5a4888a:dbb7:2d49:b3f6:8605:bf4e:caed:e5a4888a:dbb7:2d49:b3f6:8605:bf4e:caed:e5a4888a:dbb7:2d49:b3f6:8605:bf4e:caed:e5a4888a:dbb7:2d49:b3f6:8605:bf4e:caed:e5a4888a:dbb7:2d49:b3f6:8605:bf4e:caed:e5a4888a:dbb7:2d49:b3f6:8605:bf4e:caed:e5a4 > [ivy:resolve] 888a:dbb7:2d49:b3f6:8605:bf4e:caed:e5a4 net.jthink#jaudiotagger;1.0.9: > kaitlyn70@example.org(Unknown Source) > > BUILD FAILED > C:\projects\oakland\branches\prototype\site\build.xml:119: impossible to > resolve dependencies: > resolve failed - see output for details > at org.apache.ivy.ant.IvyResolve.doExecute(IvyResolve.java:315) > at org.apache.ivy.ant.IvyTask.execute(IvyTask.java:277) > at org.apache.tools.ant.UnknownElement.execute(UnknownElement.java:288) > at sun.reflect.GeneratedMethodAccessor1.invoke(Unknown Source) > ... > > My ivy file for the module is as follows: > > <?xml version="1.0" encoding="UTF-8"?> > <ivy-module version="2.0" > xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" > xsi:noNamespaceSchemaLocation= > "http://ant.apache.org/ivy/schemas/ivy.xsd"> > <info organisation="net.jthink" > module="jaudiotagger" > revision="1.0.9"> > <description homepage="http://www.jthink.net/jaudiotagger/"> > Audio tagging library > </description> > </info> > <configurations> > <conf name="default" visibility="public" /> > <conf name="sources" visibility="public" /> > </configurations> > <publications> > <artifact name="jaudiotagger" type="jar" ext="jar" conf="default" /> > <artifact name="jaudiotagger" type="source" ext="jar" conf="sources" /> > </publications> > </ivy-module> > > And the repository pattern matches up with the resolver and is the same as > all of the other modules which I installed through the ivy install task. One > thing this module doesn't have is the md5 and sha1 checksums, does that > matter? Am I missing anything? I am using Ivy 2.0.0. > > Thanks for your help, > Gordon > --001636e907294f98ba046698b00c-- From kaitlyn70@example.org Fri Apr 03 06:55:04 2009 Return-Path: <kaitlyn70@example.org> Delivered-To: kaitlyn70@example.org Received: (qmail 73005 invoked from network); 3 Apr 2009 06:55:04 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (83.161.120.155) by minotaur.apache.org with SMTP; 3 Apr 2009 06:55:04 -0000 Received: (qmail 45471 invoked by uid 500); 3 Apr 2009 06:55:03 -0000 Delivered-To: kaitlyn70@example.org Received: (qmail 45418 invoked by uid 500); 3 Apr 2009 06:55:03 -0000 Mailing-List: contact kaitlyn70@example.org; run by ezmlm Precedence: bulk List-Help: <mailto:kaitlyn70@example.org> List-Unsubscribe: <mailto:kaitlyn70@example.org> List-Post: <mailto:kaitlyn70@example.org> List-Id: <ivy-user.ant.apache.org> Reply-To: kaitlyn70@example.org Delivered-To: mailing list kaitlyn70@example.org Received: (qmail 45408 invoked by uid 99); 3 Apr 2009 06:55:03 -0000 Received: from athena.apache.org (HELO athena.apache.org) (83.161.120.155) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 03 Apr 2009 06:55:03 +0000 X-ASF-Spam-Status: No, hits=-0.0 required=10.0 tests=SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: local policy) Received: from [83.161.120.155] (HELO web30806.mail.mud.yahoo.com) (83.161.120.155) by apache.org (qpsmtpd/0.29) with SMTP; Fri, 03 Apr 2009 06:54:55 +0000 Received: (qmail 32291 invoked by uid 60001); 3 Apr 2009 06:54:34 -0000 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yahoo.com; s=s1024; t=1238741674; bh=1gSTLqgBz4jhZVxqZQ7LINkJ/S5kDqXU4B2bm/Z9nXQ=; h=Message-ID:X-YMail-OSG:Received:X-Mailer:Date:From:Subject:To:MIME-Version:Content-Type; b=EQ1VTF6wEY74t3/nVHgUhgkmFM+GTGIMsWfMhOX+WOuwm623qwYcgQ+tNHB3mhspgA+rifUp5tftUA5FFW3VnQ5QILJFlh8kuD5NGkHJG3dWpzdB3wRmN6Nsi4Z4IeOmDrU/f74D1vALr2aNwrQJZnokrsVvyxNZRlkxrKO+Q4s= DomainKey-Signature:a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com; h=Message-ID:X-YMail-OSG:Received:X-Mailer:Date:From:Subject:To:MIME-Version:Content-Type; b=LX/ezWH+X/cSP8TdtbimPXDwgRD/PJaq2NDfMxWqMuTyemf+AKFftTC1wGSWgbz5rGaE9UWggQ8tUJnnNm57MCC8zOhreNuxasbJCp9uh63y0um19NYsqc4HJkERSTbhwYh7zzZtlouo3XXoZOxvhWMecGWucG33gFbtTX2798Y=; Message-ID: <kaitlyn70@example.org> X-YMail-OSG: 4llMQzwVM1lZXd3I1mRJ29Ay72fjq9dWd2B5jdVnYUx8e9fh2FI2_pGBKGkMt.Ux9qSabAJx7fw1PhFMnk3vD5WHu3thC2Rv9ZT2eW6jQ8i7eoF3q7fkueSQmG4U.J5gl9Rq14eqyXWdp0bXIuSxKCjoE3UYHGo8UPF6vxyNuZccUzVc99J10uOnphmmGOTbeiDjcayL1ezbFg7urh6cfpvtLmEDiZldaCGcy.4jMi4OwTzUYqL.fqHBP2a7HSG8jIWWsgmp_360O2d.mmC8o8YQSIrSqHBH_S7fghuoafKfiLb_FrlxO26SHC3lyRExZK2ui_z6Z4BJ9XMJ8xsIfZA- Received: from [83.161.120.155] by web30806.mail.mud.yahoo.com via HTTP; Thu, 02 Apr 2009 23:54:34 PDT X-Mailer: YahooMailRC/1277.32 YahooMailWebService/0.7.289.1 Date: Thu, 2 Apr
{'source': 'Apache Software Foundation Public Mail Archives'}