What happened to this release? Has the issue with the TestACLAndMerge been resolved? I see that now we are already at 3.1.35-SNAPSHOT in https://github.com/apache/jackrabbit-filevault/blob/trunk/pom.xml#L26 but 3.1.34 has not been released yet (at least it is neither available at Maven Central nor being announced here). Konrad
> On 19 Jan 2017, at 10:55, Tobias Bocanegra <[email protected]> wrote: > > Hi, > > thanks a lot for testing. it might be that the source dist didn't include all > the files (thanks Tom for the hint.) > regards, Toby > > > > On Thu, Jan 19, 2017 at 6:12 PM, Stefan Guggisberg > <[email protected]> wrote: > On Thu, Jan 19, 2017 at 10:07 AM, Marcel Reutegger <[email protected]> wrote: > > On 16/01/17 08:36, Tobias Bocanegra wrote: > >> > >> A candidate for the Jackrabbit Filevault 3.1.34 release is available at: > >> > >> https://dist.apache.org/repos/dist/dev/jackrabbit/filevault/3.1.34/ > > > > > > I have reproducible test failures in TestACLAndMerge [0] when running 'mvn > > clean install'. The pasted output was generated with 'mvn > > -Dtest=TestACLAndMerge clean test' within vault-core. > > > > My environment is Mac OS X, Oracle Java 1.8, Maven 3.3.9. > > i get the same test failures (a newly setup machine with os x sierra, > java 1.8, maven 3.3.9). > > cheers > stefan > > > > > Regards > > Marcel > > > > [0] https://paste.apache.org/9hor >
