ant-ivy-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Jeffrey Blattman <jeffrey.blatt...@gmail.com>
Subject Re: can i call ivy:configure multiple times with different configuration files(which in turn refers different ivy.xmls)?
Date Thu, 21 Jun 2007 20:30:04 GMT
sorry gilles, can you point me to the pages that explain the feature? i 
looked under ivy:settings and :configure  where i expected and didn't 
see anything about resolveId there.

Gilles Scokart wrote:
> It seems that the doc is already published on the website.  But the
> code is only in the trunk in subversion.
>
> What you have to do is to declare your different settings a ant
> datatype, then you can fill the settingsRef attribute of every ivy
> task.
>
> Note that the ivy task will take by default the settings with the id
> 'ivy.instance'.  So if you don't want to put a settingRef in all your
> ivy task, you can set this id for the settings that ivy should use by
> default.
>
> Please let me know if it works like you expect, if it is easy to use
> or if there are are any problems.  I would be pleased to receive a
> feedback on this new feature.
>
> Gilles
>
> 2007/6/20, Jeffrey Blattman <jeffrey.blattman@gmail.com>:
>> hi gilles,
>>
>> is there documentation on how to use this feature? examples?
>>
>> thanks.
>>
>> Gilles Scokart wrote:
>> > This should be fixed in 2.0-alpha2. Ivy will allow to use multiple
>> > configuration (named settings in 2.0). See [1].  To test it now, you
>> > will have to make your own build of ivy (which is not very difficult).
>> >
>> > [1] https://issues.apache.org/jira/browse/IVY-366
>> >
>> >
>> > Gilles
>> >
>> >
>> > 2007/6/20, sujeewanie weerakoon <sujeewanie@yahoo.com>:
>> >>
>> >>
>> >>  I have a modular build structure based on Ant. each
>> >>  module having a separate build script. I want to
>> >>  have
>> >>  the ivy realted files also module wise.
>> >>  With ivy 1.0 this was possible. But when i upgraded
>> >>  to
>> >>  ivy 1.4 only the first configuration file seems to
>> >>  be
>> >>  reffered by all the modules.
>> >> Inorder to publish I say
>> >> <ivy:publish
>> >> artifactspattern="${dist.dir}\[artifact].[ext]"
>> >>             resolver="chain-resolver"
>> >>             pubrevision="${revision}"
>> >>             status="release"
>> >>          />
>> >>
>> >>  The [artifact] gets evaluated to module name as
>> >> defined in the first loaded ivy.xml
>> >>
>> >> Is there a way to call ivy:configure multiple times
>> >>  with different configuration files?
>> >
>>
>

Mime
View raw message