[#AJF-1] Transitive dependency management

Archetype

Transitive dependency management

Created: 08/Jan/08 03:40 PM Updated: 17/Jun/08 08:06 PM

Component/s:

Transitive Dependency management

Affects Version/s:

0.1.0, 0.1.5

Fix Version/s:

0.8.0-beta, 0.8.0

Environment:

All navigators

Description

« Hide

When configuring whether "subModules" or "needs" for a module retrieved by a "subModules" or a "needs" configuration in its parent, any rPath/aPath configuration will be ignored and only the direct interpretation of the UMN will be used.

All

Comments

Change History

Sort Order:

Ascending order - Click to sort in descending order

[ Permlink | « Hide ]

Florian Traverse - 29/Jan/08 09:06 PM

Swiip's domain :)

[ Permlink | « Hide ]

Matthieu Lux - 16/Mar/08 11:17 PM

Archetype.require is one of the oldest method of Archetype. It has evolved many times by adding functionnalities.
In order to managed all configurations : submodules, needs, we complete this method.

Configurations needs a real recursive analysis but old require was not completely recursive.

I extract the resolution of the modules names in parameter of the require to correctly recurse on the configuration, manage layers to order loading by dependency

[ Permlink | « Hide ]

Florian Traverse - 01/Apr/08 06:03 PM

Updated bug metadata (like affected//fix version).

Nota: their may remains a little bug with subModules (everything ok with needs).