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