On Wed, Nov 21, 2012 at 8:51 PM, Fabian Christ <[email protected] > wrote:
> I just wanted to add that this practice was not invented by Stanbol but > rather adopted from the OSGi gurus in Sling. > Indeed, it's quite a mess there as well. Maybe we should watch out for maven gurus instead ;) Seriously, there might be some good reasons not to have them in the parent's dependency management (this makes module release more complicated). But I think they should nevertheless be kept up to date as otherwise we have no compile time check that the module will indeed work in the trunk version of the launcher. So I think we should regularly run a mvn versions:use-latest-versions -DincludesList="org.apache.stanbol" -DallowSnapshots=true -DexcludeReactor=false to update them. If a module needs to be release independently one can execute mvn versions:use-releases to switch to the latest released version. I couldn't find the thread where this was originally discussed, only the page on the website. Cheers, Reto
