Hi, I know we had this discussion here and there, however so far we don't have a good solution and currently if bundles use jcr 1.0 as a dependency they end up with an import of the jcr packages that just imports 1.x - so these bundles fail in a jcr 2 environment. This is in fact an issue with the jcr 2 bundle which should export both versions.
I think we really need a solution now, so either we create our own jcr wrapper or we ramp up and require jcr 2 for all bundles. While in the pure dependency sense, requiring version 2.0 of an api when 1.0 is sufficient is wrong, it seems to be the most pragmatic solution we could do today. And in practice requiring 2.0 isn't a problem. If no one complains or comes up with a doable alternative, I'll change the version in the parent pom in the next days :) Carsten -- Carsten Ziegeler [email protected]
