Actually that will not reveal what needs to be fixed in the pom.xml until another release was done.
> On 14 Mar 2016, at 08:48, Carsten Ziegeler <cziege...@apache.org> wrote: > > Bertrand Delacretaz wrote >> On Sun, Mar 13, 2016 at 10:41 AM, Carsten Ziegeler <cziege...@apache.org> >> wrote: >>> ...The really annoying part is that we don't have tooling for this and >>> updating the snapshot dependencies for releases is a manual task... >> >> Doing a full build, removing the org.apache.sling.* folders from you >> local Maven repository and building again with -o will cause the build >> to break on any out of date Sling SNAPSHOT references. >> >> It's not a fantastic "tool" but can be helpful IMO. >> > Sure, but it's an after the fact tool - it helps to find if something is > screwed up. It doesn't prevent from screwing up > > Carsten > > -- > Carsten Ziegeler > Adobe Research Switzerland > cziege...@apache.org
