Re: Blocked release of maven-sling-plugin

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 wrote: > > Bertrand Delacretaz wrote >> On Sun, Mar 13, 2016 at 10:41 AM, Carsten Ziegeler >> wrote:

Re: Blocked release of maven-sling-plugin

Bertrand Delacretaz wrote > On Sun, Mar 13, 2016 at 10:41 AM, Carsten Ziegeler > 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

Re: Blocked release of maven-sling-plugin

On Sun, Mar 13, 2016 at 10:41 AM, Carsten Ziegeler 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

Re: Blocked release of maven-sling-plugin

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

Re: Blocked release of maven-sling-plugin

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

RE: Blocked release of maven-sling-plugin

the comment explains it: "update dependencies to next development snapshot until releases are available on maven central" the plugin was released together with commons.json and commons.testing - and to avoid failing builds during the voting phase we have to update to next snapshot until the