Hi Davide, The maven release plugin does change the version in the oak.version property for oak-examples See [1] for 1.3.16 release. I think what is causing problems is that the oak.version property should also have version 1.4.0-SNAPSHOT instead of 1.4-SNAPSHOT as was changed for the main artifacts [2].
Thanks Amit [1] https://github.com/apache/jackrabbit-oak/commit/58fc76337851c5a1f557da9e55743f1a1c604115 [2] https://github.com/apache/jackrabbit-oak/commit/59744433913619cff224547c5e6578395ba8b7e9 On Tue, Mar 1, 2016 at 11:11 PM, Chetan Mehrotra <[email protected]> wrote: > On Tue, Mar 1, 2016 at 10:51 PM, Davide Giannella <[email protected]> > wrote: > > I'm kind-of stuck in the release process as oak-examples contains > > dependencies to oak-1.4-SNAPSHOT. The problem is the -SNAPSHOT bit. > > Wondering how it used to work so far for various 1.3.x releases > > One approach we can try is get rid of oak.version and make use of > project.version. Such a way should be similar to how oak-lucene > depends on oak-core and hence should work > > Chetan Mehrotra >
