[cdi-dev] EDR1 ready to be released

Antoine Sabot-Durand antoine at sabot-durand.net
Mon Jun 29 08:45:24 EDT 2015


Weld experimental is my favorite, because it clearly states that it's not
final. I agree with Jozef, that we should avoid adding classes that are
obviously temporary in the API if we can.
Endorsement add extra steps making the code evaluation harder IMO. and code
evaluation by our users is our main target here.

Antoine

Le lun. 29 juin 2015 à 14:14, Jozef Hartinger <jharting at redhat.com> a
écrit :

>  That would work though given the extra steps to set up endorsed dir it
> will be simpler to use the experimental package for now I guess?
>
>
> On 06/29/2015 12:51 PM, Romain Manni-Bucau wrote:
>
> Isnt endorsing an option? Weld can provide its endorsed-API bundle no?
>  Le 29 juin 2015 03:44, "Jozef Hartinger" <jharting at redhat.com> a écrit :
>
>>  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 listcdi-dev at lists.jboss.orghttps://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/4e148a5e/attachment.html 


More information about the cdi-dev mailing list