From ivy-user-return-8429-apmail-ant-ivy-user-archive=ant.apache.org@ant.apache.org Fri Jun 22 21:20:34 2012 Return-Path: X-Original-To: apmail-ant-ivy-user-archive@www.apache.org Delivered-To: apmail-ant-ivy-user-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id 12C809E71 for ; Fri, 22 Jun 2012 21:20:34 +0000 (UTC) Received: (qmail 19248 invoked by uid 500); 22 Jun 2012 21:20:33 -0000 Delivered-To: apmail-ant-ivy-user-archive@ant.apache.org Received: (qmail 19214 invoked by uid 500); 22 Jun 2012 21:20:33 -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 19205 invoked by uid 99); 22 Jun 2012 21:20:33 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Fri, 22 Jun 2012 21:20:33 +0000 X-ASF-Spam-Status: No, hits=4.7 required=5.0 tests=FREEMAIL_FORGED_REPLYTO,FSL_FREEMAIL_1,FSL_FREEMAIL_2,HTML_MESSAGE,RCVD_IN_DNSWL_NONE,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: local policy) Received: from [98.139.212.185] (HELO nm26.bullet.mail.bf1.yahoo.com) (98.139.212.185) by apache.org (qpsmtpd/0.29) with SMTP; Fri, 22 Jun 2012 21:20:22 +0000 Received: from [98.139.212.144] by nm26.bullet.mail.bf1.yahoo.com with NNFMP; 22 Jun 2012 21:20:01 -0000 Received: from [98.139.212.209] by tm1.bullet.mail.bf1.yahoo.com with NNFMP; 22 Jun 2012 21:20:01 -0000 Received: from [127.0.0.1] by omp1018.mail.bf1.yahoo.com with NNFMP; 22 Jun 2012 21:20:01 -0000 X-Yahoo-Newman-Property: ymail-3 X-Yahoo-Newman-Id: 20402.27409.bm@omp1018.mail.bf1.yahoo.com Received: (qmail 47855 invoked by uid 60001); 22 Jun 2012 21:20:00 -0000 DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=yahoo.com; s=s1024; t=1340400000; bh=2C+6bWIWke7gIdlEnB8pUS5ccg0pfe57Z2KHBwCUiUw=; h=X-YMail-OSG:Received:X-Mailer:References:Message-ID:Date:From:Reply-To:Subject:To:In-Reply-To:MIME-Version:Content-Type; b=iEdq2AGLY6bBAawk0EdGVIl4lMMcQo/waqo0TD4ptGdGfcj0GL2J9FyJIBkbHFTv4H5JD43HM8sCopmoXZE2lFkZ8+/vLzjZzuDqhk32DcQStg+lGWJt+WWFqSoVrOiB9sVbP+jt+SfUzJRsIiiJ2GhQq/Ddo66dbn+fk0mDZOw= DomainKey-Signature:a=rsa-sha1; q=dns; c=nofws; s=s1024; d=yahoo.com; h=X-YMail-OSG:Received:X-Mailer:References:Message-ID:Date:From:Reply-To:Subject:To:In-Reply-To:MIME-Version:Content-Type; b=1PVHrFn5U7QZvpZFMelPfTco0nvV3PJ0skaFlZmWSsIyfMvEOdgnYCssSoDuMb7OrP09CXHDC8xM1mzgf0KxfPwg9jZ84x0kk3d2QincVY/XpLHHUhh64RiVmAtGIw+KOVD1LyM/ofQdIVoh8y/6Q0Bseh42VCnaBScQwRJly4o=; X-YMail-OSG: tv7JSh4VM1l0yl3XFYenLouHBLuYi_U5WHn2.hsOg8EpSH5 pH3Z3LmASAAy9EvqocwSZXzCVK02.9kCRnHrFfZeA16s0Jn_98n8cIcemRxP pvzfoI.kSHTd.K9k9KoFivC7jiYIkYPV0FZ_EOk7UAGYtCHB4Rd2Qi_oICLb H2Xub3vyKfuU4uGvmNmkWnP2m.elsf23X2PkAT8n0MD8KfdAh0VbBkdBRPp. Z_xHwS4_BQx7cTnm15DcKvFIbVMOx7KaTDsA3X57hQaTkaqVLj3UMUm.0NYm k.tbwZTVNyj7DfkaJqq6LwEsK9sGfElGA22Yatusm8QL2h6Zt4VhMZdLAfpT sweL1PMmt7q51EW6qqx_M_g2BMNxhnIVcvqgfo6.qhtzjDY9fYQbx8lOHxd6 1noy2RHQCYn3keVsUI3NjLFfAVALYjDF9gB_n3sKmeHqrgiVhLjcSYFmQZxu 7yLD2H04ECJXxpzkFQ_N2yxAHqsNLOaMPpPn0p7YFSOfmZkFOR86H Received: from [91.177.51.26] by web162902.mail.bf1.yahoo.com via HTTP; Fri, 22 Jun 2012 14:20:00 PDT X-Mailer: YahooMailWebService/0.8.118.349524 References: Message-ID: <1340400000.39043.YahooMailNeo@web162902.mail.bf1.yahoo.com> Date: Fri, 22 Jun 2012 14:20:00 -0700 (PDT) From: Maarten Coene Reply-To: Maarten Coene Subject: Re: extends & buildlist on 2.3.0-rc1 ... it gets worse To: "ivy-user@ant.apache.org" In-Reply-To: MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="1114306876-57969742-1340400000=:39043" --1114306876-57969742-1340400000=:39043 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Hi Mitch,=0A=0Aplease open a JIRA ticket for this.=0A=0AThere is another bl= ocking issue related to the extends feature (IVY-1347) that must be fixed b= efore the 2.3.0 final release.=0AThis is exactly why we create RC versions = and ask people if they could test it.=0A=0AMaarten=0A=0A=0A=0A_____________= ___________________=0A From: Mitch Gitman =0ATo: ivy-use= r@ant.apache.org =0ASent: Friday, June 22, 2012 7:21 PM=0ASubject: Re: exte= nds & buildlist on 2.3.0-rc1 ... it gets worse=0A =0AOK, I stripped away al= l use of the extends feature, and sure enough,=0Abuildlist produced a norma= l, expected, non-randomized project build order.=0AThis indicates that some= thing that had been working in Ivy 2.2.0 is no=0Alonger working in Ivy 2.3.= 0-rc1.=0A=0AConsidering that:=0AA. The buildlist task is a prerequisite for= being productive with Ivy.*=0AB. The extends feature is a prerequisite for= being productive with Ivy.*=0AThe apparent fact that these two features ar= e now mutually exclusive with=0AIvy 2.3.0-rc1 (where they weren't with Ivy = 2.2.0) represents a serious bug.=0A=0AI think my next step is to forward th= is thread to the ant-dev list and ask=0Ahow to proceed.=0A=0A* For those wh= o wish to say, "Mitch, we've been able to get by just fine=0Awithout (build= list|extends)," I'm perfectly happy to have that discussion,=0Abut my prima= ry concern now is facilitating a fix.=0A=0AOn Thu, Jun 21, 2012 at 10:12 PM= , Mitch Gitman wrote:=0A=0A> One other data point. As l= ong as my undesired simplification wasn't=0A> helping things, I went back t= o both a bootstrap-parent and a master-parent.=0A> I also tried setting hal= tOnError=3D"false" on ivy:buildlist. With that, the=0A> task successfully g= ot through everything. However, it continued to create a=0A> seriously tras= hed build order.=0A>=0A> Just as an experiment, I might try converting all = the ivy.xml files to not=0A> use the extends feature and then see what happ= ens when running buildlist.=0A> My hypothesis is, this will work. Not that = this is a desired state of=0A> affairs, but at least it isolates the proble= m to the interaction between=0A> buildlist and extends.=0A>=0A>=0A> On Thu,= Jun 21, 2012 at 9:23 PM, Mitch Gitman wrote:=0A>=0A>> = Over a week ago, I'd sent out a message to this list, "buildlist task=0A>> = chokes on absolute path to parent Ivy module." I'd found that the extends= =0A>> feature worked fine with an absolute path to the parent ivy.xml if I = was=0A>> building any single Ivy module, but the buildlist task would fail = to find=0A>> the absolute path.=0A>>=0A>>=0A>>=0A>> I'd noted that I'd been= using Ivy 2.2.0. Now that I've upgraded to Ivy=0A>> 2.3.0-rc1, my problems= have only gotten worse. The first problem I=0A>> encountered had nothing t= o do with absolute paths to parents. I'm still=0A>> using relative paths to= parents. Instead, it arose from my using two=0A>> different parent Ivy mod= ules: bootstrap-parent and master-parent. Some=0A>> projects extended the f= ormer; others the latter. For example:=0A>>=C2=A0 =0A>>=0A>>=C2=A0 =C2=A0 > revision=3D"${= version}"=0A>>=0A>>=C2=A0 =C2=A0 =C2=A0 =C2=A0 location=3D"../bootstrap-pa= rent/ivy.xml" />=0A>>=0A>>=C2=A0 =0A>>=0A>>=0A>>=0A>> But then when= I pointed the ivy:buildlist Ant task at a project stack=0A>> that included= a mix of both parents and their children, I saw this error:=0A>>=0A>> impo= ssible to parse ivy file for =E2=80=A6/foo-client/homeowner/build.xml:=0A>>= ivyfile=3D.../foo-client/homeowner/ivy.xml=0A>> exception=3Djava.text.Pars= eException: Problem occurred while parsing ivy=0A>> file: inconsistent modu= le descriptor file found in=0A>> 'file:/.../master-parent/ivy.xml': bad mod= ule name:=0A>> expected=3D'bootstrap-parent' found=3D'master-parent';=C2=A0= in=0A>> file:/.../foo-client/homeowner/ivy.xml=0A>>=0A>>=0A>>=0A>> What's = happening is, the homeowner module extends bootstrap-parent, but=0A>> someh= ow the relative path to master-parent/ivy.xml is supplanting the=0A>> relat= ive path to bootstrap-parent/ivy.xml. It appears buildlist doesn't=0A>> kno= w how to deal with more than one parent, even though there's no=0A>> intera= ction between the two parents.=0A>>=0A>>=0A>>=0A>> After this, even though = I didn't really want to, I thought, "Why not make=0A>> things simple for bu= ildlist and use just one parent, master-parent?"=0A>>=0A>>=0A>>=0A>> Here's= where things really got wild. With Ivy 2.2.0, buildlist worked=0A>> just f= ine, provided I gave it relative paths to the different parents. Now,=0A>> = even with a relative path and even with a single parent, buildlist on=0A>> = 2.3.0-rc1 goes nuts. I go so far as to introduce a buildlist Ivy conf to=0A= >> force project A to sort before project B. How does buildlist on 2.3.0-rc= 1=0A>> interpret this? It puts B before A. (And no, I can guarantee I have = no=0A>> circular dependencies.)=0A>>=0A>>=0A>>=0A>> Can someone say, are th= ere any integration tests that test the=0A>> interaction between buildlist = and extends?=0A>>=0A>>=0A>>=0A>> And how should I proceed regarding these p= roblems? Should I file a bug or=0A>> bugs or JIRA? Does anyone know of any = existing bugs on JIRA?=0A>>=0A>=0A> --1114306876-57969742-1340400000=:39043--