Return-Path: Delivered-To: apmail-ant-ivy-user-archive@www.apache.org Received: (qmail 79820 invoked from network); 30 Mar 2008 21:28:30 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 30 Mar 2008 21:28:30 -0000 Received: (qmail 38681 invoked by uid 500); 30 Mar 2008 21:28:30 -0000 Delivered-To: apmail-ant-ivy-user-archive@ant.apache.org Received: (qmail 38655 invoked by uid 500); 30 Mar 2008 21:28:30 -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 38646 invoked by uid 99); 30 Mar 2008 21:28:30 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Sun, 30 Mar 2008 14:28:30 -0700 X-ASF-Spam-Status: No, hits=2.0 required=10.0 tests=HTML_MESSAGE,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (athena.apache.org: domain of xavier.hanin@gmail.com designates 209.85.200.175 as permitted sender) Received: from [209.85.200.175] (HELO wf-out-1314.google.com) (209.85.200.175) by apache.org (qpsmtpd/0.29) with ESMTP; Sun, 30 Mar 2008 21:27:47 +0000 Received: by wf-out-1314.google.com with SMTP id 27so1216009wfd.10 for ; Sun, 30 Mar 2008 14:27:59 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=beta; h=domainkey-signature:received:received:message-id:date:from:to:subject:in-reply-to:mime-version:content-type:references; bh=sLiZsBJnPlCx6psfWnfDQpsdcW4nPhZa0tiQze7CD7Q=; b=EBFM574KizYBr+AWTAJTE0AymwPseR68/ifopstXfvuv+d43tp5lZ+U4M3B0/uw7HxWe3BQTBa931jsWVLQcE+1lVjWqrTvGYSV68kxd/0GAKExOGvov4i8Efa470jbWALrKeUOBCDLg63vtpp6rl96E7zj8cZOkFDke/6DOAcs= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=message-id:date:from:to:subject:in-reply-to:mime-version:content-type:references; b=L5fweP+SDBnRx40d4wawFfGYQvdewuUC4+N6XzfF5W9m+YPijO12y4RDl0LfBEknOntl0gyD/AM5+jii4DFEFEOv8gwQi2QkFI/A05LonxkAEsGyqhb+ZNHcjHu7aC4TwAkAW6n4ffcH3t2409a9zA+SukaphxLGssXyeXObmO8= Received: by 10.142.47.6 with SMTP id u6mr3295700wfu.29.1206912479173; Sun, 30 Mar 2008 14:27:59 -0700 (PDT) Received: by 10.142.73.7 with HTTP; Sun, 30 Mar 2008 14:27:59 -0700 (PDT) Message-ID: <635a05060803301427he987ed1j39a53ae41d95e40e@mail.gmail.com> Date: Sun, 30 Mar 2008 23:27:59 +0200 From: "Xavier Hanin" To: ivy-user@ant.apache.org Subject: Re: ivy.original.xml cache bug? In-Reply-To: <745B9EDF57802349B13F90E4E0B4B86C3B9F1D5A80@HOUEXCH012.corp.halliburton.com> MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_Part_10461_7373810.1206912479167" References: <745B9EDF57802349B13F90E4E0B4B86C3B9F1D5A80@HOUEXCH012.corp.halliburton.com> X-Virus-Checked: Checked by ClamAV on apache.org ------=_Part_10461_7373810.1206912479167 Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline On Sun, Mar 30, 2008 at 8:23 PM, Shawn Castrianni < Shawn.Castrianni@halliburton.com> wrote: > I have a caches tag like this: > > artifactPattern="${lgcbuild.releaseName > }/[module]/[branch]/[revision]/[type]/[home]/[homeType]/[path]/[artifact].[ext]"/> > > which includes my custom attributes of [home], [homeType], and [path]. In > my ivy.xml files, some of these custom attributes are filled out and some > are left as empty strings. The empty strings allow them to be ignored when > used as directories. Everything seems to work fine for the publish, > resolve, and retrieve. However, my cache is not quite right. The ivy.xmlis properly using the ivyPattern above in my caches tag, however, there is > some other ivy.original.xml file that seems to be using the > artifactPattern. Because it is using the artifactPattern AND there is no > value at all for my custom attributes (not even an empty string), the cache > is placing the ivy.original.xml file into subdirectories with "[home]", > "[homeType]", and "[path]" as names. This ivy.original.xml file is > probably a new file as a result of an enhancement recently implemented in > IVY 2 to retain original dependency information. Let's say it's part of the change in cache management, now we cache the module descriptor exactly as downloaded, before storing it in ivy format (when you use a pom the difference is more obvious). > > Regardless, I would think the ivy.original.xml file should probably also > use the ivyPattern in the cache and not the artifactPattern?? The problem is that people may not use the [artifact] token in ivy cache pattern, and since we use this token to make the difference between the original file and the converted one, we could run into name collisions in this case. But maybe using the artifact token is not a good idea, maybe we should try to append a suffix to the ivy file path instead (like .original). Please open an issue about this problem, and we'll see what's the best option to solve the problem considering what I just said. Xavier > > > --- > Shawn Castrianni > > ---------------------------------------------------------------------- > This e-mail, including any attached files, may contain confidential and > privileged information for the sole use of the intended recipient. Any > review, use, distribution, or disclosure by others is strictly prohibited. > If you are not the intended recipient (or authorized to receive information > for the intended recipient), please contact the sender by reply e-mail and > delete all copies of this message. -- Xavier Hanin - Independent Java Consultant http://xhab.blogspot.com/ http://ant.apache.org/ivy/ http://www.xoocode.org/ ------=_Part_10461_7373810.1206912479167--