Hi, On Thu, Jan 8, 2009 at 8:04 PM, Felix Meschberger <[email protected]> wrote: > Jukka Zitting schrieb: >> I'm inclined to upgrade all the dependent components so that the 1.5.1 >> build will not end up referring to two different versions of the same >> component. > > No, I would neither upgrade nor release any dependent component. This > would be very confusing and not worth the effort.
It looks like at least jackrabbit-webdav needs to be bumped to 1.5.1 with the upgraded jcr-commons dependency as it is affected by the JCR-1926 issue. The components that are not changed since 1.5.0 (in the 1.5 branch) and not affected by JCR-1926 are: classloader, jcr-rmi, jcr2spi, spi-commons and spi2jcr. I guess we have more people looking at the Maven repository and wondering whether they should upgrade their dependencies than we have people looking at the source build and wondering why these components are pulling in an earlier version of jcr-commons when a more recent one is right there to be used. Well, at least the proposed new subproject will help avoid similar issues in future by giving many of these components their own independent release cycles. BR, Jukka Zitting
