git.net

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Release config?


Yes, this is why i wondered if it was "mainstream" today but Mark
explained me offline that it can replace MP-config at some point.
My main goal is to ensure we keep a single codebase with the same
features to ensure the switch is hurtless (i just migrated from
deltaspike config to mp-config it was hurtful cause of a gap of
features in the impl), i dont want our 2 main branches be that
different so we should find a way to use the same code behind the API.
ASM remapping, common code, ... I dont care much but one main codebase
please

Romain Manni-Bucau
@rmannibucau |  Blog | Old Blog | Github | LinkedIn | Book

Le sam. 2 juin 2018 à 03:31, Jean-Louis MONTEIRO <jeanouii@xxxxxxxxx> a écrit :
>
> Config was the last spec to use javax namespace
>
> Le mar. 29 mai 2018 à 14:36, Mark Struberg <struberg@xxxxxxxx> a écrit :
>>
>> Yes, javax.config is the official namespace for JSR-382.
>>
>> LieGrue,
>> strub
>>
>>
>> > Am 29.05.2018 um 20:11 schrieb Romain Manni-Bucau <rmannibucau@xxxxxxxxx>:
>> >
>> > Are the api 1-1? If so lets merge the src and avoid a double maintenance and release both at once.
>> >
>> > What would be our mainstream then/after? Javax - is the name still allowed?
>> >
>> > Le mar. 29 mai 2018 20:02, Mark Struberg <struberg@xxxxxxxx> a écrit :
>> > JSR-382 EDR-1 will be released soon. Currently preparing.
>> > And mp-config is to follow soon.
>> >
>> > LieGrue,
>> > strub
>> >
>> > On Tuesday, 29 May 2018, 19:48:31 CEST, Romain Manni-Bucau <rmannibucau@xxxxxxxxx> wrote:
>> >
>> >
>> > Hmm
>> >
>> > Is configjsr anything real (ie with a release coming within 2-3 months)?
>> >
>> > If not let use mp as mainstream until it is the case.
>> >
>> > We can still release both with shade plugin until they diverge.
>> >
>> > Le mar. 29 mai 2018 19:39, Mark Struberg <struberg@xxxxxxxx> a écrit :
>> > The api is effectively different only for the package names yet (javax.config vs org.eclipse.microprofile.config).
>> > The rest is the same. branches/ConfigJSR contains many more features which will be backported to microprofile-config.
>> >
>> > In other words: ConfigJSR is the leading branch.
>> >
>> > LieGrue,
>> > strub
>> >
>> > On Tuesday, 29 May 2018, 18:48:40 CEST, Romain Manni-Bucau <rmannibucau@xxxxxxxxx> wrote:
>> >
>> >
>> > +1 to merge both until api breaks
>> >
>> > Romain Manni-Bucau
>> > @rmannibucau |  Blog | Old Blog | Github | LinkedIn | Book
>> >
>> >
>> > Le mar. 29 mai 2018 à 18:47, Mark Struberg <struberg@xxxxxxxx> a écrit :
>> >
>> > Will bring it to the same level like branches/ConfigJSR. Those 2 pretty much derailed from each other, so we will have a hard time to maintain it later.
>> >
>> > Will do this evening.
>> >
>> > LieGrue,
>> > strub
>> >
>> > On Tuesday, 29 May 2018, 12:16:36 CEST, Romain Manni-Bucau <rmannibucau@xxxxxxxxx> wrote:
>> >
>> >
>> > Hi guys,
>> >
>> > Any blocker to release config from master? I have a few fixes I'd like to be able to use ASAP
>> >
>> > Romain Manni-Bucau
>> > @rmannibucau |  Blog | Old Blog | Github | LinkedIn | Book
>>