Ahhhh... Too early in the morning, I guess... 3.0 branch... That wasn't building when I committed it, so this is expected.
I tried to merge develop back into 3.0 and it was massively complex, so I think I will drop 3.0 later and redo the work, since what has been done is most mundane, but tedious, work, unlike the merge, which requires a lot of thinking and testing that are likely to fail. So, no need to pay attention to this right now. On Mon, Jun 15, 2015 at 7:36 AM, Niclas Hedhman <[email protected]> wrote: > Are you sure that is 'develop', since I think I have already removed neo4j > ES... > > Cheers > Niclas > > On Mon, Jun 15, 2015 at 4:16 AM, Paul Merlin <[email protected]> wrote: > >> This is the Java8 build of the 3.0 branch that currently fail. >> First run on builds.apache.org. >> It fails there too, that's consistent. >> It won't bother us until next commits in this branch, the job polls the >> git branch for new commits. >> >> 'nite >> >> > > > -- > Niclas Hedhman, Software Developer > http://zest.apache.org - New Energy for Java > -- Niclas Hedhman, Software Developer http://zest.apache.org - New Energy for Java
