I think it is? By default one of the resolvers pulls from
repo1.maven.org -- look at ivy-settings.xml:
<include url="${ivy.default.settings.dir}/ivysettings-public.xml"/>
<include url="${ivy.default.settings.dir}/ivysettings-shared.xml"/>
<include url="${ivy.default.settings.dir}/ivysettings-local.xml"/>
<include url="${ivy.default.settings.dir}/ivysettings-main-chain.xml"/>
the main chain includes shared repos and shared is:
<ibiblio name="public" m2compatible="true"/>
And ibiblio is by default pulling from maven repos:
http://ant.apache.org/ivy/history/latest-milestone/resolver/ibiblio.html
Dawid
On Thu, Jun 28, 2012 at 8:31 AM, Lance Norskog <[email protected]> wrote:
> My mistake. I meant that Ivy was not using the maven.org repos at all.
>
> On Wed, Jun 27, 2012 at 11:17 PM, Dawid Weiss
> <[email protected]> wrote:
>> Interesting. I think they should be identical mirrors of each other.
>> Benson has more knowledge of Maven -- perheps he'll be able to tell if
>> this is a bug in the repo sync or something to be expected?
>>
>> Dawid
>>
>> On Thu, Jun 28, 2012 at 4:11 AM, Lance Norskog <[email protected]> wrote:
>>> How can I get ivy to include the maven.org repo2 in the resolver list?
>>> Is there a reason it is not in the list?
>>>
>>> I ask because there is an artifact (extjwnl) which is only on repo2.
>>>
>>> --
>>> Lance Norskog
>>> [email protected]
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: [email protected]
>>> For additional commands, e-mail: [email protected]
>>>
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: [email protected]
>> For additional commands, e-mail: [email protected]
>>
>
>
>
> --
> Lance Norskog
> [email protected]
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [email protected]
> For additional commands, e-mail: [email protected]
>
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
