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 D8C0F7384 for ; Tue, 18 Oct 2011 22:01:31 +0000 (UTC) Received: (qmail 57673 invoked by uid 500); 18 Oct 2011 22:01:31 -0000 Delivered-To: apmail-ant-ivy-user-archive@ant.apache.org Received: (qmail 57581 invoked by uid 500); 18 Oct 2011 22:01:31 -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 57573 invoked by uid 99); 18 Oct 2011 22:01:31 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 18 Oct 2011 22:01:31 +0000 X-ASF-Spam-Status: No, hits=1.5 required=5.0 tests=FREEMAIL_FROM,HTML_MESSAGE,RCVD_IN_DNSWL_LOW,SPF_PASS,T_TO_NO_BRKTS_FREEMAIL X-Spam-Check-By: apache.org Received-SPF: pass (nike.apache.org: domain of mgitman@gmail.com designates 209.85.220.173 as permitted sender) Received: from [209.85.220.173] (HELO mail-vx0-f173.google.com) (209.85.220.173) by apache.org (qpsmtpd/0.29) with ESMTP; Tue, 18 Oct 2011 22:01:24 +0000 Received: by vcbfl17 with SMTP id fl17so1117148vcb.4 for ; Tue, 18 Oct 2011 15:01:04 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=gamma; h=mime-version:in-reply-to:references:date:message-id:subject:from:to :content-type; bh=VF3M7ZYsJwAcreF7b48Cj5V2at0DPfIkhZF1YUBrn6Q=; b=WMiBuWenjtt3+wO2EcEBo7hKQcO4JpQ3lWnX6g6maD9g5wby7jYuMVJFuymKGJL92f 84dQEHPZfWyJsvyKQp7opRuPIcemSpEtGE94UQRVbSojVm2auskBMbgcjBl6ityuqDy8 7EGTY1B1YgTRmNPx8GGAEmY45tRiCOOnQnSsA= MIME-Version: 1.0 Received: by 10.52.36.41 with SMTP id n9mr4451698vdj.41.1318975264001; Tue, 18 Oct 2011 15:01:04 -0700 (PDT) Received: by 10.220.182.136 with HTTP; Tue, 18 Oct 2011 15:01:03 -0700 (PDT) In-Reply-To: <9B13BD18-C7BA-44EA-BCEA-868E03B3272E@hibnet.org> References: <9B13BD18-C7BA-44EA-BCEA-868E03B3272E@hibnet.org> Date: Tue, 18 Oct 2011 15:01:03 -0700 Message-ID: Subject: Re: IvyDE & source variations (was: workaround to consume legacy Ivy modules) From: Mitch Gitman To: ivy-user@ant.apache.org Content-Type: multipart/alternative; boundary=20cf3079ba76140ee604af99dcae X-Virus-Checked: Checked by ClamAV on apache.org --20cf3079ba76140ee604af99dcae Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: quoted-printable Great. Thanks, Nicolas. Another IvyDE question comes up. There are some Ivy modules which I do control, and those ones I'm trying to make more conventional, publishing a *-source.jar artifact. Publish works fine. And I even make IvyDE resolve to a special IvyDE-specific cache. And under that cache, I see the jars and sources directories getting populated correctly. But then when I go in Eclipse to click on some depended-upon source that I control, I see the dreaded "Source not found" error with this interesting tidbit: "The JAR of this class file belongs to container 'ivy.xml[*]' which dose no= t allow modifications to source attachments on its entries." Anyone recall what that is a sign of? 2011/10/18 Nicolas Lalev=C3=A9e > > Le 18 oct. 2011 =C3=A0 23:00, Mitch Gitman a =C3=A9crit : > > > Archie, thanks for the alternate approach. In case I still want to > consider > > the original approach--if anyone else knows about the particular place = in > > the code that I want to override, I'd love to hear. > > Correction. I believe I meant ${ivy.module.name}. > > > > Actually, this raises another question. How would I configure IvyDE to > > recognize foo.src.zip as the source for foo.jar? > > > > The "Sources suffixes" configuration has default values like: > > -source,-sources,-src > > > > I could change this value to the following: > > .src > > > > Still, the presumption seems to be that the extension is always .jar. I= t > > doesn't appear to accommodate .zip. > > IvyDE doesn't care about the extension. It only compares the artifact nam= es > and artifacts types declared in the ivy.xml to find out which is source o= f > the other. > > Nicolas > > > On Tue, Oct 18, 2011 at 11:00 AM, Archie Cobbs > wrote: > > > >> Just a thought... maybe instead you could write a resolver that contai= ns > a > >> nested, normal resolver, and applies a configured XLST stylesheet to a= ll > of > >> the ivy.xml files it downloads. Then what you want to do would be an > easy > >> specific case. > >> > >> -Archie > >> > >> On Tue, Oct 18, 2011 at 12:27 PM, Mitch Gitman > wrote: > >> > >>> It looks like I'm going to have to write a custom Ivy resolver. I wan= t > to > >>> consume modules that contain both a *.jar file and a *.src.zip file b= ut > >>> where the ivy.xml doesn't specify any publications. Unfortunately, > these > >>> modules are already published to a shared location and I can't just g= o > >> and > >>> blow them away. I understand that Ivy's default behavior is to treat > the > >>> lack of a publications element as if it were the following: > >>> > >>> > >>> > >>> > >>> I forget if the property is module.name or something else. For the > >>> artifact > >>> element, the default type and ext of "jar" kick in. > >>> > >>> So I want to get the resolver to interpret this absence of publicatio= ns > >>> instead as: > >>> > >>> > >>> > >>> > >>> > >>> Would anyone happen to know the bit of resolver code that defaults th= e > >>> absence of publications so that I might override it? > >>> > >> > >> > >> > >> -- > >> Archie L. Cobbs > >> > > --20cf3079ba76140ee604af99dcae--