Managing Dependencies to different Versions of the same App about al-go HOT 5 OPEN

Sorry for the delay
If you add appDependencyProbingPaths to every repository, then it works right?
But when you have appDependencyProbingPaths in ALGOORGSETTINGS and also in a repository - I think they are merged together and you probably end up with both - is this what you see?

from al-go.

I will do some more experimenting to see whether we can isolate any configuration that works. If they were merged together (i.e., from the org level and the repo level), how would I see that? In the logs?

from al-go.

Question: is an appDependencyProbingPaths setting at the repo level supposed to override one at the org level?

from al-go.

I think that currently, they will be added together (as all arrays in settings)

from al-go.

Ah. So that would result in a single array of repositories, all of which would be searched. That would make sense.

In the meantime, I find that we might be able to eliminate this requirement altogether by bringing these two outlier extension apps up to the current version of our base app.

I say we can close this issue for now; thanks for the clarification--now we know how that works.

from al-go.