[cdi-dev] EDR1 ready to be released

[Antoine Sabot-Durand]

> Please correct me if I got this wrong, you like to have a org.boss.weld
> package in the EDR wording?
>

You're wrong. Nobody's proposed such a thing. But to be sure, you might
want to re-read carefully the spec (nice trick to have another review on
the spec split ;) ).

More seriously, the spec mention @Priority from commons annotation and it
will stay like that, because it's the target. Wether we keep it in weld or
move it in an experimental package in the spec, this content will not
change.
I'll write a blog post explaining why user can't use the official @Priority
yet and what package to use in the meantime.
I said I find more consistent to have it in Weld experimental, because we
said  last week that we didn't want to put temp feature in the spec & API.


> In that case a strict -1 for any org.jboss.weld package in the official
> spec EDR!
> That’s a total no-go and is legally not possible as you would force ALL
> implementors to break trademark laws.
> This would also probably (in extremis) diminish the Weld trademark… So
> this is something I guess JBoss would like to prevent as well…
>
> LieGrue,
> strub
>
> > Am 29.06.2015 um 12:44 schrieb Jozef Hartinger <jharting at redhat.com>:
> >
> > Hi Antoine,
> >
> > I dislike inventing temporary behavior. For @Priority there seems to be
> consensus about the observer ordering behavior already. We just need a way
> to enable it until the annotations spec is updated. Weld experimental
> package will work fine.
> >
> > Jozef
> >
> > On 06/29/2015 12:19 PM, Antoine Sabot-Durand wrote:
> >> Hi Jozef,
> >>
> >> I thought you didn't like to have temp stuff in the spec, so fr me it
> was obvious that we should use the weld experimental package.
> >> Any thoughts?
> >>
> >> Antoine
> >> Le lun. 29 juin 2015 à 11:38, Jozef Hartinger <jharting at redhat.com> a
> écrit :
> >> How do we deal with the lack of parameter-level @Priority in the
> meantime?
> >>
> >>
> >> On 06/25/2015 11:19 AM, Antoine Sabot-Durand wrote:
> >>> Hi guys,
> >>>
> >>> The branch 2.0-EDR1 is ready for release.
> >>>
> >>> Beyond the source, you can check javadoc here:
> >>> https://dl.dropboxusercontent.com/u/2898173/EDR1-Doc/index.html
> >>>
> >>> And spec here:
> >>> https://dl.dropboxusercontent.com/u/2898173/cdi-spec.html
> >>>
> >>> Or PDF version:
> >>> https://dl.dropboxusercontent.com/u/2898173/cdi-2.0-EDR1.pdf
> >>>
> >>> I have still some work on introduction (major changes, etc…) and on
> copyright in source files and intend to start release process (three the
> JCP) tomorrow.
> >>>
> >>> Antoine
> >>>
> >>>
> >>> _______________________________________________
> >>> cdi-dev mailing list
> >>>
> >>> cdi-dev at lists.jboss.org
> >>> https://lists.jboss.org/mailman/listinfo/cdi-dev
> >>>
> >>>
> >>> Note that for all code provided on this list, the provider licenses
> the code under the Apache License, Version 2 (
> >>> http://www.apache.org/licenses/LICENSE-2.0.html). For all other ideas
> provided on this list, the provider waives all patent and other
> intellectual property rights inherent in such information.
> >>
> >
> > _______________________________________________
> > cdi-dev mailing list
> > cdi-dev at lists.jboss.org
> > https://lists.jboss.org/mailman/listinfo/cdi-dev
> >
> > Note that for all code provided on this list, the provider licenses the
> code under the Apache License, Version 2 (
> http://www.apache.org/licenses/LICENSE-2.0.html). For all other ideas
> provided on this list, the provider waives all patent and other
> intellectual property rights inherent in such information.
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/cdi-dev/attachments/20150629/4766954d/attachment.html