You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@jackrabbit.apache.org by Apache Jenkins Server <je...@builds.apache.org> on 2011/11/28 13:30:22 UTC
Jackrabbit-trunk - Build # 1756 - Still Unstable
The Apache Jenkins build system has built Jackrabbit-trunk (build #1756)
Status: Still Unstable
Check console output at https://builds.apache.org/job/Jackrabbit-trunk/1756/ to view the results.
Jackrabbit-trunk - Build # 1758 - Still Unstable
Posted by Apache Jenkins Server <je...@builds.apache.org>.
The Apache Jenkins build system has built Jackrabbit-trunk (build #1758)
Status: Still Unstable
Check console output at https://builds.apache.org/job/Jackrabbit-trunk/1758/ to view the results.
Jackrabbit-trunk - Build # 1757 - Still Unstable
Posted by Apache Jenkins Server <je...@builds.apache.org>.
The Apache Jenkins build system has built Jackrabbit-trunk (build #1757)
Status: Still Unstable
Check console output at https://builds.apache.org/job/Jackrabbit-trunk/1757/ to view the results.
Re: Jackrabbit-trunk - Build # 1756 - Still Unstable
Posted by Julian Reschke <ju...@gmx.de>.
On 2011-11-28 13:30, Apache Jenkins Server wrote:
> The Apache Jenkins build system has built Jackrabbit-trunk (build #1756)
>
> Status: Still Unstable
>
> Check console output at https://builds.apache.org/job/Jackrabbit-trunk/1756/ to view the results.
So, this includes query tests failing in jcr2spi. It appears these are
caused by earlier problems; when I rm ./target and do mvn clean install
in this subproject, the problems go away.
Best regards, Julian