[VOTE] Name the class that can start/stop contexts

classic Classic list List threaded Threaded
7 messages Options
Reply | Threaded
Open this post in threaded view
|

[VOTE] Name the class that can start/stop contexts

John D. Ament
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.


- John

_______________________________________________
cdi-dev mailing list
[hidden email]
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.
Reply | Threaded
Open this post in threaded view
|

Re: [VOTE] Name the class that can start/stop contexts

Matej Novotny
+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" <[hidden email]>
> To: [hidden email]
> 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-dev.2016-07-07-16.03.log.html
>
> - John
>
> _______________________________________________
> cdi-dev mailing list
> [hidden email]
> 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
[hidden email]
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.
Reply | Threaded
Open this post in threaded view
|

Re: [VOTE] Name the class that can start/stop contexts

Antoine Sabot-Durand
Administrator
+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 <[hidden email]> 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" <[hidden email]>
> To: [hidden email]
> 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-dev.2016-07-07-16.03.log.html
>
> - John
>
> _______________________________________________
> cdi-dev mailing list
> [hidden email]
> 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
[hidden email]
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
[hidden email]
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.
Reply | Threaded
Open this post in threaded view
|

Re: [VOTE] Name the class that can start/stop contexts

Stephan Knitelius
In reply to this post by Matej Novotny
+1 ManagedContext

On Mon, 11 Jul 2016 at 11:02 Matej Novotny <[hidden email]> wrote:
+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" <[hidden email]>
> To: [hidden email]
> 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-dev.2016-07-07-16.03.log.html
>
> - John
>
> _______________________________________________
> cdi-dev mailing list
> [hidden email]
> 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
[hidden email]
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
[hidden email]
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.
Reply | Threaded
Open this post in threaded view
|

Re: [VOTE] Name the class that can start/stop contexts

Emily Jiang
In reply to this post by Antoine Sabot-Durand
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: [hidden email]
Lotus Notes: Emily Jiang/UK/IBM@IBMGB




From:        Antoine Sabot-Durand <[hidden email]>
To:        Matej Novotny <[hidden email]>, "John D. Ament" <[hidden email]>,
Cc:        [hidden email]
Date:        11/07/2016 15:12
Subject:        Re: [cdi-dev] [VOTE] Name the class that can start/stop contexts
Sent by:        [hidden email]




+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 é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@...>
> To:
[hidden email]
> 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-dev.2016-07-07-16.03.log.html
>
> - John
>
> _______________________________________________
> cdi-dev mailing list
>
[hidden email]
>
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

[hidden email]
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
[hidden email]
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

_______________________________________________
cdi-dev mailing list
[hidden email]
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.
Reply | Threaded
Open this post in threaded view
|

Re: [VOTE] Name the class that can start/stop contexts

John D. Ament
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 <[hidden email]> 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: [hidden email]
Lotus Notes: Emily Jiang/UK/IBM@IBMGB




From:        Antoine Sabot-Durand <[hidden email]>
To:        Matej Novotny <[hidden email]>, "John D. Ament" <[hidden email]>,
Cc:        [hidden email]
Date:        11/07/2016 15:12
Subject:        Re: [cdi-dev] [VOTE] Name the class that can start/stop contexts
Sent by:        [hidden email]




+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 <[hidden email]> 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" <
[hidden email]>
> To:
[hidden email]
> 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-dev.2016-07-07-16.03.log.html
>
> - John
>
> _______________________________________________
> cdi-dev mailing list
>
[hidden email]
>
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

[hidden email]
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
[hidden email]
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

_______________________________________________
cdi-dev mailing list
[hidden email]
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.
Reply | Threaded
Open this post in threaded view
|

Re: [VOTE] Name the class that can start/stop contexts

Werner Keil-2
In reply to this post by John D. Ament
Seems the vote got swamped among many other messages both here and in my mailbox;-O

The arguments leading towards the winning name sound good and logical, so that would be my vote, too.

Werner


On Mon, Jul 18, 2016 at 12:02 PM, <[hidden email]> wrote:
Send cdi-dev mailing list submissions to
        [hidden email]

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
        [hidden email]

You can reach the person managing the list at
        [hidden email]

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" <[hidden email]>
Subject: Re: [cdi-dev] [VOTE] Name the class that can start/stop
        contexts
To: Emily Jiang <[hidden email]>,  Antoine Sabot-Durand
        <[hidden email]>
Cc: [hidden email]
Message-ID:
        <[hidden email]>
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 <[hidden email]> 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:  <a href="tel:%2B44%20%280%291962%20816278" value="+441962816278">+44 (0)1962 816278  Internal: 246278
>
> Email: [hidden email]
> Lotus Notes: Emily Jiang/UK/IBM@IBMGB
>
>
>
>
> From:        Antoine Sabot-Durand <[hidden email]>
> To:        Matej Novotny <[hidden email]>, "John D. Ament" <
> [hidden email]>,
> Cc:        [hidden email]
> Date:        11/07/2016 15:12
> Subject:        Re: [cdi-dev] [VOTE] Name the class that can start/stop
> contexts
> Sent by:        [hidden email]
> ------------------------------
>
>
>
> +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 <*[hidden email]*
> <[hidden email]>> 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" <*[hidden email]* <[hidden email]>
> >
> > To: *[hidden email]* <[hidden email]>
> > 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-dev.2016-07-07-16.03.log.html*
> <http://transcripts.jboss.org/meeting/irc.freenode.org/cdi-dev/2016/cdi-dev.2016-07-07-16.03.log.html>
> >
> > - John
> >
> > _______________________________________________
> > cdi-dev mailing list
> > *[hidden email]* <[hidden email]>
> > *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
> *[hidden email]* <[hidden email]>
> *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
> [hidden email]
> 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/attachment-0001.html

------------------------------

Message: 2
Date: Fri, 15 Jul 2016 22:38:46 +0000
From: "John D. Ament" <[hidden email]>
Subject: [cdi-dev] ManageableContext hierarchy
To: "[hidden email]" <[hidden email]>
Message-ID:
        <CAOqetn-mmfuWWTtgKiiMbV=WP36gKLM2=Pivr7Vb2v=[hidden email]>
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/attachment-0001.html

------------------------------

Message: 3
Date: Mon, 18 Jul 2016 09:59:20 +0000
From: Travis CI <[hidden email]>
Subject: [cdi-dev] Passed: cdi-spec/cdi#22 (2.0-EDR2 - 5b77f45)
To: <[hidden email]>
Message-ID:
        <[hidden email]>

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/attachment.html

------------------------------

_______________________________________________
cdi-dev mailing list
[hidden email]
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
**************************************


_______________________________________________
cdi-dev mailing list
[hidden email]
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.