I’d keep that in svn because of the tons of modules. Lg, Strub
> Am 04.05.2019 um 19:28 schrieb Romain Manni-Bucau <[email protected]>: > > 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 à 17:47, Raymond Auge <[email protected]> a écrit : >> 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 <[email protected]> >>> 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 <[email protected]> >>>> 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 <[email protected]> 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 >>>>> > <[email protected]>: >>>>> > >>>>> > Hi >>>>> > >>>>> > Idnt it the exact same as for microprofile? So we dont do? >>>>> > >>>>> > Le ven. 3 mai 2019 à 16:21, Mark Struberg <[email protected]> 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 <[email protected]>: >>>>> > > >>>>> > > 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) >> >> >> -- >> Raymond Augé (@rotty3000) >> Senior Software Architect Liferay, Inc. (@Liferay) >> Board Member & EEG Co-Chair, OSGi Alliance (@OSGiAlliance)
