Mailing-List: contact ivy-user-help@ant.apache.org; run by ezmlm
Precedence: bulk
Reply-To: ivy-user@ant.apache.org
Received-SPF: softfail (nike.apache.org: transitioning domain of
 nicolas.lalevee@hibnet.org does not designate 216.86.168.182 as permitted
 sender)
Content-Type: text/plain; charset=iso-8859-1; format=flowed; delsp=yes
Mime-Version: 1.0 (Apple Message framework v1076)
Subject: Re: sources as conf or type
From: =?iso-8859-1?Q?Nicolas_Lalev=E9e?= <nicolas.lalevee@hibnet.org>
In-Reply-To: <26124538.post@talk.nabble.com>
Date: Sat, 31 Oct 2009 20:13:30 +0100
Content-Transfer-Encoding: quoted-printable
Message-Id: <996E521C-5BF4-4B95-A0E7-5F373DE8C1F6@hibnet.org>
References: <26028446.post@talk.nabble.com>
 <7916a6a60910281329u71f7c238u65e519cbbb6fcb71@mail.gmail.com>
 <20091028211532.GB96293@nmhq.net>
 <7916a6a60910281952r28007924i487e839a842c5e5b@mail.gmail.com>
 <20091029161119.GA56244@nmhq.net> <26123692.post@talk.nabble.com>
 <20091030021309.GC56123@nmhq.net> <26124538.post@talk.nabble.com>
To: ivy-user@ant.apache.org


Le 30 oct. 2009 =E0 04:43, Stephen Haberman a =E9crit :

>
>
> Niklas Matthies-2 wrote:
>>
>> If types were hierarchical nodes in a category graph, and a mapping
>> mechanism would be provided like for confs, then I would agree with
>> you. Types would be almost like a second type of confs then. Which I
>> think would be very useful.
>>
>
> Hm...true, types are flat and non-mappable.
>
> For me living mostly in a java/ibiblio world, the "all binaries" =20
> super type
> isn't a problem--since I haven't used ivy for non-java projects, I =20
> don't
> know how often the "any binary type even if I don't know about it =20
> ahead of
> time" thing would come up. Though I understand the gist of it.
>
>
> Niklas Matthies-2 wrote:
>>
>>> Where I'll get the jetty source but not the jetty-util source
>>> because they forgot the "sources->sources(*)" mapping.
>>
>> Luckily there's dual resolvers. ;)
>> Yes, it's not ideal, but at least you *can* do something about it =20
>> that
>> way.
>>
>
> Hehe, okay, technically yes, but yuck. The pom->ivy translation =20
> works well
> enough for me that I'd prefer to not maintain other projects' ivy =20
> files by
> hand just because of the non-transitive source.
>
> Which I talked myself into it being a bug:
>
> https://issues.apache.org/jira/browse/IVY-1137

Sorry I didn't have time to reply to this interesting discussion. =20
Actually I already have that discussion around the same issue in pom / =20=

ivy mapping there:
=
http://old.nabble.com/pom2ivy-and-transitive-source-retrieving-to25112985.=
html#a25112985

I "just" (shame on me) forgot to actually implement the solution we =20
agreed on. I'll do soon.

Nicolas