Travis build was introduced after discovering compilation error in our few
tests after se boot refactoring. I plan to let it's introduction as any
isolated commit when merging.
It doesn't have any impact or API it spec content.
Antoine
Le mer. 13 juil. 2016 à 11:44, John D. Ament <john.d.ament(a)gmail.com> a
écrit :
At this point, I'm fine with #290, though I'm not sure why
its introducing
travis builds. I hope that no new issues pop up after renaming the class
with #296, I plan to push up javadocs and spec changes this evening.
John
On Wed, Jul 13, 2016 at 3:01 AM Antoine Sabot-Durand <
antoine(a)sabot-durand.net> wrote:
> Hi All,
>
> The release is still in 2 weeks and we have still 2 PR to close.
>
> I'm still waiting +1 or feedback on
>
https://github.com/cdi-spec/cdi/pull/290 to merge it or amend it.
>
> There is still discussion going on John's PR :
>
https://github.com/cdi-spec/cdi/pull/296
> I propose that we set up an hangout meeting on Monday or Tuesday to solve
> this.
>
> Antoine
>
_______________________________________________
> cdi-dev mailing list
> cdi-dev(a)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.