gilles,
i found that if i explicitly call out "ivy.instance" in the id= attr for
the step 2 ivy:settings task, i do see:
resolve:
[ivy:resolve] :: loading settings :: file =
/home/jtb/src/portal/trunk/portal/buildutil/ivysettings.xml
which the correct one resolve file, which i did not before ... but then
subsequently, i see this:
[ivy:resolve] :: problems summary ::
[ivy:resolve] :::: ERRORS
[ivy:resolve] unknown resolver portal-maven2
portal-maven2 is a resolver defined in the step 1 ivysettings.xml file.
the build fails (expectedly in this case) but i still see that weird
error message. and obviously, i didn't expect to have to call out a
non-default ID ...
?
Jeffrey Blattman wrote:
> sorry gilles, i was looking at the configure task, which i now see is
> deprecated.
>
> 1. however, i am not getting the results i'm looking for ... what i
> want is this ... one module that has settings that define several
> external resolvers ... which "installs" them and builds local repo.
>
> 2. all other modules that use a different settings, that are define
> only a single resolver, that points to the locally built repo in
step 1.
>
> in step 1 i do ...
>
> <ivy:settings id="dependencies" file="[the many resolvers
> settings file]"/>
> then many
>
> <ivy:install .... settingsRef="dependencies" />
>
> that works fine ... but then in step 2 i do ...
>
> <ivy:settings file="[one resolve file]"/>
>
> which uses the default id i assume. then
>
> <ivy:retrieve/>
>
> the retrieve still finds the many resolves defined under the
> non-default it "dependencies".
>
> what am i missing?
> thanks. Gilles Scokart wrote:
>> I settings doc [1], you have the id field.
>> In all other tasks you have the settingsRef field. Look for example
>> at [2], the field is described.
>>
>> It seems that I have a first feedback : the doc should be more
>> clear. But how?
>>
>> [1] http://incubator.apache.org/ivy/doc/use/settings.html
>> [2] http://incubator.apache.org/ivy/doc/use/resolve.html
>>
>> Gilles
>>
>> 2007/6/21, Jeffrey Blattman <[EMAIL PROTECTED]>:
>>> 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 <[EMAIL PROTECTED]>:
>>> >> 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 <[EMAIL PROTECTED]>:
>>> >> >>
>>> >> >>
>>> >> >> 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?
>>> >> >
>>> >>
>>> >
>>>
>>
>>
>
