Oh I see what you mean.
Well, if it's not able to establish dependencies, perhaps it doesn't take
your complex ant file included into account.
In your example, I put explicit values in the ivy file for UtilPrj and it
seems to come back in the expected order.
<info organisation="com.test.ivy" module="UtilPrj" revision="${test.release}"
status="${proj.status}"/>
On Mon, Sep 22, 2014 at 11:37 AM, Zac Jacobson <pie....@gmail.com> wrote:
> Your ant script is building projects in alphabetical order, which happens
> to not match your ivy dependency order. So PrjDependingOnUtilPrj is built
> first, but it can't find a UtilPrj because that project hasn't been
> built/published yet.
>
> You should give your master ant file the explicit order to build/publish
> things, if that's what you want to do.
>
> On Mon, Sep 22, 2014 at 2:07 AM, Ionut Scutaru <ionut.scut...@gmail.com>
> wrote:
>
>> Hi,
>>
>> I'm using Ivy 2.2.0 and Ant 1.9.2 and I'm currently facing a problem
>> related to ivy:buildlist: it generates the list of dependencies in the
>> project in the wrong order.
>>
>> I'm attaching a configuration that shows the problem that I'm facing.
>>
>> I'm running the build.xml located in the deploymentUtilities/ant.new
>> folder and I see this error in the console:
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>> *[ivy:resolve]
>> ::::::::::::::::::::::::::::::::::::::::::::::[ivy:resolve]
>> :: UNRESOLVED DEPENDENCIES ::[ivy:resolve]
>> ::::::::::::::::::::::::::::::::::::::::::::::[ivy:resolve] ::
>> com.test.ivy#UtilPrj;1.0.0: not found[ivy:resolve]
>> ::::::::::::::::::::::::::::::::::::::::::::::[ivy:resolve][ivy:resolve][ivy:resolve]
>> :: USE VERBOSE OR DEBUG MESSAGE LEVEL FOR MORE DETAILS*
>>
>> Could anybody help me ? I really don't understand why the order is not
>> the correct one.
>>
>> Thank you !
>>
>
>
