You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@deltaspike.apache.org by Gerhard Petracek <ge...@gmail.com> on 2014/11/17 19:54:29 UTC
first steps for the next release
hi @ all,
if there are no objections, i will start with the first steps for the next
release (v1.2.0) by the end of next week.
@ v1.2.0 instead of v1.1.1:
we have some new features (esp. >optional< cdi 1.1+ support - e.g. the
optional delegation to CDI.current().getBeanManager()).
regards,
gerhard
Re: first steps for the next release
Posted by Mark Struberg <st...@yahoo.de>.
Oh in that case +1 for 1.2.0 as well.
LieGrue,
strub
>________________________________
> From: Gerhard Petracek <ge...@gmail.com>
>To: "dev@deltaspike.apache.org" <de...@deltaspike.apache.org>; Mark Struberg <st...@yahoo.de>
>Sent: Tuesday, 18 November 2014, 9:55
>Subject: Re: first steps for the next release
>
>
>
>@mark:
>your change is not the reason (that's really just a bugfix) - there are several other tickets (see the current release notes).
>
>
>regards,
>gerhard
>
>
Re: first steps for the next release
Posted by Gerhard Petracek <ge...@gmail.com>.
@mark:
your change is not the reason (that's really just a bugfix) - there are
several other tickets (see the current release notes).
regards,
gerhard
2014-11-18 9:41 GMT+01:00 Mark Struberg <st...@yahoo.de>:
> -1 for 1.2.0 and
> +1 for releasing 1.1.1
>
>
> The fix in BeanManagerProvider was just a minor lookup to the parent
> ClassLoader. Most of the time you will not even see that it didn't work as
> it was really just broken for some scenarios. And only since a short time.
> So I'd really rather go 1.1.1. There is nothing which changed in our API
> and thus requires the minor version to get bumped ...
>
>
> LieGrue,
> strub
>
>
>
> ----- Original Message -----
> > From: Christian Kaltepoth <ch...@kaltepoth.de>
> > To: dev@deltaspike.apache.org
> > Cc:
> > Sent: Tuesday, 18 November 2014, 8:10
> > Subject: Re: first steps for the next release
> >
> > +1 for 1.2.0
> >
> >
> > 2014-11-17 20:38 GMT+01:00 Romain Manni-Bucau <rm...@gmail.com>:
> >
> >> +0 (i dont like all the noise around BeanManagerProvider but seems
> alone so
> >> dont want to block)
> >> Le 17 nov. 2014 20:20, "Jason Porter"
> > <li...@gmail.com> a écrit :
> >>
> >> > +1
> >> > On Mon, Nov 17, 2014 at 12:10 Rafael Benevides
> > <be...@redhat.com>
> >> > wrote:
> >> >
> >> > > +1 for 1.2.0
> >> > >
> >> > >
> >> > > On 11/17/14 16:54, Gerhard Petracek wrote:
> >> > > > hi @ all,
> >> > > >
> >> > > > if there are no objections, i will start with the first
> > steps for the
> >> > > next
> >> > > > release (v1.2.0) by the end of next week.
> >> > > >
> >> > > > @ v1.2.0 instead of v1.1.1:
> >> > > > we have some new features (esp. >optional< cdi 1.1+
> > support - e.g.
> >> the
> >> > > > optional delegation to CDI.current().getBeanManager()).
> >> > > >
> >> > > > regards,
> >> > > > gerhard
> >> > > >
> >> > >
> >> > >
> >> >
> >>
> >
> >
> >
> > --
> > Christian Kaltepoth
> > Blog: http://blog.kaltepoth.de/
> > Twitter: http://twitter.com/chkal
> > GitHub: https://github.com/chkal
> >
>
Re: first steps for the next release
Posted by Mark Struberg <st...@yahoo.de>.
-1 for 1.2.0 and
+1 for releasing 1.1.1
The fix in BeanManagerProvider was just a minor lookup to the parent ClassLoader. Most of the time you will not even see that it didn't work as it was really just broken for some scenarios. And only since a short time. So I'd really rather go 1.1.1. There is nothing which changed in our API and thus requires the minor version to get bumped ...
LieGrue,
strub
----- Original Message -----
> From: Christian Kaltepoth <ch...@kaltepoth.de>
> To: dev@deltaspike.apache.org
> Cc:
> Sent: Tuesday, 18 November 2014, 8:10
> Subject: Re: first steps for the next release
>
> +1 for 1.2.0
>
>
> 2014-11-17 20:38 GMT+01:00 Romain Manni-Bucau <rm...@gmail.com>:
>
>> +0 (i dont like all the noise around BeanManagerProvider but seems alone so
>> dont want to block)
>> Le 17 nov. 2014 20:20, "Jason Porter"
> <li...@gmail.com> a écrit :
>>
>> > +1
>> > On Mon, Nov 17, 2014 at 12:10 Rafael Benevides
> <be...@redhat.com>
>> > wrote:
>> >
>> > > +1 for 1.2.0
>> > >
>> > >
>> > > On 11/17/14 16:54, Gerhard Petracek wrote:
>> > > > hi @ all,
>> > > >
>> > > > if there are no objections, i will start with the first
> steps for the
>> > > next
>> > > > release (v1.2.0) by the end of next week.
>> > > >
>> > > > @ v1.2.0 instead of v1.1.1:
>> > > > we have some new features (esp. >optional< cdi 1.1+
> support - e.g.
>> the
>> > > > optional delegation to CDI.current().getBeanManager()).
>> > > >
>> > > > regards,
>> > > > gerhard
>> > > >
>> > >
>> > >
>> >
>>
>
>
>
> --
> Christian Kaltepoth
> Blog: http://blog.kaltepoth.de/
> Twitter: http://twitter.com/chkal
> GitHub: https://github.com/chkal
>
Re: first steps for the next release
Posted by Christian Kaltepoth <ch...@kaltepoth.de>.
+1 for 1.2.0
2014-11-17 20:38 GMT+01:00 Romain Manni-Bucau <rm...@gmail.com>:
> +0 (i dont like all the noise around BeanManagerProvider but seems alone so
> dont want to block)
> Le 17 nov. 2014 20:20, "Jason Porter" <li...@gmail.com> a écrit :
>
> > +1
> > On Mon, Nov 17, 2014 at 12:10 Rafael Benevides <be...@redhat.com>
> > wrote:
> >
> > > +1 for 1.2.0
> > >
> > >
> > > On 11/17/14 16:54, Gerhard Petracek wrote:
> > > > hi @ all,
> > > >
> > > > if there are no objections, i will start with the first steps for the
> > > next
> > > > release (v1.2.0) by the end of next week.
> > > >
> > > > @ v1.2.0 instead of v1.1.1:
> > > > we have some new features (esp. >optional< cdi 1.1+ support - e.g.
> the
> > > > optional delegation to CDI.current().getBeanManager()).
> > > >
> > > > regards,
> > > > gerhard
> > > >
> > >
> > >
> >
>
--
Christian Kaltepoth
Blog: http://blog.kaltepoth.de/
Twitter: http://twitter.com/chkal
GitHub: https://github.com/chkal
Re: first steps for the next release
Posted by Romain Manni-Bucau <rm...@gmail.com>.
+0 (i dont like all the noise around BeanManagerProvider but seems alone so
dont want to block)
Le 17 nov. 2014 20:20, "Jason Porter" <li...@gmail.com> a écrit :
> +1
> On Mon, Nov 17, 2014 at 12:10 Rafael Benevides <be...@redhat.com>
> wrote:
>
> > +1 for 1.2.0
> >
> >
> > On 11/17/14 16:54, Gerhard Petracek wrote:
> > > hi @ all,
> > >
> > > if there are no objections, i will start with the first steps for the
> > next
> > > release (v1.2.0) by the end of next week.
> > >
> > > @ v1.2.0 instead of v1.1.1:
> > > we have some new features (esp. >optional< cdi 1.1+ support - e.g. the
> > > optional delegation to CDI.current().getBeanManager()).
> > >
> > > regards,
> > > gerhard
> > >
> >
> >
>
Re: first steps for the next release
Posted by Jason Porter <li...@gmail.com>.
+1
On Mon, Nov 17, 2014 at 12:10 Rafael Benevides <be...@redhat.com> wrote:
> +1 for 1.2.0
>
>
> On 11/17/14 16:54, Gerhard Petracek wrote:
> > hi @ all,
> >
> > if there are no objections, i will start with the first steps for the
> next
> > release (v1.2.0) by the end of next week.
> >
> > @ v1.2.0 instead of v1.1.1:
> > we have some new features (esp. >optional< cdi 1.1+ support - e.g. the
> > optional delegation to CDI.current().getBeanManager()).
> >
> > regards,
> > gerhard
> >
>
>
Re: first steps for the next release
Posted by Rafael Benevides <be...@redhat.com>.
+1 for 1.2.0
On 11/17/14 16:54, Gerhard Petracek wrote:
> hi @ all,
>
> if there are no objections, i will start with the first steps for the next
> release (v1.2.0) by the end of next week.
>
> @ v1.2.0 instead of v1.1.1:
> we have some new features (esp. >optional< cdi 1.1+ support - e.g. the
> optional delegation to CDI.current().getBeanManager()).
>
> regards,
> gerhard
>
Re: first steps for the next release
Posted by Antoine Sabot-Durand <an...@sabot-durand.net>.
+1 for 1.2.0
> Le 17 nov. 2014 à 19:54, Gerhard Petracek <ge...@gmail.com> a écrit :
>
> hi @ all,
>
> if there are no objections, i will start with the first steps for the next
> release (v1.2.0) by the end of next week.
>
> @ v1.2.0 instead of v1.1.1:
> we have some new features (esp. >optional< cdi 1.1+ support - e.g. the
> optional delegation to CDI.current().getBeanManager()).
>
> regards,
> gerhard