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 Hudson Server <hu...@hudson.zones.apache.org> on 2008/09/19 18:57:01 UTC
Hudson build is back to stable: Jackrabbit-ocm » Jackrabbit Object Content Mapping #118
See http://hudson.zones.apache.org/hudson/job/Jackrabbit-ocm/org.apache.jackrabbit$jackrabbit-ocm/118/changes
Re: Hudson build is back to stable: Jackrabbit-ocm » Jackrabbit Object Content Mapping #118
Posted by Christophe Lombart <ch...@gmail.com>.
ok thanks for the info and for your help
Christophe
On Sat, Sep 20, 2008 at 20:27, Jukka Zitting <ju...@gmail.com>wrote:
> Hi,
>
> On Fri, Sep 19, 2008 at 7:01 PM, Jukka Zitting <ju...@gmail.com>
> wrote:
> > Something weird going on with the OCM build. Probably a Hudson issue,
> > I'll look into it.
>
> I believe these weird build failures were caused by the newly added
> Jackrabbit-trunk-java14 build that, like the Jackrabbit-ocm build, is
> automatically triggered by a successful Jackrabbit-trunk build.
>
> With both builds running concurrently, it could be that the
> Jackrabbit-ocm build was trying to access a dependency jar from the
> Maven repository right when the Jackrabbit-trunk-java14 build was
> updating the jar. This would explain why the OCM build failed with a
> ClassNotFoundException on some very common Jackrabbit classes.
>
> I've now added a lock that prevents any two Jackrabbit builds from
> executing concurrently. This should avoid such race conditions.
>
> BR,
>
> Jukka Zitting
>
Re: Hudson build is back to stable: Jackrabbit-ocm » Jackrabbit Object Content Mapping #118
Posted by Jukka Zitting <ju...@gmail.com>.
Hi,
On Fri, Sep 19, 2008 at 7:01 PM, Jukka Zitting <ju...@gmail.com> wrote:
> Something weird going on with the OCM build. Probably a Hudson issue,
> I'll look into it.
I believe these weird build failures were caused by the newly added
Jackrabbit-trunk-java14 build that, like the Jackrabbit-ocm build, is
automatically triggered by a successful Jackrabbit-trunk build.
With both builds running concurrently, it could be that the
Jackrabbit-ocm build was trying to access a dependency jar from the
Maven repository right when the Jackrabbit-trunk-java14 build was
updating the jar. This would explain why the OCM build failed with a
ClassNotFoundException on some very common Jackrabbit classes.
I've now added a lock that prevents any two Jackrabbit builds from
executing concurrently. This should avoid such race conditions.
BR,
Jukka Zitting
Re: Hudson build is back to stable: Jackrabbit-ocm » Jackrabbit Object Content Mapping #118
Posted by Jukka Zitting <ju...@gmail.com>.
Hi,
On Fri, Sep 19, 2008 at 6:57 PM, Apache Hudson Server
<hu...@hudson.zones.apache.org> wrote:
> See http://hudson.zones.apache.org/hudson/job/Jackrabbit-ocm/org.apache.jackrabbit$jackrabbit-ocm/118/changes
Something weird going on with the OCM build. Probably a Hudson issue,
I'll look into it.
BR,
Jukka Zitting