hi jukka
That should still be possible, though with one caveat: the latest version of jcr-commons in the build would now be the latest _released_ version.
Is this a problem?
it isn't a problem but it can be pretty cumbersome if fixes/improvements made to any of the commons project are floating around waiting for the next release cycle (that takes forever for some reason or the other) and i need to use them already in the core modules (basically that was the reason why the issue was detected at all)... in that situation i will have to wait for the next release or locally adjust the pom setting the dependency to the current commons snapshot. that latter is pretty much error prone, i'd say. angela
