From dev-return-100108-archive-asf-public=cust-asf.ponee.io@geronimo.apache.org Sat May 4 19:36:10 2019 Return-Path: X-Original-To: archive-asf-public@cust-asf.ponee.io Delivered-To: archive-asf-public@cust-asf.ponee.io Received: from mail.apache.org (hermes.apache.org [207.244.88.153]) by mx-eu-01.ponee.io (Postfix) with SMTP id B0B3D180621 for ; Sat, 4 May 2019 21:36:09 +0200 (CEST) Received: (qmail 96283 invoked by uid 500); 4 May 2019 19:36:08 -0000 Mailing-List: contact dev-help@geronimo.apache.org; run by ezmlm Precedence: bulk list-help: list-unsubscribe: List-Post: Reply-To: dev@geronimo.apache.org List-Id: Delivered-To: mailing list dev@geronimo.apache.org Received: (qmail 96273 invoked by uid 99); 4 May 2019 19:36:08 -0000 Received: from pnap-us-west-generic-nat.apache.org (HELO spamd4-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Sat, 04 May 2019 19:36:08 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd4-us-west.apache.org (ASF Mail Server at spamd4-us-west.apache.org) with ESMTP id BD889C3763 for ; Sat, 4 May 2019 19:36:07 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd4-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: 1.802 X-Spam-Level: * X-Spam-Status: No, score=1.802 tagged_above=-999 required=6.31 tests=[DKIM_SIGNED=0.1, DKIM_VALID=-0.1, DKIM_VALID_AU=-0.1, DKIM_VALID_EF=-0.1, HTML_MESSAGE=2, RCVD_IN_DNSWL_NONE=-0.0001, RCVD_IN_MSPIKE_H3=0.001, RCVD_IN_MSPIKE_WL=0.001, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=disabled Authentication-Results: spamd4-us-west.apache.org (amavisd-new); dkim=pass (2048-bit key) header.d=gmail.com Received: from mx1-lw-eu.apache.org ([10.40.0.8]) by localhost (spamd4-us-west.apache.org [10.40.0.11]) (amavisd-new, port 10024) with ESMTP id 0lab6O87TKeS for ; Sat, 4 May 2019 19:36:05 +0000 (UTC) Received: from mail-qt1-f193.google.com (mail-qt1-f193.google.com [209.85.160.193]) by mx1-lw-eu.apache.org (ASF Mail Server at mx1-lw-eu.apache.org) with ESMTPS id 23E5F5F4D4 for ; Sat, 4 May 2019 19:36:04 +0000 (UTC) Received: by mail-qt1-f193.google.com with SMTP id c35so10564968qtk.3 for ; Sat, 04 May 2019 12:36:04 -0700 (PDT) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:references:in-reply-to:from:date:message-id:subject:to; bh=jXofDpzAn+LzHV3ujDPZHjiVV3vkp76LI1bzkQ8xwBY=; b=MjRY48C+ck1g7j2zsd524ia6WdBLrNRCQdr1Gc1Ns9+GDwZDzY4sgeh08YiLqxWcsp TO68lq4m0x+eVfI/k8HRjBfWJjtP/N1hH6gT2DyhjkhToQJ9gazP454tjl3RjWtgAe5N /VD9OaEFdNHUZEDpGvHesbEvsTaPOh7PZ2uzOmjYojAfk0nA5t/gndSI39tTjHvhJhvd Vw4CiExU8NsJa8XUKjvPPQUM3K+LL+AipJnLNceJo/I+WDkB508z6QW9szp5irqoQKKg /UYbzD999aQoAdSkp2f/8Ktp1JIU8ezntpaQ1uKCtTNI96teyYBCGDpiXm/yEmleH7DQ vRvw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:references:in-reply-to:from:date :message-id:subject:to; bh=jXofDpzAn+LzHV3ujDPZHjiVV3vkp76LI1bzkQ8xwBY=; b=UoZWDvYKjKibx+rt6h2UpjmWPG9zK4CA3DaLaH7QnFbc3Vjour9gXcyacVSKuIH4ui olLOIPTNJktDlkyqfK57APAPgJ3FltB1MdmDeu4z/H+ihtMJ2jdqA1WwLkv6q758xSkB 6iNfKnWXi1b7K5CrO5EGxTz+B2mkqz+3Uf+3D4JoqFE4wvQXobYeGIsyHVex7igeXaeS b9yWJdiRyAbazWyeQWdm092p33/lWhQ3rxzupDcb5UUtw7a7MZSYhFWcjA9cw7Z4prx4 luMiy+yzdsZJD34m401CM70GLAye3Du/cCnxovjyxb91ztLV5aN7vHsFH/C3mPj2W+Zf U7uQ== X-Gm-Message-State: APjAAAXV614XWwZXcYwdYVxlvb7Lu4k7eY8s2QX2TlRP+90aKTS97U6Z zS4OSGfpiGGt+9Rmjqf1FNykR8w+Qgn7wC+rCsJFFdXI X-Google-Smtp-Source: APXvYqwnP/T5iRstmHdWZIyRRhdChLHzqz5Zow/Pwh27XEdT1s/s+4KAV7S6mEg7Vyjif7LaoV6QhNRJw+2CcsLsF2k= X-Received: by 2002:aed:258a:: with SMTP id x10mr14534847qtc.380.1556998563460; Sat, 04 May 2019 12:36:03 -0700 (PDT) MIME-Version: 1.0 References: <89C25331-028B-4C1E-84C7-60741C515953@yahoo.de> <9EAABA10-ECB6-4053-B7FD-8C901D9E3553@yahoo.de> In-Reply-To: From: Romain Manni-Bucau Date: Sat, 4 May 2019 21:35:51 +0200 Message-ID: Subject: Re: [DISCUSS] implement jakarta spec apis To: dev@geronimo.apache.org Content-Type: multipart/alternative; boundary="0000000000004a7ade058814fad4" --0000000000004a7ade058814fad4 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable AFAIK we dont have limitations there and can do share stuff outside with jgit - but it is very rare - so probably sane to unify all repo to git. In particular since we will not do all specs probably. Cxf already moved to jakarta spec so we dont need jaxrs stack for instance, same for cdi, bval,... So we wil reduce a lot what we fork IMHO. Le sam. 4 mai 2019 =C3=A0 21:12, Mark Struberg a =C3=A9= crit : > I=E2=80=99d keep that in svn because of the tons of modules. > > Lg, > Strub > > Am 04.05.2019 um 19:28 schrieb Romain Manni-Bucau = : > > We mainly fork for legal reasons and defaults so name is probably not > critical while we respect module names. > > Btw do we do it in gitbox? Svn had some limitations by the past for > contributions. > > Le sam. 4 mai 2019 =C3=A0 17:47, Raymond Auge = a > =C3=A9crit : > >> One thing to consider is there may be cases where it is desirable to >> retain the javax API alongside some extra jakarta packages & types. >> >> For example, for JAX-RS you may wish to add some newly defined jakarta >> types (part of a new spec) which interact over the original javax API. >> >> The result might be that "Jakarta EE REST" (a fictitious name for next >> JAX-RS) might contain a subset of packages which, in combination with JA= XRS >> v2.1, also qualifies as "Jakarata EE Rest". >> >> - Ray >> >> On Sat, May 4, 2019 at 11:26 AM Raymond Auge >> wrote: >> >>> so is this a matter of forking all the current specs into the new >>> namespace? Or is the intention to completely change the packages in-pla= ce? >>> >>> - Ray >>> >>> On Fri, May 3, 2019 at 1:58 PM Romain Manni-Bucau >>> wrote: >>> >>>> Hmm >>>> >>>> My understanding was it was getting under eclipse license as well and >>>> was fully donated but can have missed some details. >>>> >>>> If we cant reuse them let's just create new ones and fix module name >>>> for others. >>>> >>>> specs/ is fine since it is the same for us IMHO >>>> >>>> Le ven. 3 mai 2019 =C3=A0 18:24, Mark Struberg a = =C3=A9crit : >>>> >>>>> No, it is not the same. microprofile specs are licensed under ALv2 an= d >>>>> we know all the legal details. >>>>> For the EE specs this is by far not the same. We don't even know >>>>> exactly what parts did yet get donated by Oracle to the EF. >>>>> >>>>> LieGrue, >>>>> strub >>>>> >>>>> >>>>> > Am 03.05.2019 um 18:12 schrieb Romain Manni-Bucau < >>>>> rmannibucau@gmail.com>: >>>>> > >>>>> > Hi >>>>> > >>>>> > Idnt it the exact same as for microprofile? So we dont do? >>>>> > >>>>> > Le ven. 3 mai 2019 =C3=A0 16:21, Mark Struberg = a >>>>> =C3=A9crit : >>>>> > I've started tinkering something under specs/branches/jakarta. >>>>> > It's wip but have to rush out for a few hours now. >>>>> > Will continue later today. >>>>> > >>>>> > LieGrue, >>>>> > strub >>>>> > >>>>> > >>>>> > > Am 03.05.2019 um 15:50 schrieb Mark Struberg : >>>>> > > >>>>> > > hi folks! >>>>> > > >>>>> > > You might have read todays post from Mike Milinkovich. >>>>> > > >>>>> > > >>>>> https://eclipse-foundation.blog/2019/05/03/jakarta-ee-java-trademarks= / >>>>> > > >>>>> > > It basically says that Jakarta will not be able to change a singl= e >>>>> bit in the current spec apis under the javax.* package. >>>>> > > Any change has to be done in a different package. >>>>> > > The Jakarta people over at Eclipse already did some voting and th= e >>>>> new package name will be jakarta.* >>>>> > > >>>>> > > Thus I would like to recommend to use our IP clean geronimo-specs >>>>> to setup a new project for the EE8 specs under the jakarta.* package = name. >>>>> > > >>>>> > > I'll go forward and create a branch starting with the most >>>>> important specs. >>>>> > > >>>>> > > Any feedback and help is welcome! >>>>> > > >>>>> > > LieGrue, >>>>> > > strub >>>>> > > >>>>> > >>>>> >>>>> >>> >>> -- >>> *Raymond Aug=C3=A9* >>> (@rotty3000) >>> Senior Software Architect *Liferay, Inc.* >>> (@Liferay) >>> Board Member & EEG Co-Chair, OSGi Alliance >>> (@OSGiAlliance) >>> >> >> >> -- >> *Raymond Aug=C3=A9* >> (@rotty3000) >> Senior Software Architect *Liferay, Inc.* >> (@Liferay) >> Board Member & EEG Co-Chair, OSGi Alliance >> (@OSGiAlliance) >> > --0000000000004a7ade058814fad4 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
AFAIK we dont have limitations there and can do shar= e stuff outside with jgit - but it is very rare - so probably sane to unify= all repo to git. In particular since we will not do all specs probably. Cx= f already moved to jakarta spec so we dont need jaxrs stack for instance, s= ame for cdi, bval,... So we wil reduce a lot what we fork IMHO.

Le= sam. 4 mai 2019 =C3=A0 21:12, Mark Struberg <struberg@yahoo.de> a =C3=A9crit=C2=A0:
I=E2=80=99d keep that in svn because of the tons of modules.

Lg,
Strub

Am 04.05.2019 um 19:28 schrieb Romain Manni-Bucau &l= t;rmannibucau@gmail.com>:

=
We mainly fork for legal reasons and def= aults so name is probably not critical while we respect module names.

Btw do we do it in gitbox? Svn had = some limitations by the past for contributions.

Le sam. 4 mai 2019 =C3=A0 17:47, Raymond = Auge <raymond.auge@liferay.com> a =C3=A9crit=C2=A0:
One thing to consid= er is there may be cases where it is desirable to retain the javax API alon= gside some extra jakarta packages & types.

For= example, for JAX-RS you may wish to add some newly defined jakarta types (= part of a new spec) which interact over the original javax API.
<= br>
The result might be that "Jakarta EE REST" (a ficti= tious name for next JAX-RS) might contain a subset of packages which, in co= mbination with JAXRS v2.1, also qualifies as "Jakarata EE Rest".<= /div>

- Ray

On Sat, May 4, 2019 at 11:26 AM Ra= ymond Auge <raymond.auge@liferay.com> wrote:
=
so is this a matter of forking all the current specs into the new namesp= ace? Or is the intention to completely change the packages in-place?
<= div>
- Ray

On Fri, May 3, 2019 at 1:58 PM Romain Man= ni-Bucau <rmannibucau@gmail.com> wrote:
Hmm

My understanding was it was getting= under eclipse license as well and was fully donated but can have missed so= me details.

If we cant r= euse them let's just create new ones and fix module name for others.

specs/ is fine since it is= the same for us IMHO

Le ven. 3 mai 2019 =C3=A0 18:24, Mark Struberg <struberg= @yahoo.de> a =C3=A9crit=C2=A0:
No, it is not the same. microprofile specs are licens= ed under ALv2 and we know all the legal details.
For the EE specs this is by far not the same. We don't even know exactl= y what parts did yet get donated by Oracle to the EF.

LieGrue,
strub


> Am 03.05.2019 um 18:12 schrieb Romain Manni-Bucau <rmannibucau@gmail.com>:
>
> Hi
>
> Idnt it the exact same as for microprofile? So we dont do?
>
> Le ven. 3 mai 2019 =C3=A0 16:21, Mark Struberg <struberg@yahoo.de> a =C3=A9crit :
> I've started tinkering something under specs/branches/jakarta.
> It's wip but have to rush out for a few hours now.
> Will continue later today.
>
> LieGrue,
> strub
>
>
> > Am 03.05.2019 um 15:50 schrieb Mark Struberg <struberg@yahoo.de>:
> >
> > hi folks!
> >
> > You might have read todays post from Mike Milinkovich.
> >
> > https://eclipse-foundation.blog/2019/05/03/jakarta-ee-java-tra= demarks/
> >
> > It basically says that Jakarta will not be able to change a singl= e bit in the current spec apis under the javax.* package.
> > Any change has to be done in a different package.
> > The Jakarta people over at Eclipse already did some voting and th= e new package name will be jakarta.*
> >
> > Thus I would like to recommend to use our IP clean geronimo-specs= to setup a new project for the EE8 specs under the jakarta.* package name.=
> >
> > I'll go forward and create a branch starting with the most im= portant specs.
> >
> > Any feedback and help is welcome!
> >
> > LieGrue,
> > strub
> >
>



--
R= aymond Aug=C3=A9=C2=A0(@rotty3000)
Senior Software Architect=C2=A0Lif= eray, Inc.=C2=A0(@Liferay)
Board Member & EEG Co-Chair, OSGi A= lliance (@OSGiAlliance)


--
--0000000000004a7ade058814fad4--