yes, it's a freestyle job - it wasn't possible to start the Xvfb in the other configurations
On Sat, Jun 26, 2010 at 08:43, Kalle Korhonen <[email protected]> wrote: > Thanks Andreas, that's what I thought. I run with -U but no changes > yet, however there's a few caches in between my local repo and > Apache's (our nexus etc), will try again tomorrow. I don't have access > to Apache's Hudson instance but how's the Tapestry job declared as, is > it running mvn deploy directly? Hudson's Maven build configuration has > a "deploy" option that would deploy all libs after a multi-module > build is successfully completed rather than deploying one module at a > time to prevent these kind of problem. If it's a freestyle job you are > out of luck though (I recall that might be the case). > > Kalle > > > On Fri, Jun 25, 2010 at 2:49 PM, Andreas Andreou <[email protected]> wrote: >> it should be fine now, pls, try again >> >> On Sat, Jun 26, 2010 at 00:20, Andreas Andreou <[email protected]> wrote: >>> it's a bad combination of tapestry-ioc and tapestry-core >>> >>> Due to a build failure, the latest tapestry-core was never deployed >>> and unfortunately >>> hudson.zones.apache.org seems to be down lately... i'll try to deploy >>> tapestry-core myself >>> >>> PS From repository.apache.org i see as latest >>> tapestry-ioc-5.2.0-20100625.030603-136.pom and >>> tapestry-core-5.2.0-20100623.223543-99.pom >>> >>> On Fri, Jun 25, 2010 at 23:43, Kalle Korhonen >>> <[email protected]> wrote: >>>> On Fri, Jun 25, 2010 at 1:00 PM, Thiago H. de Paula Figueiredo >>>> <[email protected]> wrote: >>>>> On Fri, 25 Jun 2010 14:49:22 -0300, Kalle Korhonen >>>>> <[email protected]> wrote: >>>>>> Hmm.. Tynamo's examples started failing related to this change, see >>>>>> below. Maybe we just don't have (all of) the latest snapshots since >>>>>> the Hudson build failed as well. We aitre getting the snapshots directly >>>>>> from Apache's snapshot repository. Or maybe there's some other >>>>>> explanation, Howard are you still working on finishing these changes? >>>>> IdAllocator was recently changed into a non-internal class. >>>> >>>> Well that's stating the obvious. See that stack trace - it's not that >>>> anything external to Tapestry is referring to IdAllocator. >>>> >>>> Kalle >>>> >>>> --------------------------------------------------------------------- >>>> To unsubscribe, e-mail: [email protected] >>>> For additional commands, e-mail: [email protected] >>>> >>>> >>> >>> >>> >>> -- >>> Andreas Andreou - [email protected] - http://blog.andyhot.gr >>> Tapestry PMC / Tacos developer >>> Open Source / JEE Consulting >>> >> >> >> >> -- >> Andreas Andreou - [email protected] - http://blog.andyhot.gr >> Tapestry PMC / Tacos developer >> Open Source / JEE Consulting >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: [email protected] >> For additional commands, e-mail: [email protected] >> >> > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > > -- Andreas Andreou - [email protected] - http://blog.andyhot.gr Tapestry PMC / Tacos developer Open Source / JEE Consulting --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
