Re: [VOTE] Release JWT Auth 1.0.0

@John: do you change your -1 anf if not what would it need? @Mark: any vote? ;) Le mar. 5 juin 2018 14:40, Jean-Louis MONTEIRO a écrit : > ok then +1 if as we discussed, we will try to push a PR to Eclipse so we > can yank the APIs from our repos > > Le mar. 5 juin 2018 à 09:33, Romain

Re: [VOTE] Release JWT Auth 1.0.0

ok then +1 if as we discussed, we will try to push a PR to Eclipse so we can yank the APIs from our repos Le mar. 5 juin 2018 à 09:33, Romain Manni-Bucau a écrit : > Le mar. 5 juin 2018 à 09:29, Jean-Louis MONTEIRO a > écrit : > >> I have checked with the 1.1 release and it passes. >> Looks

Re: [DISCUSS] Do we want to host MP-api versions or not

Sounds great. Thanks Le mar. 5 juin 2018 à 09:58, Romain Manni-Bucau a écrit : > I don't have them handy but maybe we should get in touch with aries guys. > Seems current OSGi@MP is driven by liberty profile and they don't seem to > be aware of recent OSGi update leading to API pollution which

Re: [DISCUSS] Do we want to host MP-api versions or not

I don't have them handy but maybe we should get in touch with aries guys. Seems current OSGi@MP is driven by liberty profile and they don't seem to be aware of recent OSGi update leading to API pollution which is pretty bad for end users. Will try to ping a few OSGi@asf guys I know to get help on

Re: [DISCUSS] Do we want to host MP-api versions or not

Sounds a good plan. Can you send a PR on the eclipse projects? I can review them there and most likely get them merged or help pushing Le mar. 5 juin 2018 à 09:36, Romain Manni-Bucau a écrit : > I see, so what about this one: for now we stay like we are @G and once > eclipse has released

[CANCEL][VOTE] Release Simple JCache 1.0.0

Cancelling since JL found that TCK had an issue in their setup. We will reroll soon. Romain Manni-Bucau @rmannibucau | Blog | Old Blog | Github | LinkedIn

[GitHub] jeanouii closed pull request #1: Remove JCS mentions from the project

jeanouii closed pull request #1: Remove JCS mentions from the project URL: https://github.com/apache/geronimo-jcache-simple/pull/1 This is a PR merged from a forked repository. As GitHub hides the original diff on merge, it is displayed below for the sake of provenance: As this is a

[GitHub] jeanouii opened a new pull request #1: Remove JCS mentions from the project

jeanouii opened a new pull request #1: Remove JCS mentions from the project URL: https://github.com/apache/geronimo-jcache-simple/pull/1 This is an automated message from the Apache Git Service. To respond to the message,

Re: [DISCUSS] Do we want to host MP-api versions or not

I see, so what about this one: for now we stay like we are @G and once eclipse has released spifly/provider header/contracts meta we drop them since they prooved we dont need it anymore. Does it sound like a plan? Romain Manni-Bucau @rmannibucau | Blog

Re: [VOTE] Release JWT Auth 1.0.0

Le mar. 5 juin 2018 à 09:29, Jean-Louis MONTEIRO a écrit : > I have checked with the 1.1 release and it passes. > Looks good to me, but I believe we need to decide about the API stuff > before. > Not really, what has been said before is that it was ok to release and then remove if and use

Re: [VOTE] Release JWT Auth 1.0.0

I have checked with the 1.1 release and it passes. Looks good to me, but I believe we need to decide about the API stuff before. It is definitely not a bind copy of the sources, as I checked it. But the signatures and the packages are obviously the same. Le dim. 3 juin 2018 à 22:49, Romain

Re: [DISCUSS] Do we want to host MP-api versions or not

So not needed if we use apache parent pby - this was my point Romain Manni-Bucau @rmannibucau | Blog | Old Blog | Github | LinkedIn

Re: Microprofile 1.3

Hi JL, there is no real "master" for MP AFAIK but basically opentracing is getting released as soon as JWT Auth and simple jcache (vote welcomed) will pass and config is on its way (just needs some cleanup since in current state there are some blocking cases so we need to find a way to enable

Re: Can't close a PR on geronimo-config

Thanks Jon. I did not know about this detail. Good to know even if we are moving to Gitbox Le lun. 4 juin 2018 à 15:23, John D. Ament a écrit : > The commit message doesn't include "this closes " so nothing was triggered > to close. Once this moves to gitbox we should be good. > > John > > On

Re: Microprofile APIs

Oups, sorry Romain, I missed it. Lemme see if I find it Le mar. 5 juin 2018 à 09:01, Romain Manni-Bucau a écrit : > Hi JL, there is already a thread about that, let's continue in the other > one which has more content. > > > Romain Manni-Bucau > @rmannibucau |

Re: Microprofile APIs

Hi JL, there is already a thread about that, let's continue in the other one which has more content. Romain Manni-Bucau @rmannibucau | Blog | Old Blog | Github

Microprofile APIs

Hi again, I have noticed that some MP implementations in Geronimo have APIs duplicated (JWT for instance) some other not (Config for instance). I have quickly chatted with Romain, he told me that's because of the OSGI integration mainly. Was wondering if instead of duplicating, we could maybe

Microprofile 1.3

Hi, Microprofile 1.3 is almost out. Config and JWT are up to date with the last release. Where are we with the rest? Does it make sense to release them all for Microprofile 1.3 and then we can move master to the next versions for Microprofile 1.4. What do you think? Jean-Louis

Re: [DISCUSS] Do we want to host MP-api versions or not

It contains a few standard plugin settings, but that's really it. LieGrue, strub > Am 05.06.2018 um 06:52 schrieb Romain Manni-Bucau : > > I know that part but never understood why not using apache parent > > Le lun. 4 juin 2018 22:06, Mark Struberg a écrit : > yes, they are the parents for