It seems I'm unable to use any configuration to configure a CacheLoader.
I'm having better luck if I do all of this:
- force my CacheLoader to implement CacheStore (didn't want to do that yet)
- use the programmatic configuration, and *legacy* deprecated code only
- avoid to configure any option - I'm having to hardcode what I need
it do to in the CacheLoader implementation
Only then I'm able to test my things; in fact most of the new failures
are related to CacheLoader tests.
On 17 May 2012 14:50, Galder Zamarreño <galder(a)redhat.com> wrote:
Some of this could be result of migrating to the new configuration in
master, I'll have a look over next few days.
On May 17, 2012, at 12:56 AM, Sanne Grinovero wrote:
> Build 198 [1] introduced 25 failures, nearly doubling the amount to
> 43. Ok, business as usual.. In fact, no worries I have recently
> configured a mail filter "from jenkins -> SPAM" as it was too painful.
>
> But this time it broke the build of the Lucene Directory!
> I'll have my revenge, très-bien froide.
>
> 1 -
https://infinispan.ci.cloudbees.com/job/Infinispan-master-JDK6-tcp-NON_PA...
>
> _______________________________________________
> infinispan-dev mailing list
> infinispan-dev(a)lists.jboss.org
>
https://lists.jboss.org/mailman/listinfo/infinispan-dev
--
Galder Zamarreño
Sr. Software Engineer
Infinispan, JBoss Cache
_______________________________________________
infinispan-dev mailing list
infinispan-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/infinispan-dev