Re: Make geronimo/xbean config a JSR-382 impl?

Hmm, would work and be saner that what i had in mind. In term of which one wraps the other I'm tempted to say javax.* will move slower than MP so I'd impl javax.* with MP but no strong opposition on the other side for now, doesn't impact the user anyway, right? Romain Manni-Bucau @rmannibucau |

Re: Make geronimo/xbean config a JSR-382 impl?

Maybe we can go yet another way.Take what we have right now (MicroProfile-API) and expose the JSR-382 functionality as wrapper in an additional module? It would also be possible to do it the other way around: have the core use javax.config.* and expose the MP apis in an additional module. I'd

Re: Make geronimo/xbean config a JSR-382 impl?

is a copy-artifact with a relocation doable while 1:1? would avoid branches, otherwise we can need some common modules to avoid a headache when fixing something :s Romain Manni-Bucau @rmannibucau | Blog | Old Blog | Github | LinkedIn 2017-10-27 17:41 GMT+02:00 Mark Struberg

Re: Make geronimo/xbean config a JSR-382 impl?

I thought about just providing another branch. One for MP, the other for the JSR. I expect MicroProfile to also switch to the JSR once it is finally released. I will try to clarify the relation in the next mp meeting. Until that we gonna impl both I'd say. In the future we might even provide an

Re: Make geronimo/xbean config a JSR-382 impl?

As long as we don't lose support for MP Config in the process, I'm fine with it. John On Thu, Oct 26, 2017 at 4:06 PM Jean-Louis MONTEIRO wrote: > Hi Mark, > > sounds like a good idea. > Happy to help if you wish > > JLouis > > Le jeu. 26 oct. 2017 à 21:46, Mark Struberg

[jira] [Created] (GERONIMO-6593) [config] Create a branch for JSR-382

Mark Struberg created GERONIMO-6593: --- Summary: [config] Create a branch for JSR-382 Key: GERONIMO-6593 URL: https://issues.apache.org/jira/browse/GERONIMO-6593 Project: Geronimo Issue