You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@deltaspike.apache.org by Mark Struberg <st...@yahoo.de> on 2013/08/11 15:22:04 UTC
all tests green (almost)
Hi folks!
All our CI are now green again. The only Exception being weld-2.0.0 and 2.0.0.SP1.
I first guessed it's due to the missing getBean() handling in our InjectionPoints created via BeanBuilder. But it turns our it had no impact.
These 2 weld verions fail with an internal proxy failure (NPE deep inside the proxy due to wrong handling of abstract classes).
It seems those errors already got fixed with weld-2.0.1 onwards (both works perfectly fine in our CI builds).
Are those buggy 2.0.0 versions used in some containers? Or can we just remove them from our CI because they are known to be broken?
txs and LieGrue,
strub
PS: like to finally do 0.5 this week...
Re: all tests green (almost)
Posted by Romain Manni-Bucau <rm...@gmail.com>.
I think so too, this is not a main feature of DS IMO
Le 11 août 2013 16:43, "John D. Ament" <jo...@gmail.com> a écrit :
> Well, it looks like Glassfish 4 is shipping with 2.0.0.SP1.
>
> Maybe we can just list this as a known limitation?
>
> On Sun, Aug 11, 2013 at 9:22 AM, Mark Struberg <st...@yahoo.de> wrote:
> > Hi folks!
> >
> > All our CI are now green again. The only Exception being weld-2.0.0 and
> 2.0.0.SP1.
> >
> > I first guessed it's due to the missing getBean() handling in our
> InjectionPoints created via BeanBuilder. But it turns our it had no impact.
> > These 2 weld verions fail with an internal proxy failure (NPE deep
> inside the proxy due to wrong handling of abstract classes).
> > It seems those errors already got fixed with weld-2.0.1 onwards (both
> works perfectly fine in our CI builds).
> >
> > Are those buggy 2.0.0 versions used in some containers? Or can we just
> remove them from our CI because they are known to be broken?
> >
> > txs and LieGrue,
> > strub
> >
> >
> > PS: like to finally do 0.5 this week...
>
Re: all tests green (almost)
Posted by "John D. Ament" <jo...@gmail.com>.
Well, it looks like Glassfish 4 is shipping with 2.0.0.SP1.
Maybe we can just list this as a known limitation?
On Sun, Aug 11, 2013 at 9:22 AM, Mark Struberg <st...@yahoo.de> wrote:
> Hi folks!
>
> All our CI are now green again. The only Exception being weld-2.0.0 and 2.0.0.SP1.
>
> I first guessed it's due to the missing getBean() handling in our InjectionPoints created via BeanBuilder. But it turns our it had no impact.
> These 2 weld verions fail with an internal proxy failure (NPE deep inside the proxy due to wrong handling of abstract classes).
> It seems those errors already got fixed with weld-2.0.1 onwards (both works perfectly fine in our CI builds).
>
> Are those buggy 2.0.0 versions used in some containers? Or can we just remove them from our CI because they are known to be broken?
>
> txs and LieGrue,
> strub
>
>
> PS: like to finally do 0.5 this week...
Re: all tests green (almost)
Posted by Mark Struberg <st...@yahoo.de>.
Txs!
I've now introduced a mechanism to skip certain tests based on the cdi-container being used.
See CdiContainerUnderTest.
Now even the weld-2.0.0 CI went green, woha!
LieGrue,
strub
----- Original Message -----
> From: Gerhard Petracek <ge...@gmail.com>
> To: dev@deltaspike.apache.org
> Cc:
> Sent: Sunday, 11 August 2013, 17:19
> Subject: Re: all tests green (almost)
>
> please have a look at the info i added to [1] back then.
>
> regards,
> gerhard
>
> [1]
> https://builds.apache.org/view/A-D/view/DeltaSpike/job/DeltaSpike%20Weld%202.0.0.SP1/
>
>
>
> 2013/8/11 Mark Struberg <st...@yahoo.de>
>
>> Hi folks!
>>
>> All our CI are now green again. The only Exception being weld-2.0.0 and
>> 2.0.0.SP1.
>>
>> I first guessed it's due to the missing getBean() handling in our
>> InjectionPoints created via BeanBuilder. But it turns our it had no impact.
>> These 2 weld verions fail with an internal proxy failure (NPE deep inside
>> the proxy due to wrong handling of abstract classes).
>> It seems those errors already got fixed with weld-2.0.1 onwards (both
>> works perfectly fine in our CI builds).
>>
>> Are those buggy 2.0.0 versions used in some containers? Or can we just
>> remove them from our CI because they are known to be broken?
>>
>> txs and LieGrue,
>> strub
>>
>>
>> PS: like to finally do 0.5 this week...
>>
>
Re: all tests green (almost)
Posted by Gerhard Petracek <ge...@gmail.com>.
please have a look at the info i added to [1] back then.
regards,
gerhard
[1]
https://builds.apache.org/view/A-D/view/DeltaSpike/job/DeltaSpike%20Weld%202.0.0.SP1/
2013/8/11 Mark Struberg <st...@yahoo.de>
> Hi folks!
>
> All our CI are now green again. The only Exception being weld-2.0.0 and
> 2.0.0.SP1.
>
> I first guessed it's due to the missing getBean() handling in our
> InjectionPoints created via BeanBuilder. But it turns our it had no impact.
> These 2 weld verions fail with an internal proxy failure (NPE deep inside
> the proxy due to wrong handling of abstract classes).
> It seems those errors already got fixed with weld-2.0.1 onwards (both
> works perfectly fine in our CI builds).
>
> Are those buggy 2.0.0 versions used in some containers? Or can we just
> remove them from our CI because they are known to be broken?
>
> txs and LieGrue,
> strub
>
>
> PS: like to finally do 0.5 this week...
>