[cdi-dev] Project renaming

Markus KARG markus at headcrashing.eu
Tue Sep 10 13:26:42 EDT 2019


Just to be clear: The reason told is slightly wrong. There is no *need* to
rename CDI, it is just *wanted* by the EF. Anything named "X for Java" is
officially allowed to be used without explicit contract with Oracle, as told
by the publicly visible trademark documents lays out:
https://www.oracle.com/legal/trademarks.html.
-Markus

-----Ursprüngliche Nachricht-----
Von: cdi-dev-bounces at lists.jboss.org
[mailto:cdi-dev-bounces at lists.jboss.org] Im Auftrag von Mark Struberg
Gesendet: Dienstag, 10. September 2019 18:45
An: cdi-dev
Betreff: Re: [cdi-dev] Project renaming

I don't care much about a rename as long as the abreviation (CDI) is still
used.

LieGrue,
strub


> Am 02.09.2019 um 17:35 schrieb Kito Mann <kito-public at virtua.com>:
> 
> +1
> 
> On Fri, May 17, 2019 at 2:16 AM Reza Rahman <reza_rahman at lycos.com> wrote:
> Jakarta Contexts and Dependency Injection seems like a good name to me.
> 
> On 5/17/2019 10:29 AM, Scott Stark wrote:
>> One thing that needs to happen for each Jakarta EE project is a renaming
to avoid the Oracle trademarked names and acronyms. The means that Contexts
and Dependency Injection for Java needs to change to avoid the use of Java.
The current proposed name from the steering committee is Jakarta Contexts
and Dependency Injection.
>> 
>> The projects should have been asked by the PMC what their preferred
rename is, but I have not seen anything back from the CDI dev group. I had
asked this question a while back but it appears to be have bounced due to
not being subscribed, so I wanted to raise this question again.
>> 
>> Are there other preferences this project would like the steering and
specification committees to entertain?
>> 
>> 
>> 
>> _______________________________________________
>> 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.
> _______________________________________________
> 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.
> _______________________________________________
> 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.


_______________________________________________
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.




More information about the cdi-dev mailing list