Re: Microprofile OpenAPI

The question posed to the MP team does not really match the question posted here, and seems to be a tangental ask. The problem is this line of code [1], and nothing to do with TomEE's behavior; it defaults to JSON even though the spec states it should be YAML. Perhaps a clean solution would be

Re: Managed connection pool on Safegard

t; Cheers > Bruno Baptista > http://twitter.com/brunobat_ > > > > On 03/10/2018 18:53, Bruno Baptista wrote: > > Thanks John and Romain, > > Will work on the new FailsafeExecutionManagerProvider. > > Cheers > Bruno Baptista > http://twitter.com/brunobat_ > > >

Re: Managed connection pool on Safegard

Hi Bruno Thanks for the PR! I think my intention for what's provided in Safeguard is that we have an overideable per container integration that allows you to look up the executor. So rather than having boolean logic, you use a new implementation of FailsafeExecutionManagerProvider (perhaps as

Re: Geronimo-Config - help in Jira

Hi Daniel We have a single Geronimo project and each component is mapped to a JIRA component. Hope this helps John On Fri, Aug 31, 2018, 13:04 Daniel Dias Dos Santos < daniel.dias.analist...@gmail.com> wrote: > Hi Romain, > > I understood, but how do I find some issue for the other

Re: safeguard's TCK status

Unfortunately the TCK tests have timing issues. They are non-deterministic. On Tue, Aug 28, 2018, 15:15 Raymond Auge wrote: > must have been a first checkout, temporal kinda thing. > > Sorry for the noise, > - Ray > > On Tue, Aug 28, 2018 at 2:54 PM, Raymond Auge > wrote: > >> I've just

Re: geronimo-config-impl CDI beans

I would have to double check in SE mode but I think the archive would be ignored without a beans.xml, at least with weld. On Tue, Aug 21, 2018, 13:46 Romain Manni-Bucau wrote: > We can move all the code to extensions but id be for it only using cdi2 as > a base to avoid useless code. > >

Re: [ANN] new GIT source repos for geronimo microprofile stuff

-1 to a big Uber git repo. It's not really how git is meant to work and makes releasing a bit harder. On Thu, Jun 28, 2018, 7:22 AM Jean-Louis MONTEIRO wrote: > I was asking myself the exact same question this morning. > Each project is quite small and we could put them all into the same

Re: [ANN] new GIT source repos for geronimo microprofile stuff

Sorry must have missed the final "it's now converted" email when infra did the switch :-) On Thu, Jun 28, 2018, 7:22 AM Jean-Louis MONTEIRO wrote: > I was asking myself the exact same question this morning. > Each project is quite small and we could put them all into the same place. > > I

Re: microprofile openapi @asf?

If it's hosted at Geronimo will it be platform independent? Or only work with CXF? On Mon, Jun 18, 2018, 3:30 PM Romain Manni-Bucau wrote: > Hi guys, > > I'm planning to implement microprofile-openapi at geronimo (next to other > microprofile specs) soon (probably beginning of next month).

Config repo being migrated to gitbox

Infra just started work for the move.

Re: [VOTE] Release Apache Geronimo-config-1.2 (take2)

+1 ! On Sun, Jun 10, 2018 at 11:43 AM Mark Struberg wrote: > Hi folks! > > take 2 of the geronimo-config-1.2 release > staging repo is at > > https://repository.apache.org/content/repositories/orgapachegeronimo-1059/ > > source release is at > >

Re: [VOTE] Release JWT Auth 1.0.0

um > (mainly to guarantee the ordinal). Except that it is mainly a normal API > rewrite. Think a diff should show that it is not just copied. Also the > javadoc is 100% from scratch. > > > > > > Romain Manni-Bucau > > > @rmannibucau | Blog | Old Blog |

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

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 Mon, Jun 4, 2018, 8:07 AM Jean-Louis MONTEIRO wrote: > Hi, > > I have applied the PR/2 from Daniel Soro to SVN, but I can't close it. > Usually when Github

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

: > > > Le lun. 4 juin 2018 à 13:36, John D. Ament a > écrit : > >> We should be fixing the MP spec JARs rather than implementing our set of >> JARs. It creates confusion and will lead to inability to run on Java 9. >> > > Last point is wrong since we'll pu

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

We should be fixing the MP spec JARs rather than implementing our set of JARs. It creates confusion and will lead to inability to run on Java 9. On Mon, Jun 4, 2018, 3:57 AM Romain Manni-Bucau wrote: > Well b doesn't solve 3, any way we get karma to do the releases? This > would solve that

Re: [VOTE] Release JWT Auth 1.0.0

t/java-ee-8-high-performance> > > > Le dim. 3 juin 2018 à 17:24, John D. Ament a > écrit : > >> -1 since there's questionably licensed files in >> https://github.com/apache/geronimo-jwt-auth/tree/master/geronimo-microprofile-jwt-auth-spec/src/main/java/org/eclipse/micro

Re: Is JWT Auth Portable?

; | Old Blog > <http://rmannibucau.wordpress.com> | Github > <https://github.com/rmannibucau> | LinkedIn > <https://www.linkedin.com/in/rmannibucau> | Book > <https://www.packtpub.com/application-development/java-ee-8-high-performance> > > > Le dim. 3 jui

Re: [VOTE] Release JWT Auth 1.0.0

-1 since there's questionably licensed files in https://github.com/apache/geronimo-jwt-auth/tree/master/geronimo-microprofile-jwt-auth-spec/src/main/java/org/eclipse/microprofile On Sun, Jun 3, 2018 at 3:44 AM Romain Manni-Bucau wrote: > Up + FYI we pass the tck 1.1 so no need to do another

Is JWT Auth Portable?

I saw that the JWT Auth project only uses OWB and Meecrowave. It does not have tests against Weld, which makes me think its not portable. Why is it a part of Geronimo then?

Re: Move Geronimo MP Config from SVN to GITBOX

eat. Thanks John. > > Le sam. 2 juin 2018 à 12:32, John D. Ament a > écrit : > >> Actually we already discussed it in the past, but slipped through my >> hands due to busy-ness [1]. >> >> I'll submit the request now, since we'll need to reset the mirror needs

Re: Move Geronimo MP Config from SVN to GITBOX

Actually we already discussed it in the past, but slipped through my hands due to busy-ness [1]. I'll submit the request now, since we'll need to reset the mirror needs an infra ticket. [1]:

Re: opentracing update

We can surely refactor it and split it cause the main cdi usage is to > fire a FinishSpan event which hosts a Span and provide a natural extension > point to plug a backend (i intend to just provide a noop and logger impls > which would enable kafka, jdbc, through appenders). > > > > Then

Re: opentracing update

A while ago I tried to implement the MP Open Tracing spec and then gave up. The feature is really something that belongs as a part of the OpenTracing project, and not a vendor implementation capability. You still need a full tracing implementation behind it to work properly, as they are

Re: Wrong header on JWT auth api

lt;https://rmannibucau.metawerx.net/> | Old Blog > <http://rmannibucau.wordpress.com> | Github > <https://github.com/rmannibucau> | LinkedIn > <https://www.linkedin.com/in/rmannibucau> | Book > <https://www.packtpub.com/application-development/java-ee-8-high-p

Wrong header on JWT auth api

Looks like we imported the jwt api to the guthub repo. The header now says licensed to the ASF which is incorrect.

Re: jwt-auth CDI base version

lifiers as AnnotatedType and only OWB 2.0.5 > supports it in OWB series ATM > > > > > > Romain Manni-Bucau > > @rmannibucau | Blog | Old Blog | Github | LinkedIn | Book > > > > 2018-04-23 14:18 GMT+02:00 John D. Ament <johndam...@apache.org>: > >

Re: jwt-auth CDI base version

> <https://github.com/rmannibucau> | LinkedIn > <https://www.linkedin.com/in/rmannibucau> | Book > <https://www.packtpub.com/application-development/java-ee-8-high-performance> > > 2018-04-23 13:17 GMT+02:00 John D. Ament <johndam...@apache.org>: > >>

Re: jwt-auth CDI base version

s or so. > > On 23 April 2018 at 13:03, Jean-Louis MONTEIRO <jeano...@gmail.com> wrote: > >> Overall same view here. >> How hard is it to make it 1.2 compliant? >> >> >> Le lun. 23 avr. 2018 à 12:25, John D. Ament <johndam...@apache.org> a >&

Re: jwt-auth CDI base version

MP has made it very clear they don't care about portable libraries, and only care about the vendor provided solutions. The requirement is that vendors provide a CDI 1.2 runtime to use. Liberty provides a way to switch between them (1.2, 2.0). I think Swarm may have moved to 2.0; not sure. I

Re: website pointers

n | Book >> > > >> > > 2018-03-19 19:28 GMT+01:00 Romain Manni-Bucau <rmannibu...@gmail.com >> >: >> > > ok, seems easier than I thought (not sure why I thought it was still >> a mix with confluence): >> https://svn.apache.org/repos/infra/websites/production/g

Re: simple-jcache?

ps://www.linkedin.com/in/rmannibucau> | Book > <https://www.packtpub.com/application-development/java-ee-8-high-performance> > > 2018-03-20 15:05 GMT+01:00 John D. Ament <john.d.am...@gmail.com>: > >> So it was developed entirely here? I guess its ok, it looked like it was >

Move other repos to gitbox?

Since the JCS code is now on gitbox, how do others feel about moving the other git repos into gitbox? And possibly even converting config into gitbox?

Re: simple-jcache?

ess.com> | Github > <https://github.com/rmannibucau> | LinkedIn > <https://www.linkedin.com/in/rmannibucau> | Book > <https://www.packtpub.com/application-development/java-ee-8-high-performance> > > 2018-03-20 14:56 GMT+01:00 John D. Ament <johndam...@apache.

Re: simple-jcache?

Don't forget that code imports need to go through IP clearance via incubator. On Mon, Mar 19, 2018 at 2:21 PM Romain Manni-Bucau wrote: > Hi guys, > > wonder if there would be some objection to create a geronimo-jcache-simple > project? > > it would host a jcache

Re: jaxrs 2.1 fix

LGTM On Tue, Mar 20, 2018 at 4:15 AM Romain Manni-Bucau wrote: > Hi guys, > > fixed this morning an issue in our jaxrs 2.1 jar which was not handling a > nested SPI (SseEventSource$Builder) correctly - the $ was converted to a .. > > Also changed the default (spec API) to

Re: [VOTE] Release XBean 4.7 (take 2)

On Mon, Mar 19, 2018 at 6:11 PM Romain Manni-Bucau <rmannibu...@gmail.com> wrote: > > > Le 19 mars 2018 20:20, "John D. Ament" <johndam...@apache.org> a écrit : > > The check in the build is that there's a NOTICE file available, and if its > there you s

Re: [VOTE] Release XBean 4.7 (take 2)

hich only > had a very few BSD classes. In our case the majority or work is BSD. Still > the summary derivative work (our shaded bundle) is ALv2. > > So my personal opinion is to revert back to the previous version of the > NOTICE! > > LieGrue, > strub > > > >

Re: MP-JWT progress

On Mon, Mar 19, 2018 at 3:20 AM Romain Manni-Bucau <rmannibu...@gmail.com> wrote: > 2018-03-19 0:07 GMT+01:00 John D. Ament <johndam...@apache.org>: > >> >> >> On Sun, Mar 18, 2018 at 5:38 PM Romain Manni-Bucau <rmannibu...@gmail.com> >> wrote: >

Re: website pointers

We already talked about this last summer https://lists.apache.org/thread.html/f28d62c18e9274e9aa6dd455630b9ea9b962dac5d59eef876e07c237@%3Cdev.geronimo.apache.org%3E John On Mon, Mar 19, 2018 at 5:41 AM Romain Manni-Bucau wrote: > Hi guys, > > anyone able to help to

Re: [VOTE] Release XBean 4.7 (take 2)

-1 The NOTICE file in the JAR is now worse. It indicates that the code was developed at the ASF. IMHO, there should be no NOTICE file in the JAR. If the NOTICE file includes just Apache XBean :: ASM 6 shaded (repackaged) Copyright 2005-2018 The Apache Software Foundation That should be

Re: [VOTE] Move ahead with creating a reusable JWT module

Just to make sure I understand. a +1 on this to me means there may be a module created in geronimo. Maybe not. But either way it shouldn't stop what TomEE is doing. On Sun, Mar 18, 2018 at 8:59 PM David Blevins wrote: > My vote would be -0 and I hesitate even for a

Re: [VOTE] Move ahead with creating a reusable JWT module

On Sun, Mar 18, 2018 at 8:05 PM David Blevins wrote: > Two votes are up in the TomEE community on what to do with PR #123 ( > https://github.com/apache/tomee/pull/123 ). The first vote is if TomEE > should merge it. The second vote is if TomEE should attempt to extract

Re: [VOTE] XBean 4.7 release

t;> >>> I see. Note that the updated guideline does say 'need not' and not 'MUST >>> NOT'. >>> Yes we should probably remove it. But no, it's not a show stopper imo. >>> >>> LieGrue, >>> strub >>> >>> > Am 15.03.2018

Re: MP-JWT progress

On Sun, Mar 18, 2018 at 5:38 PM Romain Manni-Bucau wrote: > > > Le 18 mars 2018 21:29, "David Blevins" a écrit : > > > > On Mar 18, 2018, at 12:43 PM, Romain Manni-Bucau > wrote: > > > > 1. code will be at geronimo -

Re: [VOTE] XBean 4.7 release

On Wed, Mar 14, 2018 at 7:54 PM John D. Ament <john.d.am...@gmail.com> wrote: > On Wed, Mar 14, 2018 at 7:43 PM Mark Struberg <strub...@yahoo.de> wrote: > >> +1 it's not incorrect. Please read the BSD3c license >> >> > 1. Redistributions of sour

Re: [VOTE] XBean 4.7 release

it into NOTICE ;) > > +1 from me. > > Sorry but you're incorrect. The copyright claim is already present by copying in their license file. > > LieGrue, > strub > > > > Am 14.03.2018 um 19:00 schrieb Romain Manni-Bucau <rmannibu...@gmail.com > >: > &g

Re: [VOTE] XBean 4.7 release

:46 PM Romain Manni-Bucau <rmannibu...@gmail.com> wrote: > > > Le 14 mars 2018 18:30, "John D. Ament" <johndam...@apache.org> a écrit : > > Why does the NOTICE file in the resulting JAR (for the ASM shaded > dependency) include > > This product include

Re: [VOTE] XBean 4.7 release

Why does the NOTICE file in the resulting JAR (for the ASM shaded dependency) include This product includes software developed at OW2 Consortium (http://asm.ow2.org/) There is no notice file associated with ASM 6.1, so we should not need to declare any notice. On Wed, Mar 14, 2018 at 12:54 PM

Re: MP-JWT progress

I don't think its a good idea to move TomEE code into Geronimo. On Fri, Mar 9, 2018 at 5:50 AM Romain Manni-Bucau wrote: > If there is no other comment, any objection to move it to > geronimo-jwt-auth? (let say if not we do it on monday european time) > > > Romain

Re: [DISCUSS] Moving our repos to git?

:17 AM John D. Ament <johndam...@apache.org> wrote: > At this point, moving our repos to git would be moving to gitbox, e.g. > github hosted repos, but you can still write to the ASF side primary via > gitbox.a.o. > > Being more active on github will give us a more modern l

Re: [DISCUSS] Moving our repos to git?

At this point, moving our repos to git would be moving to gitbox, e.g. github hosted repos, but you can still write to the ASF side primary via gitbox.a.o. Being more active on github will give us a more modern look. It seems like the right approach to take. John On Sun, Feb 25, 2018 at 5:49

[jira] [Created] (GERONIMO-6598) Pluggable Executor Service

John D. Ament created GERONIMO-6598: --- Summary: Pluggable Executor Service Key: GERONIMO-6598 URL: https://issues.apache.org/jira/browse/GERONIMO-6598 Project: Geronimo Issue Type

[RESULT] (was Re: [VOTE] Apache Safeguard 1.0)

ks guys. > > Great job > > > > and big +1 of course > > > > Le dim. 7 janv. 2018 à 16:21, Romain Manni-Bucau <rmannibu...@gmail.com> > a écrit : > > +1 > > > > Le 6 janv. 2018 19:15, "John D. Ament" <johndam...@apache.org&

Re: Increase email from buildbot

ead of each > time? > That's not a config option that I'm aware of in buildbot, but I can ask. I'm not in favor of that type of behavior though, its still pretty easy to lose. > > Le 8 janv. 2018 23:23, "John D. Ament" <johndam...@apache.org> a écrit : > >>

How the Geronimo Site is built (currently)

Posting this in email, so we don't lose track of the info gathered today. The Geronimo site is built via buildbot against an SVN directory. The buildbot config: https://svn.apache.org/repos/infra/infrastructure/buildbot/aegis/buildmaster/master1/projects/geronimo.conf The SVN dir:

Increase email from buildbot

There was an issue with our site build, which is based on buildbot. It uses some internally developed tools by the CXF project to extract contents of confluence wiki spaces and generate website contents. The job had been failing, for who knows how long. I think it would be useful if we change

Handling blank/empty List/Set/Array values

I just noticed last night that the TCK for MP doesn't cover tests for blank/empty values in List/Set/Array. My assumption is that wrapping these in Optional<> doesn't make sense, but if you are missing a value in one of these types for injection purposes, we should use an empty object. Does

[VOTE] Apache Safeguard 1.0

All, This is a call to vote on the Safeguard 1.0 release. it implements the MicroProfile Fault Tolerance API v1.0. Release notes can be found at *https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=10220=12341571

[jira] [Resolved] (GERONIMO-6591) Add support for fallbacks

[ https://issues.apache.org/jira/browse/GERONIMO-6591?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] John D. Ament resolved GERONIMO-6591. - Resolution: Fixed Assignee: John D. Ament > Add support for fallba

[jira] [Resolved] (GERONIMO-6587) Add support for Asynchronous invocations

[ https://issues.apache.org/jira/browse/GERONIMO-6587?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] John D. Ament resolved GERONIMO-6587. - Resolution: Fixed Assignee: John D. Ament > Add support for Asynchron

[jira] [Resolved] (GERONIMO-6582) Implement MicroProfile Fault Tolerance 1.0

[ https://issues.apache.org/jira/browse/GERONIMO-6582?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] John D. Ament resolved GERONIMO-6582. - Resolution: Fixed Assignee: John D. Ament > Implement MicroProfile Fa

[jira] [Resolved] (GERONIMO-6584) Add support for Circuit Breakers

[ https://issues.apache.org/jira/browse/GERONIMO-6584?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] John D. Ament resolved GERONIMO-6584. - Resolution: Fixed Assignee: John D. Ament > Add support for Circuit Break

[jira] [Resolved] (GERONIMO-6583) Add support for Bulkhead

[ https://issues.apache.org/jira/browse/GERONIMO-6583?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] John D. Ament resolved GERONIMO-6583. - Resolution: Fixed Assignee: John D. Ament > Add support for Bulkh

[jira] [Resolved] (GERONIMO-6585) Add support for Timeouts

[ https://issues.apache.org/jira/browse/GERONIMO-6585?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] John D. Ament resolved GERONIMO-6585. - Resolution: Fixed Assignee: John D. Ament > Add support for Timeo

[jira] [Closed] (GERONIMO-6597) Implement MP Config 1.2

[ https://issues.apache.org/jira/browse/GERONIMO-6597?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] John D. Ament closed GERONIMO-6597. --- Assignee: John D. Ament > Implement MP Config

[jira] [Closed] (GERONIMO-6595) add support for Implicit Converters

[ https://issues.apache.org/jira/browse/GERONIMO-6595?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] John D. Ament closed GERONIMO-6595. --- > add support for Implicit Convert

[jira] [Closed] (GERONIMO-6592) PropertyFileConfigSource throws NPE when passed in URL doesn't match a file

[ https://issues.apache.org/jira/browse/GERONIMO-6592?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] John D. Ament closed GERONIMO-6592. --- > PropertyFileConfigSource throws NPE when passed in URL doesn't match a f

Re: Planning to cut Config & Safeguard This Week

Romain, On Thu, Jan 4, 2018 at 12:58 AM Romain Manni-Bucau <rmannibu...@gmail.com> wrote: > > > Le 4 janv. 2018 04:24, "John D. Ament" <john.d.am...@gmail.com> a écrit : > > Romain, > > I'm going to top post, because I don't want to keep this

[RESULT] (was Re: [VOTE] Release Geronimo Config 1.1)

e 2 janv. 2018 18:57, "Jean-Louis MONTEIRO" <jeano...@gmail.com> a > écrit : > >> I have the kids tonight so as soon as they are in bed, I'll have a look > ;-) > >> > >> Le mar. 2 janv. 2018 à 15:06, John D. Ament <johndam...@apache.org> a > éc

Re: Planning to cut Config & Safeguard This Week

@%3Cdev.geronimo.apache.org%3E On Tue, Jan 2, 2018 at 10:05 AM Romain Manni-Bucau <rmannibu...@gmail.com> wrote: > 2018-01-02 15:01 GMT+01:00 John D. Ament <johndam...@apache.org>: > >> >> >> On Tue, Jan 2, 2018 at 8:11 AM Romain Manni-Bucau <rmannibu...@gm

[VOTE] Release Geronimo Config 1.1

All, This is a call to vote on the Geronimo Config 1.1 release. it implements the MicroProfile Config API v1.2. Release notes can be found at https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=10220=12341750 The source release can be found at:

Re: Planning to cut Config & Safeguard This Week

On Tue, Jan 2, 2018 at 8:11 AM Romain Manni-Bucau <rmannibu...@gmail.com> wrote: > 2018-01-02 13:02 GMT+01:00 John D. Ament <johndam...@apache.org>: > >> >> >> On Tue, Jan 2, 2018 at 3:17 AM Romain Manni-Bucau <rmannibu...@gmail.com> >&g

[jira] [Updated] (GERONIMO-6597) Implement MP Config 1.2

[ https://issues.apache.org/jira/browse/GERONIMO-6597?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] John D. Ament updated GERONIMO-6597: Component/s: Config > Implement MP Config

[jira] [Resolved] (GERONIMO-6597) Implement MP Config 1.2

[ https://issues.apache.org/jira/browse/GERONIMO-6597?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] John D. Ament resolved GERONIMO-6597. - Resolution: Fixed > Implement MP Config

[jira] [Updated] (GERONIMO-6597) Implement MP Config 1.2

[ https://issues.apache.org/jira/browse/GERONIMO-6597?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] John D. Ament updated GERONIMO-6597: Fix Version/s: Config_1.1 > Implement MP Config

Re: Planning to cut Config & Safeguard This Week

e here. >> >> Looking that now, will report soon >> >> >> Romain Manni-Bucau >> @rmannibucau <https://twitter.com/rmannibucau> | Blog >> <https://rmannibucau.metawerx.net/> | Old Blog >> <http://rmannibucau.wordpress.com> | Github >&g

Re: Planning to cut Config & Safeguard This Week

t not I'm a bit worried with that kind of approach since class importing is no longer behaving the same way. I went with a ServiceLoader approach, this way even app servers can come up with their own configuration mechanism independent of MP. > > Le 1 janv. 2018 18:51, "John D. Ame

Re: Planning to cut Config & Safeguard This Week

ote: > Any hope to have mp config optional before? Was planning to do it before > Xmas but didnt get a chance yet to code it. Can try later this week > probably. > > Le 1 janv. 2018 17:19, "John D. Ament" <johndam...@apache.org> a écrit : > >> >> >&

Re: Planning to cut Config & Safeguard This Week

l and the spec issues I saw, GConfig 1.0 ended up implementing MP Config 1.1. I think only IBM shipped an impl of just Config 1.0. > > LieGrue, > strub > > > Am 01.01.2018 um 16:34 schrieb John D. Ament <johndam...@apache.org>: > > > > Hey guys > > >

Planning to cut Config & Safeguard This Week

Hey guys Just pushed up the last of the changes for Safeguard to make it pass Fault Tolerance 1.0's TCK. There's a small change I still want to make it to allow the executor to be pluggable, and plan to have a following release soon that introduces more configurable properties. With that said,

Re: Geronimo Config 1.1?

> them in sync! > So on that note, I think we should start trying to figure out how to support both ConfigJSR and MP in a single codebase. They're similar enough that its feasible, I'm wondering if it makes sense to introduce unique builders per, but have a common underlying Config object in

Re: Geronimo Config 1.1?

nd do a pair review of it and then unify it again. > > LieGrue, > strub > > > Am 24.12.2017 um 08:23 schrieb Romain Manni-Bucau <rmannibu...@gmail.com > >: > > > > Sounds good. Thanks for the heads up > > > > Le 24 déc. 2017 05:02, "John

Geronimo Config 1.1?

Hey all I just pushed up the last of the changes in the Geronimo config trunk that would align to the MP Config 1.2 spec. There's still a bit of clean up I want to aim for, so maybe after the new year we can plan to cut a release of Config 1.1? You'll note in my commit, I moved most of the

[jira] [Updated] (GERONIMO-6597) Implement MP Config 1.2

[ https://issues.apache.org/jira/browse/GERONIMO-6597?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] John D. Ament updated GERONIMO-6597: Summary: Implement MP Config 1.2 (was: Support MP Config 1.2) > Implement MP Config

[jira] [Created] (GERONIMO-6597) Support MP Config 1.2

John D. Ament created GERONIMO-6597: --- Summary: Support MP Config 1.2 Key: GERONIMO-6597 URL: https://issues.apache.org/jira/browse/GERONIMO-6597 Project: Geronimo Issue Type: New Feature

Re: [VOTE] [RESULT] JAX-RS 2.1 spec jar release

; > Am 23.12.2017 um 15:06 schrieb Romain Manni-Bucau <rmannibu...@gmail.com > >: > > > > Hi John > > > > I fixed the notice but missed other parts i think > > > > Happy to fix more if it gets pointed out. > > > > Side note: will try

Re: [VOTE] JAX-RS 2.1 spec jar release

In addition to what Reinhard's noting, the vendor in the pom is wrong. I also reported https://issues.apache.org/jira/browse/INFRA-15714 since Romain's changes aren't up on github The newly created files include "Apache Geronimo JAX-RS Spec 2.0" which is wrong and should be addressed next

Re: Reading microprofile-config.properties from a WAR file in an Arquillian test

2017 at 1:10 PM John D. Ament <johndam...@apache.org> wrote: > I agree, but then why does Shrinkwrap put the files there? > > > On Thu, Nov 30, 2017 at 1:07 PM Romain Manni-Bucau <rmannibu...@gmail.com> > wrote: > >> WEB-INF/classes/META-INF yep, (classpath only

Re: Reading microprofile-config.properties from a WAR file in an Arquillian test

NF in a war sounds weird no? > > Romain Manni-Bucau > @rmannibucau | Blog | Old Blog | Github | LinkedIn > > > 2017-11-30 19:05 GMT+01:00 John D. Ament <johndam...@apache.org>: > > I have the following deployment used in an Arquillian test: > > > > @

Reading microprofile-config.properties from a WAR file in an Arquillian test

I have the following deployment used in an Arquillian test: @Deployment public static WebArchive createDeployment() { String propertyName = SimpleGetApi.class.getName()+"/mp-rest/url"; String value = getStringURL(); return ShrinkWrap.create(WebArchive.class)

Re: Safeguard without MP-Config?

Hi Rüdiger! I think it would be fine if it could operate without MP Config. I was actually thinking that configuration could be more of an SPI, rather than a hard requirement. E.g. one impl for MP Config, another for ConfigJSR, and maybe a default one with system properties enabled? And you

[jira] [Closed] (GERONIMO-6589) Use getPropertyNames to locate properties that should exist

[ https://issues.apache.org/jira/browse/GERONIMO-6589?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] John D. Ament closed GERONIMO-6589. --- Resolution: Invalid I had already done this. > Use getPropertyNames to locate propert

[jira] [Resolved] (GERONIMO-6592) PropertyFileConfigSource throws NPE when passed in URL doesn't match a file

[ https://issues.apache.org/jira/browse/GERONIMO-6592?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] John D. Ament resolved GERONIMO-6592. - Resolution: Fixed > PropertyFileConfigSource throws NPE when passed in URL does

Update on Safeguard

Hey guys I pushed up a pretty big commit last night which adds bulkhead support. Lots of pain in the TCK in that area, if it was clearer what was going on I would have been done a few weeks ago :-( Anyways, with that commit the last actual Fault Tolerance feature is done. There's two areas left:

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-6592) PropertyFileConfigSource throws NPE when passed in URL doesn't match a file

John D. Ament created GERONIMO-6592: --- Summary: PropertyFileConfigSource throws NPE when passed in URL doesn't match a file Key: GERONIMO-6592 URL: https://issues.apache.org/jira/browse/GERONIMO-6592

Re: Better ways to add to an Arquillian deployment?

supports enrichment instead or archive > enrichment? > > Le 8 oct. 2017 19:22, "Romain Manni-Bucau" <rmannibu...@gmail.com> a > écrit : > >> What about wrapping the contextual container and enrich it in deploy? >> >> Le 8 oct. 2017 18:54, "John D. Ament

Better ways to add to an Arquillian deployment?

Hey guys (maybe Mark specifically?) A number of people have been copying the pattern you helped create, where we use an archive appender in Arquillian to add test classes. This works, however it causes an issue. I opened a bug against Arquillian, because deployments that expect exceptions to be

[jira] [Created] (GERONIMO-6591) Add support for fallbacks

John D. Ament created GERONIMO-6591: --- Summary: Add support for fallbacks Key: GERONIMO-6591 URL: https://issues.apache.org/jira/browse/GERONIMO-6591 Project: Geronimo Issue Type: Sub-task

Re: Additional Config Sources?

t and it is quite unconfortable > at that time to do twice the exact same thing @asf. We should probably try > to converge at some point. > > > > > > Romain Manni-Bucau > > @rmannibucau | Blog | Old Blog | Github | LinkedIn | JavaEE Factory > > > > 201

  1   2   3   >