Return-Path: Delivered-To: apmail-ant-dev-archive@www.apache.org Received: (qmail 59182 invoked from network); 12 May 2005 20:43:07 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199) by minotaur.apache.org with SMTP; 12 May 2005 20:43:07 -0000 Received: (qmail 83511 invoked by uid 500); 12 May 2005 20:47:14 -0000 Delivered-To: apmail-ant-dev-archive@ant.apache.org Received: (qmail 83456 invoked by uid 500); 12 May 2005 20:47:14 -0000 Mailing-List: contact dev-help@ant.apache.org; run by ezmlm Precedence: bulk List-Unsubscribe: List-Help: List-Post: List-Id: "Ant Developers List" Reply-To: "Ant Developers List" Delivered-To: mailing list dev@ant.apache.org Received: (qmail 83439 invoked by uid 99); 12 May 2005 20:47:14 -0000 X-ASF-Spam-Status: No, hits=2.2 required=10.0 tests=FORGED_YAHOO_RCVD X-Spam-Check-By: apache.org Received-SPF: pass (hermes.apache.org: local policy) Received: from web30913.mail.mud.yahoo.com (HELO web30913.mail.mud.yahoo.com) (68.142.201.66) by apache.org (qpsmtpd/0.28) with SMTP; Thu, 12 May 2005 13:47:14 -0700 Received: (qmail 95911 invoked by uid 60001); 12 May 2005 20:43:02 -0000 Comment: DomainKeys? See http://antispam.yahoo.com/domainkeys DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com; b=X+lx00JAdGp5ft4E33Qd2ldMAsREdRvo9pcQ7x5p+VbKVQk8JhJh4zWbzU0zArd38Me2bDTw4H46hhkVD2qQ+9M34K/9VyeCgkah4L+N/xn6q6hO/OMr78QtPzbGgzc9feVH3JkdbsW6U8Gbh50KkmjHyYgVzSLe9AEdUPtPAVs= ; Message-ID: <20050512204302.95909.qmail@web30913.mail.mud.yahoo.com> Received: from [65.247.233.5] by web30913.mail.mud.yahoo.com via HTTP; Thu, 12 May 2005 13:43:01 PDT Date: Thu, 12 May 2005 13:43:01 -0700 (PDT) From: Matt Benson Subject: Re: [Bug 28444] - Import: Target Handling Bug To: Ant Developers List In-Reply-To: 6667 MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Virus-Checked: Checked X-Spam-Rating: minotaur.apache.org 1.6.2 0/1000/N --- Stefan Bodewig wrote: [SNIP] > Turning Matt's idea around: > > (1) Target "foo" is in project "bar". > (2a) There already is a target "foo" from the file > that imported > "bar", use the current code, we are ready, > "bar.foo" is there. > (2b) There is no other target "foo" yet. Create an > empty placeholder > target "bar.foo" that depends on "foo". > > If then later a target "foo" is found in the > importing buildfile, > replace the placeholder "bar.foo" with the > initial "foo" target. > > Wouldn't that work, stay backwards compatible and > hide "bar." whenever > possible? You confused me with the "later." Even though this could theoretically happen via 3rd-party API calls, we wouldn't be able to detect it, would we? Our local targets are known before we actually execute a top-level (target "") import, right? So what I take away from the above is that when there is only one "foo", the real work lives in "foo" while "bar.foo" depends on "foo" (my idea turned around). But say the importER explicitly depends on bar.foo . Isn't this still going to pollute the log in the opposite way my implementation would? :) i.e. [foo]: [bar.foo]: -Matt > > Stefan > > --------------------------------------------------------------------- > To unsubscribe, e-mail: > dev-unsubscribe@ant.apache.org > For additional commands, e-mail: > dev-help@ant.apache.org > > Discover Yahoo! Find restaurants, movies, travel and more fun for the weekend. Check it out! http://discover.yahoo.com/weekend.html --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscribe@ant.apache.org For additional commands, e-mail: dev-help@ant.apache.org