<div dir="ltr"><div><div>Seems the vote got swamped among many other messages both here and in my mailbox;-O<br><br></div>The arguments leading towards the winning name sound good and logical, so that would be my vote, too.<br><br></div>Werner<br><div><div><div><div class="gmail_extra"><div><div class="gmail_signature" data-smartmail="gmail_signature"><div dir="ltr"><div><div dir="ltr"><div><div dir="ltr"><div dir="ltr"><div dir="ltr"><div dir="ltr"><div dir="ltr"><div dir="ltr"><div dir="ltr"><div dir="ltr"><div dir="ltr"><div dir="ltr"><div dir="ltr"><div dir="ltr"><span lang="EN-GB"><div style="font-family:arial,helvetica,sans-serif"><br></div></span></div></div></div></div></div></div></div></div></div></div></div></div></div></div></div></div></div></div>
<br><div class="gmail_quote">On Mon, Jul 18, 2016 at 12:02 PM, <span dir="ltr"><<a href="mailto:cdi-dev-request@lists.jboss.org" target="_blank">cdi-dev-request@lists.jboss.org</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Send cdi-dev mailing list submissions to<br>
<a href="mailto:cdi-dev@lists.jboss.org">cdi-dev@lists.jboss.org</a><br>
<br>
To subscribe or unsubscribe via the World Wide Web, visit<br>
<a href="https://lists.jboss.org/mailman/listinfo/cdi-dev" rel="noreferrer" target="_blank">https://lists.jboss.org/mailman/listinfo/cdi-dev</a><br>
or, via email, send a message with subject or body 'help' to<br>
<a href="mailto:cdi-dev-request@lists.jboss.org">cdi-dev-request@lists.jboss.org</a><br>
<br>
You can reach the person managing the list at<br>
<a href="mailto:cdi-dev-owner@lists.jboss.org">cdi-dev-owner@lists.jboss.org</a><br>
<br>
When replying, please edit your Subject line so it is more specific<br>
than "Re: Contents of cdi-dev digest..."<br>
<br>
<br>
Today's Topics:<br>
<br>
1. Re: [VOTE] Name the class that can start/stop contexts<br>
(John D. Ament)<br>
2. ManageableContext hierarchy (John D. Ament)<br>
3. Passed: cdi-spec/cdi#22 (2.0-EDR2 - 5b77f45) (Travis CI)<br>
<br>
<br>
----------------------------------------------------------------------<br>
<br>
Message: 1<br>
Date: Fri, 15 Jul 2016 02:13:04 +0000<br>
From: "John D. Ament" <<a href="mailto:john.d.ament@gmail.com">john.d.ament@gmail.com</a>><br>
Subject: Re: [cdi-dev] [VOTE] Name the class that can start/stop<br>
contexts<br>
To: Emily Jiang <<a href="mailto:EMIJIANG@uk.ibm.com">EMIJIANG@uk.ibm.com</a>>, Antoine Sabot-Durand<br>
<<a href="mailto:antoine@sabot-durand.net">antoine@sabot-durand.net</a>><br>
Cc: <a href="mailto:cdi-dev@lists.jboss.org">cdi-dev@lists.jboss.org</a><br>
Message-ID:<br>
<<a href="mailto:CAOqetn_E0u6HCOyb5mm7hv-NRqxBKjwykz7v1YW0ynvYxtZPBw@mail.gmail.com">CAOqetn_E0u6HCOyb5mm7hv-NRqxBKjwykz7v1YW0ynvYxtZPBw@mail.gmail.com</a>><br>
Content-Type: text/plain; charset="utf-8"<br>
<br>
All,<br>
<br>
Thanks for those who voted.<br>
<br>
2 votes for ManageableContext<br>
1 vote for ManagedContext<br>
1 vote for UserManagedContext<br>
<br>
Therefore I'm declaring the winner ManageableContext.<br>
<br>
John<br>
<br>
On Mon, Jul 11, 2016 at 6:23 PM Emily Jiang <<a href="mailto:EMIJIANG@uk.ibm.com">EMIJIANG@uk.ibm.com</a>> wrote:<br>
<br>
> We are trying to find a better name than UnManagedContext.<br>
><br>
> ManagedContext is surely opposite to the option UnManagedContext:o.<br>
><br>
> ManagableContext fits well with AlternableContext. In addition,<br>
> ManagableContext should be managed by others, which is the same as<br>
> UserManagedContext and it is shorter.<br>
><br>
> Hence, +1 for ManagableContext.<br>
><br>
> Many thanks,<br>
> Emily<br>
> ===========================<br>
> Emily Jiang<br>
> WebSphere Application Server, CDI Development Lead<br>
><br>
> MP 211, DE3A20, Winchester, Hampshire, England, SO21 2JN<br>
> Phone: <a href="tel:%2B44%20%280%291962%20816278" value="+441962816278">+44 (0)1962 816278</a> Internal: 246278<br>
><br>
> Email: <a href="mailto:emijiang@uk.ibm.com">emijiang@uk.ibm.com</a><br>
> Lotus Notes: Emily Jiang/UK/IBM@IBMGB<br>
><br>
><br>
><br>
><br>
> From: Antoine Sabot-Durand <<a href="mailto:antoine@sabot-durand.net">antoine@sabot-durand.net</a>><br>
> To: Matej Novotny <<a href="mailto:manovotn@redhat.com">manovotn@redhat.com</a>>, "John D. Ament" <<br>
> <a href="mailto:john.d.ament@gmail.com">john.d.ament@gmail.com</a>>,<br>
> Cc: <a href="mailto:cdi-dev@lists.jboss.org">cdi-dev@lists.jboss.org</a><br>
> Date: 11/07/2016 15:12<br>
> Subject: Re: [cdi-dev] [VOTE] Name the class that can start/stop<br>
> contexts<br>
> Sent by: <a href="mailto:cdi-dev-bounces@lists.jboss.org">cdi-dev-bounces@lists.jboss.org</a><br>
> ------------------------------<br>
><br>
><br>
><br>
> +1 for UserManagedContext, it says clearly that user is in charge of<br>
> managing the context.<br>
> ManageableContext is ok as fallback to me but the fact the the context is<br>
> manageable does not says anything about who has the responsibility to<br>
> manage it.<br>
><br>
><br>
> Le lun. 11 juil. 2016 ? 11:02, Matej Novotny <*<a href="mailto:manovotn@redhat.com">manovotn@redhat.com</a>*<br>
> <<a href="mailto:manovotn@redhat.com">manovotn@redhat.com</a>>> a ?crit :<br>
> +1 for ManageableContext<br>
><br>
> Personally I would still have UnmanagedContext, but since that seems<br>
> ambiguous (as does ManagedContext),<br>
> I chose ManageableContext.<br>
><br>
> Matej<br>
><br>
> ----- Original Message -----<br>
> > From: "John D. Ament" <*<a href="mailto:john.d.ament@gmail.com">john.d.ament@gmail.com</a>* <<a href="mailto:john.d.ament@gmail.com">john.d.ament@gmail.com</a>><br>
> ><br>
> > To: *<a href="mailto:cdi-dev@lists.jboss.org">cdi-dev@lists.jboss.org</a>* <<a href="mailto:cdi-dev@lists.jboss.org">cdi-dev@lists.jboss.org</a>><br>
> > Sent: Monday, July 11, 2016 2:50:23 AM<br>
> > Subject: [cdi-dev] [VOTE] Name the class that can start/stop contexts<br>
> ><br>
> > All,<br>
> ><br>
> > It seems like one of the remaining issues with CDI-30 is the name for the<br>
> > class for the context management. This name isn't permanent, we can<br>
> change<br>
> > after EDR2, but not after final.<br>
> ><br>
> > Here's the proposed renames for "UnmanagedContext":<br>
> ><br>
> > - ManagedContext<br>
> > - ManageableContext<br>
> > - ProgrammaticContext<br>
> > - ExternallyManagedContext<br>
> > - UserManagedContext<br>
> ><br>
> > Please respond back with your vote, I'll leave this open for 3 days ( I<br>
> > believe its Monday morning in central Europe), so I'll close it Thursday<br>
> > morning.<br>
> ><br>
> > Reference:<br>
> ><br>
> *<a href="http://transcripts.jboss.org/meeting/irc.freenode.org/cdi-dev/2016/cdi-dev.2016-07-07-16.03.log.html*" rel="noreferrer" target="_blank">http://transcripts.jboss.org/meeting/irc.freenode.org/cdi-dev/2016/cdi-dev.2016-07-07-16.03.log.html*</a><br>
> <<a href="http://transcripts.jboss.org/meeting/irc.freenode.org/cdi-dev/2016/cdi-dev.2016-07-07-16.03.log.html" rel="noreferrer" target="_blank">http://transcripts.jboss.org/meeting/irc.freenode.org/cdi-dev/2016/cdi-dev.2016-07-07-16.03.log.html</a>><br>
> ><br>
> > - John<br>
> ><br>
> > _______________________________________________<br>
> > cdi-dev mailing list<br>
> > *<a href="mailto:cdi-dev@lists.jboss.org">cdi-dev@lists.jboss.org</a>* <<a href="mailto:cdi-dev@lists.jboss.org">cdi-dev@lists.jboss.org</a>><br>
> > *<a href="https://lists.jboss.org/mailman/listinfo/cdi-dev*" rel="noreferrer" target="_blank">https://lists.jboss.org/mailman/listinfo/cdi-dev*</a><br>
> <<a href="https://lists.jboss.org/mailman/listinfo/cdi-dev" rel="noreferrer" target="_blank">https://lists.jboss.org/mailman/listinfo/cdi-dev</a>><br>
> ><br>
> > Note that for all code provided on this list, the provider licenses the<br>
> code<br>
> > under the Apache License, Version 2<br>
> > (*<a href="http://www.apache.org/licenses/LICENSE-2.0.html*" rel="noreferrer" target="_blank">http://www.apache.org/licenses/LICENSE-2.0.html*</a><br>
> <<a href="http://www.apache.org/licenses/LICENSE-2.0.html" rel="noreferrer" target="_blank">http://www.apache.org/licenses/LICENSE-2.0.html</a>>). For all other ideas<br>
> > provided on this list, the provider waives all patent and other<br>
> intellectual<br>
> > property rights inherent in such information.<br>
> _______________________________________________<br>
> cdi-dev mailing list<br>
> *<a href="mailto:cdi-dev@lists.jboss.org">cdi-dev@lists.jboss.org</a>* <<a href="mailto:cdi-dev@lists.jboss.org">cdi-dev@lists.jboss.org</a>><br>
> *<a href="https://lists.jboss.org/mailman/listinfo/cdi-dev*" rel="noreferrer" target="_blank">https://lists.jboss.org/mailman/listinfo/cdi-dev*</a><br>
> <<a href="https://lists.jboss.org/mailman/listinfo/cdi-dev" rel="noreferrer" target="_blank">https://lists.jboss.org/mailman/listinfo/cdi-dev</a>><br>
><br>
> Note that for all code provided on this list, the provider licenses the<br>
> code under the Apache License, Version 2 (<br>
> *<a href="http://www.apache.org/licenses/LICENSE-2.0.html*" rel="noreferrer" target="_blank">http://www.apache.org/licenses/LICENSE-2.0.html*</a><br>
> <<a href="http://www.apache.org/licenses/LICENSE-2.0.html" rel="noreferrer" target="_blank">http://www.apache.org/licenses/LICENSE-2.0.html</a>>). For all other ideas<br>
> provided on this list, the provider waives all patent and other<br>
> intellectual property rights inherent in such information.<br>
> _______________________________________________<br>
> cdi-dev mailing list<br>
> <a href="mailto:cdi-dev@lists.jboss.org">cdi-dev@lists.jboss.org</a><br>
> <a href="https://lists.jboss.org/mailman/listinfo/cdi-dev" rel="noreferrer" target="_blank">https://lists.jboss.org/mailman/listinfo/cdi-dev</a><br>
><br>
> Note that for all code provided on this list, the provider licenses the<br>
> code under the Apache License, Version 2 (<br>
> <a href="http://www.apache.org/licenses/LICENSE-2.0.html" rel="noreferrer" target="_blank">http://www.apache.org/licenses/LICENSE-2.0.html</a>). For all other ideas<br>
> provided on this list, the provider waives all patent and other<br>
> intellectual property rights inherent in such information.<br>
><br>
> Unless stated otherwise above:<br>
> IBM United Kingdom Limited - Registered in England and Wales with number<br>
> 741598.<br>
> Registered office: PO Box 41, North Harbour, Portsmouth, Hampshire PO6 3AU<br>
><br>
-------------- next part --------------<br>
An HTML attachment was scrubbed...<br>
URL: <a href="http://lists.jboss.org/pipermail/cdi-dev/attachments/20160715/7cfdde8c/attachment-0001.html" rel="noreferrer" target="_blank">http://lists.jboss.org/pipermail/cdi-dev/attachments/20160715/7cfdde8c/attachment-0001.html</a><br>
<br>
------------------------------<br>
<br>
Message: 2<br>
Date: Fri, 15 Jul 2016 22:38:46 +0000<br>
From: "John D. Ament" <<a href="mailto:john.d.ament@gmail.com">john.d.ament@gmail.com</a>><br>
Subject: [cdi-dev] ManageableContext hierarchy<br>
To: "<a href="mailto:cdi-dev@lists.jboss.org">cdi-dev@lists.jboss.org</a>" <<a href="mailto:cdi-dev@lists.jboss.org">cdi-dev@lists.jboss.org</a>><br>
Message-ID:<br>
<CAOqetn-mmfuWWTtgKiiMbV=WP36gKLM2=Pivr7Vb2v=<a href="mailto:UyFm2Ng@mail.gmail.com">UyFm2Ng@mail.gmail.com</a>><br>
Content-Type: text/plain; charset="utf-8"<br>
<br>
All,<br>
<br>
One of the items from our last conversation was to remove the hierarchy<br>
changes for ManageableContext.<br>
<br>
I'd like to propose that we re-evaluate the hierarchy post EDR2, to avoid<br>
too many changes. This is related to CDI-30.<br>
<br>
If agreed, I can create a follow up ticket.<br>
<br>
John<br>
-------------- next part --------------<br>
An HTML attachment was scrubbed...<br>
URL: <a href="http://lists.jboss.org/pipermail/cdi-dev/attachments/20160715/8967178a/attachment-0001.html" rel="noreferrer" target="_blank">http://lists.jboss.org/pipermail/cdi-dev/attachments/20160715/8967178a/attachment-0001.html</a><br>
<br>
------------------------------<br>
<br>
Message: 3<br>
Date: Mon, 18 Jul 2016 09:59:20 +0000<br>
From: Travis CI <<a href="mailto:builds@travis-ci.org">builds@travis-ci.org</a>><br>
Subject: [cdi-dev] Passed: cdi-spec/cdi#22 (2.0-EDR2 - 5b77f45)<br>
To: <<a href="mailto:cdi-dev@lists.jboss.org">cdi-dev@lists.jboss.org</a>><br>
Message-ID:<br>
<578ca878916ce_33f98a949d7bc8168af@17287723-a229-46ff-8c0f-465f15696c07.mail><br>
<br>
Content-Type: text/plain; charset="utf-8"<br>
<br>
Build Update for cdi-spec/cdi<br>
-------------------------------------<br>
<br>
Build: #22<br>
Status: Passed<br>
<br>
Duration: 8 minutes and 30 seconds<br>
Commit: 5b77f45 (2.0-EDR2)<br>
Author: Antoine Sabot-Durand<br>
Message: Adding travis CI config<br>
<br>
View the changeset: <a href="https://github.com/cdi-spec/cdi/compare/19a471aa497f...5b77f45d99d5" rel="noreferrer" target="_blank">https://github.com/cdi-spec/cdi/compare/19a471aa497f...5b77f45d99d5</a><br>
<br>
View the full build log and details: <a href="https://travis-ci.org/cdi-spec/cdi/builds/145494191" rel="noreferrer" target="_blank">https://travis-ci.org/cdi-spec/cdi/builds/145494191</a><br>
<br>
--<br>
<br>
You can configure recipients for build notifications in your .travis.yml file. See <a href="https://docs.travis-ci.com/user/notifications" rel="noreferrer" target="_blank">https://docs.travis-ci.com/user/notifications</a><br>
<br>
-------------- next part --------------<br>
An HTML attachment was scrubbed...<br>
URL: <a href="http://lists.jboss.org/pipermail/cdi-dev/attachments/20160718/f2041438/attachment.html" rel="noreferrer" target="_blank">http://lists.jboss.org/pipermail/cdi-dev/attachments/20160718/f2041438/attachment.html</a><br>
<br>
------------------------------<br>
<br>
_______________________________________________<br>
cdi-dev mailing list<br>
<a href="mailto:cdi-dev@lists.jboss.org">cdi-dev@lists.jboss.org</a><br>
<a href="https://lists.jboss.org/mailman/listinfo/cdi-dev" rel="noreferrer" target="_blank">https://lists.jboss.org/mailman/listinfo/cdi-dev</a><br>
<br>
Note that for all code provided on this list, the provider licenses the code under the Apache License, Version 2 (<a href="http://www.apache.org/licenses/LICENSE-2.0.html" rel="noreferrer" target="_blank">http://www.apache.org/licenses/LICENSE-2.0.html</a>). For all other ideas provided on this list, the provider waives all patent and other intellectual property rights inherent in such information.<br>
<br>
End of cdi-dev Digest, Vol 68, Issue 8<br>
**************************************<br>
</blockquote></div><br></div></div></div></div></div>