wicket-cdi-1.1 is in a terrible state at the moment. Both in master and wicket-6.x. Perhaps we should remove or disable it for now in master and update it once I've done my work on 6.x.
On Wed, Nov 20, 2013 at 3:39 PM, Martin Grigorov <[email protected]>wrote: > JS UI tests run only for master branch (v.7). > There is no such problem in wicket-6.x. I guess something is not merged to > master ... > I'll check it tomorrow if someone else don't do it earlier. > > > On Wed, Nov 20, 2013 at 4:33 PM, Emond Papegaaij < > [email protected] > > wrote: > > > Hi Martin, > > > > Is this on wicket 6 or 7? I'm currently working on a side-branch of the > > wicket-6.x branch. This error is fixed in more recent versions of weld, > so > > it > > seems this testcase is using an old version of weld. The next version of > > weld not even logs a warning anymore, only a debug. > > > > Best regards, > > Emond > > > > On Wednesday 20 November 2013 16:26:07 Martin Grigorov wrote: > > > Hi Emond, > > > > > > I guess your recent changes related to CDI broke the Wicket Examples > > CDI > > > example. > > > The JavaScript UI tests fail with: > > > > > > org.jboss.weld.exceptions.DefinitionException: WELD-000070 Simple > > bean > > > [EnhancedAnnotatedTypeImpl] class > > > org.apache.wicket.devutils.debugbar.DebugBar$3 cannot be a non- > > static inner > > > class > > > at > > > > > > org.jboss.weld.injection.producer.BasicInjectionTarget.checkType(BasicInjec > > t > > > ionTarget.java:81) at > > > > > > > > org.jboss.weld.injection.producer.BasicInjectionTarget.<init>(BasicInjection > > > Target.java:69) at > > > > > > org.jboss.weld.injection.producer.BeanInjectionTarget.<init>(BeanInjection > > Ta > > > rget.java:52) at > > > > > > org.jboss.weld.manager.InjectionTargetFactoryImpl.createInjectionTarget(Inj > > e > > > ctionTargetFactoryImpl.java:95) > > > > > > This is related to the problem that led to Wicket 6.9.1 release. > > > > > > Please fix it as you find appropriate. > > > > >
