Return-Path: Delivered-To: apmail-incubator-ivy-user-archive@locus.apache.org Received: (qmail 45376 invoked from network); 13 Jan 2007 08:15:13 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 13 Jan 2007 08:15:13 -0000 Received: (qmail 21739 invoked by uid 500); 13 Jan 2007 08:15:20 -0000 Delivered-To: apmail-incubator-ivy-user-archive@incubator.apache.org Received: (qmail 21714 invoked by uid 500); 13 Jan 2007 08:15:20 -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 21704 invoked by uid 99); 13 Jan 2007 08:15:19 -0000 Received: from herse.apache.org (HELO herse.apache.org) (140.211.11.133) by apache.org (qpsmtpd/0.29) with ESMTP; Sat, 13 Jan 2007 00:15:19 -0800 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 (herse.apache.org: domain of xavier.hanin@gmail.com designates 66.249.92.174 as permitted sender) Received: from [66.249.92.174] (HELO ug-out-1314.google.com) (66.249.92.174) by apache.org (qpsmtpd/0.29) with ESMTP; Sat, 13 Jan 2007 00:15:10 -0800 Received: by ug-out-1314.google.com with SMTP id y2so1128086uge for ; Sat, 13 Jan 2007 00:14:49 -0800 (PST) DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=received:message-id:date:from:to:subject:in-reply-to:mime-version:content-type:references; b=FSG+VGkwrp566YkUD/na0EKVz7jL6T7BdBQ9pclg0XRFtld/qqjabjgc8lYLfNq8lrHqpppfhHTpkizJhjGC0UivxKMnfvNOk85rtaSHpAPx8pHPrT+sroYEBTOoAFloU7tQ7o42MxP/T+HCHDH6UYzDURgN4oLKp1BZN6tJfJk= Received: by 10.66.232.10 with SMTP id e10mr2136974ugh.1168676088471; Sat, 13 Jan 2007 00:14:48 -0800 (PST) Received: by 10.67.100.5 with HTTP; Sat, 13 Jan 2007 00:14:47 -0800 (PST) Message-ID: <635a05060701130014v4b5896a6v47dd31efdbadcb2e@mail.gmail.com> Date: Sat, 13 Jan 2007 09:14:47 +0100 From: "Xavier Hanin" To: ivy-user@incubator.apache.org, "Dmitriy Korobskiy" Subject: Re: Re[4]: Does the IvyDE classpath container have support for source attachments? In-Reply-To: <1839361750.20070112164928@gmail.com> MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_Part_44237_27122861.1168676087452" References: <56b162b60612070231g12bf5181m822800bb2f3dab92@mail.gmail.com> <635a05060612070259p347e0f09h280056e818f87b2a@mail.gmail.com> <1766028300.20061207112040@gmail.com> <635a05060612070854h2fd5c6dasb91143e8bd824929@mail.gmail.com> <1839361750.20070112164928@gmail.com> X-Virus-Checked: Checked by ClamAV on apache.org ------=_Part_44237_27122861.1168676087452 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline On 1/12/07, Dmitriy Korobskiy wrote: > > Xavier, > > > I've tried source ZIP attachment with IvyDE and it worked, but JavaDoc > attachment did not. > I'm configuring JavaDoc in exactly the same way I'm configuring source > attachments. > > The resolve seemed to have worked fine, but in the end the JavaDoc ZIP is > not attached. > > > Do you know whether JavaDoc attachements are supported by IvyDE 1.2.0 or > not? > To be honest I don't know. And I'm already so busy with plenty of stuff and Ivy migration that I don't have time to test and debug for the moment. But I'm not surprised it doesn't work, Peter (who implemented the feature) told about a problem with javadoc. Sorry that I can't say more for the moment... Xavier Here is the example: > > > \apache\commons-collections\commons- > collections-3.2\commons-collections-3.2.jar > > \apache\commons-collections\commons- > collections-3.2\commons-collections-3.2.zip > > \apache\commons-collections\commons- > collections-3.2\commons-collections-3.2.javadoc.zip > > \apache\commons-collections\commons- > collections-3.2\commons-collections-3.2.src.zip > > > > > http://ivyrep.jayasoft.org/ivy-doc.xsl"?> > > > > status="release"/> > > > > > > > > > > > > > > conf="ide"/> > > conf="ide"/> > > > > > > > Dmitriy <1-127-441 @ICQ, DKroot @Skype, DKroot1 @AIM, > dkroot1_at_gmail_dot_com @Google Talk> > > > ===8<==============Original message =============== > > From: Xavier Hanin > > To: Dmitriy Korobskiy > > Subject: Does the IvyDE classpath container have support for source > attachments? > > Sent: Thursday, December 7, 2006 > > > On 12/7/06, Dmitriy Korobskiy wrote: > > Xavier, > > > Thanks for your explanation. It makes sense. I was longing for some kind > of > > example/documentation for this exciting new feature of IvyDE! > > > Yes, but this is a user contributed feature, and I hope more > example/documentation will be user contributed too :-) > > > > I understand now how it works if you have ZIPs of JavaDocs and/or source. > > > Note that according to Peter who developed the feature there is still > problems with javadoc... but if you have sources attached, you have inline > javadoc with eclipse. > > > > I have another related question - if a distrubution has expanded > directories in > > repository - say, javadoc/ and src/ - is it possible to attach those using > IvyDE > > and url attribute or something like that? > > > No, not right now, but it's maybe not too difficult to develop. Have a > look at the code IvyClasspathContainer code, and you'll see how Peter has > implemented the feature. Then you should be able to see if you can tweak it > to your needs. > > > Xavier > > > > >> > > >> Hi, > > >> > > >> As far as I can see from http://jira.jayasoft.org/browse/IVYDE-12, the > > >> IvyDE supports source and javadoc attachments. However, I cannot find > > >> any examples using this feature. As far as I can read from the > > >> IVYDE-12 issue, I should extend the ivys in my repository so they > > >> include source and javadoc artifacts. Could somebody please give a > > >> short example of the use of this feature or point me to relevant > > >> documentation? > > > > XH> There is no documentation for the moment, here are some basic > explanations > > XH> of how it works for the moment: > > XH> When it find a jar artifact to add in the container, it looks for > another > > XH> artifact with the same name and with a "source" type, and attach it as > > XH> source if it finds one. The type (source) can be configured. > > XH> So if you want to have source attached you should have an ivy file > like this > > XH> one for your dependency: > > XH> > > XH> > > XH> > > XH> > > XH> > > XH> > > XH> > > XH> > > XH> conf="sources" > > />> > > XH> > > XH> > > XH> Then if you depend on it like this: > > XH> > conf="default->>default;dependencies-sources->sources" /> > > > XH> And if you resolve both the default and the dependencies-sources > > XH> configurations in IvyDE, you should get the myartifact.jar in the > container > > XH> with sources from myartifact.zip attached. > > > XH> Xavier > > > > > XH> Best regards, > > >> Jacob Grydholt Jensen > > >> > > > Dmitriy <1-127-441 @ICQ, DKroot @Skype, DKroot1 @AIM, > dkroot1_at_gmail_dot_com @Google Talk> > > > ===8<===========End of original message =========== > ------=_Part_44237_27122861.1168676087452--