Return-Path: Delivered-To: apmail-incubator-ivy-user-archive@locus.apache.org Received: (qmail 96630 invoked from network); 12 Dec 2007 09:41:07 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 12 Dec 2007 09:41:07 -0000 Received: (qmail 22277 invoked by uid 500); 12 Dec 2007 09:40:55 -0000 Delivered-To: apmail-incubator-ivy-user-archive@incubator.apache.org Received: (qmail 22249 invoked by uid 500); 12 Dec 2007 09:40:55 -0000 Mailing-List: contact ivy-user-help@incubator.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: ivy-user@incubator.apache.org Delivered-To: mailing list ivy-user@incubator.apache.org Received: (qmail 22240 invoked by uid 99); 12 Dec 2007 09:40:55 -0000 Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 12 Dec 2007 01:40:55 -0800 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 gerard.fernandes@lehman.com designates 192.147.56.151 as permitted sender) Received: from [192.147.56.151] (HELO extrelay6.lehman.com) (192.147.56.151) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 12 Dec 2007 09:40:34 +0000 Received: from nysmtplxmgmac08.lehman.com (nysmtplxmgmac08.lehman.com [10.12.86.117]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by extrelay6.lehman.com (Postfix) with ESMTP id 84D50253957 for ; Wed, 12 Dec 2007 04:40:36 -0500 (EST) Received: from localhost (localhost.localdomain [127.0.0.1]) by nysmtplxmgmac08.lehman.com (8.12.11/8.12.11) with SMTP id lBC9eaJK017727 for ; Wed, 12 Dec 2007 04:40:36 -0500 Received: from lopets1excb001.leh.lbcorp.lehman.com (lopets1excb001.leh.lbcorp.lehman.com [10.96.69.44]) by lonmailhost1.lehman.com (Postfix) with ESMTP id E5EE932FD9 for ; Wed, 12 Dec 2007 09:40:31 +0000 (GMT) Received: from lopets1exms002.leh.lbcorp.lehman.com ([10.69.23.22]) by lopets1excb001.leh.lbcorp.lehman.com with Microsoft SMTPSVC(6.0.3790.1830); Wed, 12 Dec 2007 09:40:31 +0000 Content-class: urn:content-classes:message MIME-Version: 1.0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable X-MimeOLE: Produced By Microsoft Exchange V6.5 Subject: RE: IvyDE source artifact not recognised Date: Wed, 12 Dec 2007 09:40:31 -0000 Message-ID: In-Reply-To: X-MS-Has-Attach: X-MS-TNEF-Correlator: Thread-Topic: IvyDE source artifact not recognised Thread-Index: Acg8MRBX8geIyAHMR6qW2lADacZwHgAcM5lAAABEwtA= References: <49c77ae40712110211t2527c749qbaaa8cf5dc101365@mail.gmail.com> <2912BA8E-CF4E-4745-8FC2-8A3066693F57@anyware-tech.com> From: "Fernandes, Gerard" To: X-OriginalArrivalTime: 12 Dec 2007 09:40:31.0847 (UTC) FILETIME=[0999CF70:01C83CA3] X-messagegate_id: 3D1F53521CCC X-Virus-Checked: Checked by ClamAV on apache.org =20 Note that the cglib 2.1_03 source artifact is named: cglib-src-2.1_03.jar -----Original Message----- From: Fernandes, Gerard=20 Sent: 12 December 2007 09:39 To: 'ivy-user=40incubator.apache.org' Subject: RE: IvyDE source artifact not recognised In my opinion, it is very important that the =22-src=22 part be acceptable = and recognised by IvyDE. If one has to workaround by: 1-=09changing the source artifact name=20 2-=09adding =22-src=22 in ivysettings One runs the risk of Ivy resolving source artifacts instead of binaries. E.g. Try having cglib 2.1_03 and commons-cli and configuring Ivy with the = cglib binary only and commons-cli with binary and source artifacts by = working around in the ivysettings. The cglib artifact attached is the = source artifact=21 Of course Eclipse compilation breaks. Try with the ivysettings as you've mentioned below and Ivy configuration: =09=09default=22/> =09=09default=22> =09=09=09 =09=09=09 =09=09 This kind of workaround also affects Ivy and breaks the ant build as = well=21 This means my CruiseControl build is no longer working because of = the workaround in ivysettings and the above configuration to accommodate = IvyDE for attaching sources in Eclipse. Gerard -----Original Message----- From: Nicolas Lalev=E9e =5Bmailto:nicolas.lalevee=40anyware-tech.com=5D Sent: 11 December 2007 20:06 To: ivy-user=40incubator.apache.org Subject: Re: IvyDE source artifact not recognised Le 11 d=E9c. 07 =E0 11:11, John Gill a =E9crit : > I believe that one of the limitations of ivyDE source linking is that=20 > the names must match. You can have a different type/ext like=20 > =22.src.jar=22 > but > that's it. The only way I have ever got it to work is with matching=20 > names. And I think that it is an error to have different names. Because having = different names means talking about different artifact. So the ivy.xml have to look like that : default=22> Then there is the problem with the real artifact name : commons-cli- = src-1.1.zip That can be fixed easily with a proper pattern : Nicolas > > > On Dec 11, 2007 6:16 PM, Fernandes, Gerard=20 > > > wrote: > >> >> IvyDE doesn't recognise source artifacts with a different name than=20 >> the binary artifact. >> >> E.g., If I have a JAR called commons-cli-1.1.jar and it's source=20 >> called commons-cli-src-1.1.zip, an Ivy configuration with the=20 >> following will resolve and the sources are downloaded (can be=20 >> confirmed by the Ivy report as well as checking the cache) but will=20 >> NOT attach sources in >> Eclipse: >> > cli=22 >> rev=3D=221.1=22 conf=3D=22COMPILE,RUNTIME,TEST->default=22> >> >> > ext=3D=22zip=22 conf=3D=22COMPILE=22 /> >> >> >> Ivy settings are: >> >> > = pattern=3D=22=24=7Bivy.conf.dir=7D/=5Borganisation=5D/=5Brevision=5D/=5Bart= ifact=5D. >> =5Bext=5D=22/> >> > = pattern=3D=22=24=7Bivy.conf.dir=7D/=5Borganisation=5D/=5Brevision=5D/=5Bart= ifact=5D- >> =5Brevision=5D >> .=5Bext=5D=22/> >> >> >> The only way to make this work is to change Ivy settings to: >> >> >> > = pattern=3D=22=24=7Bivy.conf.dir=7D/=5Borganisation=5D/=5Brevision=5D/=5Bart= ifact=5D. >> =5Bext=5D=22/> >> > = pattern=3D=22=24=7Bivy.conf.dir=7D/=5Borganisation=5D/=5Brevision=5D/=5Bart= ifact=5D-src. >> =5Bext=5D=22 >> /> >> > = pattern=3D=22=24=7Bivy.conf.dir=7D/=5Borganisation=5D/=5Brevision=5D/=5Bart= ifact=5D- >> =5Brevision=5D >> .=5Bext=5D=22/> >> > = pattern=3D=22=24=7Bivy.conf.dir=7D/=5Borganisation=5D/=5Brevision=5D/=5Bart= ifact=5D- >> =5Brevision=5D >> -src.=5Bext=5D=22/> >> >> >> And rename >> commons-cli-src-1.1.zip >> To >> commons-cli-1.1-src.zip >> >> And finally change the Ivy configuration to: >> > cli=22 >> rev=3D=221.1=22 conf=3D=22COMPILE,RUNTIME,TEST->default=22> >> >> > ext=3D=22zip=22 conf=3D=22COMPILE=22 /> >> >> >> >> Gerard >> - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - >> - - - >> - - - - - - - >> >> This message is intended only for the personal and confidential use=20 >> of the designated recipient(s) named above. If you are not the=20 >> intended recipient of this message you are hereby notified that any=20 >> review, dissemination, distribution or copying of this message is=20 >> strictly prohibited. This communication is for information purposes=20 >> only and should not be regarded as an offer to sell or as a=20 >> solicitation of an offer to buy any financial product, an official=20 >> confirmation of any transaction, or as an official statement of=20 >> Lehman Brothers. Email transmission cannot be guaranteed to be=20 >> secure or error-free. Therefore, we do not represent that this=20 >> information >> is complete or accurate and it should not be relied upon as such. =20 >> All >> information is subject to change without notice. >> >> >> >> > > > -- > Regards, > John Gill - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - = - - - - - - - This message is intended only for the personal and confidential use of the = designated recipient(s) named above. If you are not the intended = recipient of this message you are hereby notified that any review, = dissemination, distribution or copying of this message is strictly = prohibited. This communication is for information purposes only and = should not be regarded as an offer to sell or as a solicitation of an = offer to buy any financial product, an official confirmation of any = transaction, or as an official statement of Lehman Brothers. Email = transmission cannot be guaranteed to be secure or error-free. Therefore, = we do not represent that this information is complete or accurate and it = should not be relied upon as such. All information is subject to change = without notice.