Konrad Windszus wrote > Sorry, indeed I didn't read carefully enough. > Still I would have expected, that in case the release is not yet available > from Maven Central the dependency would be rolled back to the previous > SNAPSHOT version (which would have been 2.1.5-SNAPSHOT), because that one > will not be modified any longer. But instead you referenced the new > development version, which might be influenced by other commits. > At first glance (without looking at the history) it is impossible to tell, > whether that was referenced, because > a) the previous release is not yet available at Maven Central > b) the SNAPSHOT already contains an important fix which did not yet end up in > a release >
We can't use the previous snapshot as this might not be available. Imagine someone checking out Sling and trying to build it. It will fail as the previous version is not part of the reactor. We run into this issue a lot during the year, when a release is done and the snapshot reference is *not* updated. I think the problem is not huge, a vote usually takes three dates, so it's very unlikely that something new is committed to the module under vote in this period. And even if, it should be compatible anyway. The really annoying part is that we don't have tooling for this and updating the snapshot dependencies for releases is a manual task. Carsten -- Carsten Ziegeler Adobe Research Switzerland [email protected]
