Perhaps  you are printing the messages in the wrong spot while recursing...just 
a thought. Otherwise, it might be necessary to see your repository.xml file.


"San Martín, Matías" <[email protected]> wrote:

>Hi everybody, 
>first of all sorry about the odd mail subject, I will try to explain
>myself better.
>
>The context of the problem:
>=================
>
>I have the following bundles:
>Main 
>   Depends on (packages): Console, InterConsole, Runner
>Console: 
>   Depends on: InterConsole
>   Exports (package): Console
>InterConsole:
>   Exports: InterConsole
>Runner:
>   Depends on: InterConsole, InterRunner
>   Exports: Runner
>InterRunner:
>   Exports: InterRunner
>//////////////////////////
>
>I have the following OBR repositories:
>Repo1: (contains) Main, Console, InterConsole
>Repo2: Runner
>Repo3: InterRunner
>//////////////////////////
>
>Then I have this (pseudo)code/logic:
>
>1- Install Repo1 in OBR repository admin
>2- discover resource Main
>3- get a new resolver
>4- try to deploy Main
>5- If there are missing dependencies, print them, else go to pont 9
>6- Find repository that contains missing dependencies
>7- Install repository found
>8- Go to point 3
>9- Bundle deployed
>
>The run output:
>==========
>
>The execution of the logic just mentioned prints this:
>Got new resolver
>Missing dependency: InterRunner
>Missing dependency: Runner
>Installed Repository 3
>Installed Repository 2
>Got new resolver
>Bundle deployed
>
>The question/problem:
>===============
>How is possible that the first resolver knows about the missing
>dependency InterRunner if the Runner is not known yet???!!!
>
>Any thoughts???
>
>Thank you in advance for taking the time to read and give any thought
>to
>my problem.
>Regards

Reply via email to