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 module name for others.

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

Le ven. 3 mai 2019 à 18:24, Mark Struberg <struberg@yahoo.de> a écrit :
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 à 16:21, Mark Struberg <struberg@yahoo.de> a écrit :
> 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é (@rotty3000)
Senior Software Architect Liferay, Inc. (@Liferay)
Board Member & EEG Co-Chair, OSGi Alliance (@OSGiAlliance)