From dev-return-100119-archive-asf-public=cust-asf.ponee.io@geronimo.apache.org Sun May 5 17:44:12 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 99AF018066B for ; Sun, 5 May 2019 19:44:11 +0200 (CEST) Received: (qmail 47811 invoked by uid 500); 5 May 2019 17:44:10 -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 47797 invoked by uid 99); 5 May 2019 17:44:09 -0000 Received: from pnap-us-west-generic-nat.apache.org (HELO spamd1-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Sun, 05 May 2019 17:44:09 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd1-us-west.apache.org (ASF Mail Server at spamd1-us-west.apache.org) with ESMTP id 048BBC251B for ; Sun, 5 May 2019 17:44:09 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd1-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: 1.78 X-Spam-Level: * X-Spam-Status: No, score=1.78 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.01, RCVD_IN_MSPIKE_WL=-0.01, SPF_PASS=-0.001, URIBL_BLOCKED=0.001] autolearn=disabled Authentication-Results: spamd1-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 (spamd1-us-west.apache.org [10.40.0.7]) (amavisd-new, port 10024) with ESMTP id S8ZXXvKF9dXz for ; Sun, 5 May 2019 17:44:06 +0000 (UTC) Received: from mail-qt1-f196.google.com (mail-qt1-f196.google.com [209.85.160.196]) by mx1-lw-eu.apache.org (ASF Mail Server at mx1-lw-eu.apache.org) with ESMTPS id ACA5160CF8 for ; Sun, 5 May 2019 17:36:05 +0000 (UTC) Received: by mail-qt1-f196.google.com with SMTP id f24so1849869qtk.11 for ; Sun, 05 May 2019 10:36:05 -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=8PEbaJiMs63jLxJ0OVacJQcNlNsY4weOgmE1D/n5u5U=; b=mBALzo0hemSsC9AMV6a38tzWqt4BjIaBwcF0Bco0oRyBwBxAiiaw2z07HwO1X18PS2 qqLLmVY53DVGDMW/Q/YsFLZzAlLg9JiyFQK18cp3lzjVH5YRPTxEtmS2/zPUQrgJTU43 HeFWrDCLGOj+fre6CF6jKVuj+ZOcQIS0C3bgN2vvWcQoZLW8JBhjTM2DgxlzthOYk4XS VeDPt3IltYFv89+mpys4Duf3zoYhj6lxJp4w30GwsDjv9k6y1T+A8tOH2qcDPw+9yTC2 P0HVueNtsl+OewbYAaEpRFmrmad8UELeF8xffSfS/tNFa1S0enITSKZJyBTMvEH3+S4a JAdQ== 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=8PEbaJiMs63jLxJ0OVacJQcNlNsY4weOgmE1D/n5u5U=; b=c9e7E9fiIqXo48L+SZLxPz89cVmtjuTJwfSiyaVH4NO80tMOBlDkVOxZV9IdJdljwY IBpiixQo2EGwypCcj6l8f5fF/+pOrImFRe3/VmrUA/GARs52V/bjtAbLQUk7z9l2qdzJ HdktPdvBVJFvRn8Gks6wkQwoJYJtC8aCeNUSU039Qid1MicEyS4i2fObl8XodyR30qfD TyqicpffWmv8ddulYlH9RH1P2VZ2VW/zH5CSz7PnOYKVfu6jvGvNvs1zFQmlsJL+Yj8R COiyJUXoEZyFnDOYKjeXICMblFtcm3wJ/wnBfJyUj72E4kNR4tNa6N5MKQz60e1l7ezh IIGA== X-Gm-Message-State: APjAAAVGkMagoU2OWSXq9Lc1iIlBjWVCltNjz5g6s5EIXGtCkdwIMFGh O8IE6kl8OFsQmi6ZP1hKeb4wLvaq5YNbPEJHRkFFxLc8 X-Google-Smtp-Source: APXvYqx5eyX8BKmTAVj3+Rwew7P/Ly8e82xiM0FHImGY/QlWA4AUx3KDLpx4JMCyfaHUkPTTdFl9na7UFopHQhBo2HY= X-Received: by 2002:a0c:8b69:: with SMTP id d41mr17996663qvc.186.1557077764173; Sun, 05 May 2019 10:36:04 -0700 (PDT) MIME-Version: 1.0 References: <89C25331-028B-4C1E-84C7-60741C515953@yahoo.de> <9EAABA10-ECB6-4053-B7FD-8C901D9E3553@yahoo.de> <68371188-8355-4E6C-A63D-F791044ACDA5@yahoo.de> <9904D65B-AA35-4037-95C3-3CDF83F18F98@yahoo.de> <9E67C623-78BE-4FE8-9FD7-D0BE2CF7C608@yahoo.de> <9EEF5150-758D-4F61-B586-78229BFC4BB3@yahoo.de> In-Reply-To: From: Romain Manni-Bucau Date: Sun, 5 May 2019 19:35:51 +0200 Message-ID: Subject: Re: [DISCUSS] implement jakarta spec apis To: dev@geronimo.apache.org Content-Type: multipart/alternative; boundary="0000000000000576270588276bf3" --0000000000000576270588276bf3 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Ok. Can we agree to take this discussion back and hold any release - no issue with snaps - until it is clarified? Le dim. 5 mai 2019 =C3=A0 18:45, Mark Struberg a =C3=A9= crit : > I'm not even sure whether they yet got all the necessary IP to release > anything. > > LieGrue, > strub > > > > Am 05.05.2019 um 18:39 schrieb Romain Manni-Bucau >: > > > > > > > > Le dim. 5 mai 2019 =C3=A0 18:30, Mark Struberg a = =C3=A9crit : > > I'm not mandating jakarta in the groupId, but it should something else > than the current one. > > Because otw we would have them completely mixed up in the same folder. > That's not nice. > > > > Depends, that said happy to just replace specs by jakarta if it works > for you better (org.apache.geronimo.jakarta). I just dont want > jakarta-specs or _spec-xxx as before, always looked fishy and almost wron= g > even if I get where it comes from. > > > > Btw, what is our status on having eclipse releasing api under asf2 > license? > > > > I dont want us to invest in something we drop like in 2 weeks and sound= s > it can be for most of specs. Any page tracking that? > > > > > > LieGrue > > strub > > > > > Am 05.05.2019 um 18:20 schrieb Romain Manni-Bucau < > rmannibucau@gmail.com>: > > > > > > We dont need jakarta in the gav at all. > > > > > > Why not org.apache.geronimo.spec:servlet:4.0.1? > > > > > > As a reminder specs means jakarta already and there id jo ambiguity > between jakarta and javaee thanks the version. > > > > > > That said if we move to git it id even physically clearer. > > > > > > Finally servlet is a bad example cause owned at tomcat for apache i > think. We should absolutely stop duplicating them, it pollutes user land > for no gain IMHO. > > > > > > > > > > > > > > > Le dim. 5 mai 2019 =C3=A0 16:28, Mark Struberg a = =C3=A9crit > : > > > Eclipse itself probably doesn't yet have all the IP themselves. This > first needs to be clarified. Since all those legal questions have been > dealt with behind closed doors we simply have no idea. > > > > > > But we do have clean-room implemented APIs under ALv2 over here at > Geronimo. > > > And we can move this ourselves without having to wait for anybody. > > > > > > LieGrue, > > > strub > > > > > > > > > > Am 05.05.2019 um 16:12 schrieb Bernd Eckenfels < > ecki@zusammenkunft.net>: > > > > > > > > I wonder if you need that going forward for Jakarta Specs, they > could just be distributed by Eclipse directly? Having said that, if this = is > not the case I would at least remove =E2=80=9Egeronimo-=E2=80=9C from the= artifact Id? > > > > > > > > > > > > -- > > > > http://bernd.eckenfels.net > > > > > > > > Von: Mark Struberg > > > > Gesendet: Sonntag, Mai 5, 2019 4:09 PM > > > > An: geronimo-dev > > > > Betreff: Re: [DISCUSS] implement jakarta spec apis > > > > > > > > For now I've used the following patterns: > > > > > > > > org.apache.geronimo.jakarta-specs > > > > because specs and jakarta-specs should be in a clearly separated > folder. > > > > > > > > geronimo-jakarta-servlet_spec > > > > because 'jakarta' should be in the jar name > > > > > > > > 4.0_1-SNAPSHOT > > > > 4.0 is for servlet-4.0, 1 is the patch level. > > > > > > > > I'd NOT do a release or push to our snapshots repo until in about 2 > weeks when the modus operandi is clear within the Jakarta community. > > > > > > > > LieGrue, > > > > strub > > > > > > > > > > > > > > > > > Am 05.05.2019 um 08:55 schrieb Romain Manni-Bucau < > rmannibucau@gmail.com>: > > > > > > > > > > Do we also want to clean our gav? Artifact=3Dspec, major.minor > version =3Dspec version > > > > > > > > > > Ex: org.apache.geronimo.specs:jsp:2.1.1 > > > > > > > > > > Le sam. 4 mai 2019 =C3=A0 21:49, Romain Manni-Bucau < > rmannibucau@gmail.com> a =C3=A9crit : > > > > > > > > > > > > > > > Le sam. 4 mai 2019 =C3=A0 21:44, Mark Struberg a > =C3=A9crit : > > > > > The problem is that in a git repo you can only release all at > once. That means we would need to have a single git repo for each and eve= ry > spec. That will be quite many... > > > > > > > > > > No, maven plugins was a monorepo for years and then they split. > > > > > > > > > > That said i proposed that exactly for that. At the end the releas= e > process is more on jira dev etc, one or N repos does not compress that > time. Release prepare/perform is very fast on these repo so one or 100 is > likely the same for release manager and seems it will also enable better > osgi support and probably - hopefully - enable servicemix to stop forking > the fork ;). > > > > > > > > > > I also see svn as legacy now gitbox is mainstream and people > contributing like to see their name in - I expect maybe some help for new > spec as we got for each new version. > > > > > Fixed are generally trivial there and a good reason to use github= . > > > > > > > > > > > > > > > LieGrue, > > > > > strub > > > > > > > > > > > Am 04.05.2019 um 21:35 schrieb Romain Manni-Bucau < > rmannibucau@gmail.com>: > > > > > > > > > > > > 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=A9crit : > > > > > > 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 < > rmannibucau@gmail.com>: > > > > > > > > > > > >> 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 pas= t > for contributions. > > > > > >> > > > > > >> Le sam. 4 mai 2019 =C3=A0 17:47, Raymond Auge < > raymond.auge@liferay.com> 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 JAXRS v2.1, also qualifies as "Jakarata EE Rest". > > > > > >> > > > > > >> - Ray > > > > > >> > > > > > >> On Sat, May 4, 2019 at 11:26 AM Raymond Auge < > raymond.auge@liferay.com> 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-place? > > > > > >> > > > > > >> - Ray > > > > > >> > > > > > >> On Fri, May 3, 2019 at 1:58 PM Romain Manni-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 some details. > > > > > >> > > > > > >> If we cant reuse them let's just create new ones and fix modul= e > 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 and 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 < > struberg@yahoo.de>: > > > > > >> > > > > > > > >> > > 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 > single 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 the 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) > > > > > > > > > > > > > > > > --0000000000000576270588276bf3 Content-Type: text/html; charset="UTF-8" Content-Transfer-Encoding: quoted-printable
Ok.

Can we a= gree to take this discussion back and hold any release - no issue with snap= s - until it is clarified?

Le dim. 5 mai 2019 =C3=A0 18:45, Mark Struberg <struberg@yahoo.de> a =C3=A9crit=C2=A0:
I'm not even sure whether they yet g= ot all the necessary IP to release anything.

LieGrue,
strub


> Am 05.05.2019 um 18:39 schrieb Romain Manni-Bucau <rmannibucau@g= mail.com>:
>
>
>
> Le dim. 5 mai 2019 =C3=A0 18:30, Mark Struberg <struberg@yahoo.de> a =C3=A9crit :
> I'm not mandating jakarta in the groupId, but it should something = else than the current one.
> Because otw we would have them completely mixed up in the same folder.= That's not nice.
>
> Depends, that said happy to just replace specs by jakarta if it works = for you better (org.apache.geronimo.jakarta). I just dont want jakarta-spec= s or _spec-xxx as before, always looked fishy and almost wrong even if I ge= t where it comes from.
>
> Btw, what is our status on having eclipse releasing api under asf2 lic= ense?
>
> I dont want us to invest in something we drop like in 2 weeks and soun= ds it can be for most of specs. Any page tracking that?
>
>
> LieGrue
> strub
>
> > Am 05.05.2019 um 18:20 schrieb Romain Manni-Bucau <rmannibu= cau@gmail.com>:
> >
> > We dont need jakarta in the gav at all.
> >
> > Why not org.apache.geronimo.spec:servlet:4.0.1?
> >
> > As a reminder specs means jakarta already and there id jo ambigui= ty between jakarta and javaee thanks the version.
> >
> > That said if we move to git it id even physically clearer.
> >
> > Finally servlet is a bad example cause owned at tomcat for apache= i think. We should absolutely stop duplicating them, it pollutes user land= for no gain IMHO.
> >
> >
> >
> >
> > Le dim. 5 mai 2019 =C3=A0 16:28, Mark Struberg <struberg@yahoo.= de> a =C3=A9crit :
> > Eclipse itself probably doesn't yet have all the IP themselve= s. This first needs to be clarified. Since all those legal questions have b= een dealt with behind closed doors we simply have no idea.
> >
> > But we do have clean-room implemented APIs under ALv2 over here a= t Geronimo.
> > And we can move this ourselves without having to wait for anybody= .
> >
> > LieGrue,
> > strub
> >
> >
> > > Am 05.05.2019 um 16:12 schrieb Bernd Eckenfels <eck= i@zusammenkunft.net>:
> > >
> > > I wonder if you need that going forward for Jakarta Specs, t= hey could just be distributed by Eclipse directly? Having said that, if thi= s is not the case I would at least remove =E2=80=9Egeronimo-=E2=80=9C from = the artifact Id?
> > >
> > >
> > > --
> > > http://bernd.eckenfels.net
> > >=C2=A0
> > > Von: Mark Struberg <struberg@yahoo.de>
> > > Gesendet: Sonntag, Mai 5, 2019 4:09 PM
> > > An: geronimo-dev
> > > Betreff: Re: [DISCUSS] implement jakarta spec apis
> > >=C2=A0
> > > For now I've used the following patterns:
> > >
> > > <groupId>org.apache.geronimo.jakarta-specs</groupId= >
> > > because specs and jakarta-specs should be in a clearly separ= ated folder.
> > >
> > > <artifactId>geronimo-jakarta-servlet_spec</artifact= Id>
> > > because 'jakarta' should be in the jar name
> > >
> > > <version>4.0_1-SNAPSHOT</version>
> > > 4.0 is for servlet-4.0, 1 is the patch level.
> > >
> > > I'd NOT do a release or push to our snapshots repo until= in about 2 weeks when the modus operandi is clear within the Jakarta commu= nity.
> > >
> > > LieGrue,
> > > strub
> > >
> > >
> > >
> > > > Am 05.05.2019 um 08:55 schrieb Romain Manni-Bucau <<= a href=3D"mailto:rmannibucau@gmail.com" target=3D"_blank" rel=3D"noreferrer= ">rmannibucau@gmail.com>:
> > > >
> > > > Do we also want to clean our gav? Artifact=3Dspec, majo= r.minor version =3Dspec version
> > > >
> > > > Ex: org.apache.geronimo.specs:jsp:2.1.1
> > > >
> > > > Le sam. 4 mai 2019 =C3=A0 21:49, Romain Manni-Bucau <= ;rmannibucau@gmail.com> a =C3=A9crit :
> > > >
> > > >
> > > > Le sam. 4 mai 2019 =C3=A0 21:44, Mark Struberg <strub= erg@yahoo.de> a =C3=A9crit :
> > > > The problem is that in a git repo you can only release = all at once. That means we would need to have a single git repo for each an= d every spec. That will be quite many...
> > > >
> > > > No, maven plugins was a monorepo for years and then the= y split.
> > > >
> > > > That said i proposed that exactly for that. At the end = the release process is more on jira dev etc, one or N repos does not compre= ss that time. Release prepare/perform is very fast on these repo so one or = 100 is likely the same for release manager and seems it will also enable be= tter osgi support and probably - hopefully - enable servicemix to stop fork= ing the fork ;).
> > > >
> > > > I also see svn as legacy now gitbox is mainstream and p= eople contributing like to see their name in - I expect maybe some help for= new spec as we got for each new version.
> > > > Fixed are generally trivial there and a good reason to = use github.
> > > >
> > > >
> > > > LieGrue,
> > > > strub
> > > >
> > > > > Am 04.05.2019 um 21:35 schrieb Romain Manni-Bucau = <rmannibucau@gmail.com>:
> > > > >
> > > > > AFAIK we dont have limitations there and can do sh= are stuff outside with jgit - but it is very rare - so probably sane to uni= fy 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 <= ;= struberg@yahoo.de> a =C3=A9crit :
> > > > > I=E2=80=99d keep that in svn because of the tons o= f modules.
> > > > >
> > > > > Lg,
> > > > > Strub
> > > > >
> > > > > Am 04.05.2019 um 19:28 schrieb Romain Manni-Bucau = <rmannibucau@gmail.com>:
> > > > >
> > > > >> 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 limita= tions by the past for contributions.
> > > > >>
> > > > >> Le sam. 4 mai 2019 =C3=A0 17:47, Raymond Auge = <raymond.auge@liferay.com> a =C3=A9crit :
> > > > >> One thing to consider is there may be cases wh= ere it is desirable to retain the javax API alongside some extra jakarta pa= ckages & types.
> > > > >>
> > > > >> For example, for JAX-RS you may wish to add so= me 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 packag= es which, in combination with JAXRS v2.1, also qualifies as "Jakarata = EE Rest".
> > > > >>
> > > > >> - Ray
> > > > >>
> > > > >> On Sat, May 4, 2019 at 11:26 AM Raymond Auge &= lt;raymond.auge@liferay.com> 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-place?
> > > > >>
> > > > >> - Ray
> > > > >>
> > > > >> On Fri, May 3, 2019 at 1:58 PM Romain Manni-Bu= cau <rmannibucau@gmail.com> wrote:
> > > > >> Hmm
> > > > >>
> > > > >> My understanding was it was getting under ecli= pse license as well and was fully donated but can have missed some details.=
> > > > >>
> > > > >> If we cant reuse them let's just create ne= w ones and fix module name for others.
> > > > >>
> > > > >> specs/ is fine since it is the same for us IMH= O
> > > > >>
> > > > >> Le ven. 3 mai 2019 =C3=A0 18:24, Mark Struberg= <struberg@yahoo.de> a =C3=A9crit :
> > > > >> No, it is not the same. microprofile specs are= licensed 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 exactly what parts did yet get donated by Oracle to = the EF.
> > > > >>
> > > > >> LieGrue,
> > > > >> strub
> > > > >>
> > > > >>
> > > > >> > Am 03.05.2019 um 18:12 schrieb Romain Man= ni-Bucau <rmannibucau@gmail.com>:
> > > > >> >
> > > > >> > Hi
> > > > >> >
> > > > >> > Idnt it the exact same as for microprofil= e? So we dont do?
> > > > >> >
> > > > >> > Le ven. 3 mai 2019 =C3=A0 16:21, Mark Str= uberg <struberg@yahoo.de> a =C3=A9crit :
> > > > >> > I've started tinkering something unde= r specs/branches/jakarta.
> > > > >> > It's wip but have to rush out for a f= ew 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-j= ava-trademarks/
> > > > >> > >
> > > > >> > > It basically says that Jakarta will = not be able to change a single bit in the current spec apis under the javax= .* package.
> > > > >> > > Any change has to be done in a diffe= rent package.
> > > > >> > > The Jakarta people over at Eclipse a= lready did some voting and the new package name will be jakarta.*
> > > > >> > >
> > > > >> > > Thus I would like to recommend to us= e our IP clean geronimo-specs to setup a new project for the EE8 specs unde= r the jakarta.* package name.
> > > > >> > >
> > > > >> > > I'll go forward and create a bra= nch starting with the most important specs.
> > > > >> > >
> > > > >> > > Any feedback and help is welcome! > > > > >> > >
> > > > >> > > LieGrue,
> > > > >> > > strub
> > > > >> > >
> > > > >> >
> > > > >>
> > > > >>
> > > > >>
> > > > >> --
> > > > >> Raymond Aug=C3=A9 (@rotty3000)
> > > > >> Senior Software Architect Liferay, Inc. (@Life= ray)
> > > > >> Board Member & EEG Co-Chair, OSGi Alliance= (@OSGiAlliance)
> > > > >>
> > > > >>
> > > > >> --
> > > > >> Raymond Aug=C3=A9 (@rotty3000)
> > > > >> Senior Software Architect Liferay, Inc. (@Life= ray)
> > > > >> Board Member & EEG Co-Chair, OSGi Alliance= (@OSGiAlliance)
> > > >
> > >
> >
>

--0000000000000576270588276bf3--