Those decisions where intensional. Normally Fabian would be the right person to answer this, but I will try it anyway:
This is only a short summary as there was a long discussion that leaded to this: Dependency management for Stanbol modules can not be in the parent (1) because modules versions as this would not allow releasing components without releasing also the parent. Components that depending on the oldest supported version gives users more freedom in their launcher configurations. In addition keeping dependencies to released version is critical for released of single/subsets of components. If Stanbol modules do not depend on the latest version doing the dependency management in the parent does not work. Developers of modules need to manage their dependencies themselves. Only the Stanbol launchers are supposed to use the newest versions of modules. On Wed, Nov 21, 2012 at 5:56 PM, Reto Bachmann-Gmür <[email protected]> wrote: > e.g. the > enhancer using 0.9.0-incubating of commons.web.base. This can cause > incompatibilities as in the launchers 0.10.1-SNAPSHOT is used. If there is a change in the enhancer.jersey module that requires the current commons.web.base than the developer that introduces this change needs to update the dependency. This happened also to myself. But after some time one gets used to it. best Rupert -- | Rupert Westenthaler [email protected] | Bodenlehenstraße 11 ++43-699-11108907 | A-5500 Bischofshofen
