On 5/9/07, Steve Loughran <[EMAIL PROTECTED]> wrote:
Xavier Hanin wrote:
> On 5/8/07, Steve Loughran <[EMAIL PROTECTED]> wrote:
>> Xavier Hanin wrote:
>> > On 5/7/07, Steve Loughran <[EMAIL PROTECTED]> wrote:
>>
>> >> hooking in to a named ivy conf:
>> >>
>> >> <antlib uri="org.example.something" conf="example" />
>> > And wher is the version information? And how do we map this package
>> > name to an organization/module name couple? What do you think of
>> > providing all information:
>> > <antlib uri="org.example.something"
>> > org="org.example"
>> > module="example"
>> > rev="1.3"
>> > conf="example" />
>>
>> I'd expect all version info to be in ivy.xml; when I declare a
>> configuration in the <antlib> declaration, I say which ivy
configuration
>> I want, without any version info embedded in the build files
> And where is the ivy.xml?
>
alongside the build.xml, of course. I'm assuming that <ivy:resoolve> has
already kicked in.
So you have to call ivy:resolve manually if you use multiple antlibs (to
name the ivy.xml files). I'm not sure having to use a separate ivy.xml for
each antlib make much sense, since you will usually have only one dependency
in your ivy.xml. I think the inline mode (where you specify the dependency
when calling the task, with no ivy file) should at least be an option. If we
really want to put this information out of the antlib task, I think it
doesn't really that different from what is possible today:
<ivy:cachepath organisation="org.example" module="example"
revision="1.3"
inline="true" conf="example" pathid="
example.classpath"/>
<taskdef resource="org/example/something/antlib.xml"
uri="antlib:org.example.something" classpathref="
example.classpath"/>
Am I missing something?
Xavier
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
--
Xavier Hanin - Independent Java Consultant
Manage your dependencies with Ivy!
http://incubator.apache.org/ivy/
