Return-Path: 
 <ivy-user-return-1726-apmail-incubator-ivy-user-archive=incubator.apache.org@incubator.apache.org>
Delivered-To: apmail-incubator-ivy-user-archive@locus.apache.org
Received: (qmail 59514 invoked from network); 4 Oct 2007 01:22:15 -0000
Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2)
  by minotaur.apache.org with SMTP; 4 Oct 2007 01:22:15 -0000
Received: (qmail 260 invoked by uid 500); 4 Oct 2007 01:22:04 -0000
Delivered-To: apmail-incubator-ivy-user-archive@incubator.apache.org
Received: (qmail 234 invoked by uid 500); 4 Oct 2007 01:22:04 -0000
Mailing-List: contact ivy-user-help@incubator.apache.org; run by ezmlm
Precedence: bulk
List-Help: <mailto:ivy-user-help@incubator.apache.org>
List-Unsubscribe: <mailto:ivy-user-unsubscribe@incubator.apache.org>
List-Post: <mailto:ivy-user@incubator.apache.org>
List-Id: <ivy-user.incubator.apache.org>
Reply-To: ivy-user@incubator.apache.org
Delivered-To: mailing list ivy-user@incubator.apache.org
Received: (qmail 225 invoked by uid 99); 4 Oct 2007 01:22:04 -0000
Received: from athena.apache.org (HELO athena.apache.org) (140.211.11.136)
    by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 03 Oct 2007 18:22:04 -0700
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 (athena.apache.org: domain of llignhoj@gmail.com designates
 66.249.92.171 as permitted sender)
Received: from [66.249.92.171] (HELO ug-out-1314.google.com) (66.249.92.171)
    by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 04 Oct 2007 01:22:03 +0000
Received: by ug-out-1314.google.com with SMTP id 30so329742ugs
        for <ivy-user@incubator.apache.org>;
 Wed, 03 Oct 2007 18:21:41 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
        d=gmail.com; s=beta;
        h=domainkey-signature:received:received:message-id:date:from:to:subject:in-reply-to:mime-version:content-type:references;
        bh=MYWQNJpKTaEzSSfrNzjYYk6F3UAkzdkPUTDljCzB6OQ=;
        b=LqHbXtwI2dWto452Aw3L/3WS24VpFhHQDCPx61WmFCHWf7/g7ZGK1DQb4b1HSg7GWzOlecqh+ocREItQg9Ftb+WBu9rd5kRXVfOYBmyMHETgSiJfxO4Jis/VBgtx8qggPL2E6mR6W1ZviqRDDldIJu+jjDpz0+lD5MaDwI7/aQ4=
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=gykght8ZnXs4HINZv1QRlC24kvuOWDdZDIJbQ5iWVZU5CJgBR/Lh1x7WIHHJ0iIeNFAoxAdi+iKLn5ZqXJMnSvGTkAsWh0PJSrWz1qUZesG6q/PQSlHpjyLJ1YddxYMcugKIpFFkvAJvCmb2i3aQ9B5RV6SY3xwVdwjn7L6A2Ic=
Received: by 10.142.50.15 with SMTP id x15mr146863wfx.1191460899604;
        Wed, 03 Oct 2007 18:21:39 -0700 (PDT)
Received: by 10.141.28.18 with HTTP; Wed, 3 Oct 2007 18:21:39 -0700 (PDT)
Message-ID: <49c77ae40710031821r37ff3c00lf598eaf8d8215d88@mail.gmail.com>
Date: Thu, 4 Oct 2007 09:21:39 +0800
From: "John Gill" <llignhoj@gmail.com>
To: ivy-user@incubator.apache.org
Subject: Re: resolving java source files using IvyDE
In-Reply-To: <17753330.1191449167843.JavaMail.ngmail@webmail12>
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary="----=_Part_12515_22895042.1191460899604"
References: <17753330.1191449167843.JavaMail.ngmail@webmail12>
X-Virus-Checked: Checked by ClamAV on apache.org

------=_Part_12515_22895042.1191460899604
Content-Type: text/plain; charset=WINDOWS-1252
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline

It is possible to "attach" the source jars to the class jars in ivyDE. The
trick is to ensure that the name of the source jar is the same as the class
jar.

If your class jar is called "myjar.jar" then name your source jar "
myjar.src.jar" and then define both the class and source jar in your
ivy.xmlfile like so:

<artifact name=3D"myjar"           type=3D"jar" />
<artifact name=3D"myjar"           type=3D"src" ext=3D"src.jar" />

Then make sure that ivyDE is configured to accept the type "src" as the
source types.

The same trick works for javadoc as well (although I don't tend to find thi=
s
as useful, unless perhaps you don't have the source code jar).
<artifact name=3D"myjar"           type=3D"javadoc" ext=3D"zip" />

If the source jars and javadoc jars are from a third party and not names
appropriately, then what I do is rename them and put them in your own ivy
repository.

On 10/4/07, tfulde@arcor.de <tfulde@arcor.de> wrote:
>
> Hi,
>
> I am using IvyDE since two days now. I am working with RAD 7 in a large
> scale project.
> IvyDE seems to help me solving my classpath problems.
>
> I have found out how to declare dependencies for library jars in my
> workspace using a simple file resolver:
>
>         <resolvers>
>                 <filesystem name=3D"internal">
>                         <ivy pattern=3D"C:/workspace/[module]/ivy.xml" />
>                         <artifact
> pattern=3D"C:/workspace/libDir/[module].jar" />
>                 </filesystem>
>         </resolvers>
>
>
> I have still some trouble to put simple java projects including sources o=
f
> my workspace into the build path of RAD.
> I assume that this possible using  IvyDE.
> Does anybody have an idea how to solve this problem using IvyDE?
>
> Tanja
>
> Viel oder wenig? Schnell oder langsam? Unbegrenzt surfen + telefonieren
> ohne Zeit- und Volumenbegrenzung? DAS TOP ANGEBOT F=DCR ALLE NEUEINSTEIGE=
R
> Jetzt bei Arcor: g=FCnstig und schnell mit DSL - das All-Inclusive-Paket
> f=FCr clevere Doppel-Sparer, nur  34,95 =80  inkl. DSL- und ISDN-Grundgeb=
=FChr!
> http://www.arcor.de/rd/emf-dsl-2
>



--=20
Regards,
John Gill

------=_Part_12515_22895042.1191460899604--