Quarkus Resteasy Problem Extension (RFC7807)

[Lukasz Usowicz]

Hi,

I just wanted to ask about possible ways to incorporate recently opensourced extension we made in TietoEvry to Quarkus ecosystem.

https://github.com/TietoEVRY/quarkus-resteasy-problem

I wonder if there a means/guidelines if/how this can be integrated closer with Quarkus itself.
Could be part of Quarkus , should we maybe contact Quarkiverse and try to apply there?

Or maybe this particular type of extension should be kept separate from Quarkus related repositories.

And hints for how make our contribution most valuable and visible to community will be appreciate.

Regards,

Lukasz

[Georgios Andrianakis]

Hi,

This sounds like a prime candidate for the Quarkiverse

--
You received this message because you are subscribed to the Google Groups "Quarkus Development mailing list" group.
To unsubscribe from this group and stop receiving emails from it, send an email to quarkus-dev...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/quarkus-dev/c5c47352-8d7b-4539-bbd5-3ce9913d49b8n%40googlegroups.com.

[Andy Damevin]

You can find more info on how to get an extension on boarded in the Quarkiverse there: https://github.com/quarkiverse/quarkiverse

To view this discussion on the web visit https://groups.google.com/d/msgid/quarkus-dev/CALeTM-kuRnWeqhuZo871Q%2BeNc96f_V8p2FGqHX1uDh5FAY_8ZA%40mail.gmail.com.

--

Andy Damevin

[Lukasz Usowicz]

Just out of curiosity how "split" between: into Quarkus vs into Quarkiverse is made? Asking due to `quarkus-jacoco` case which for me seem to be more Quarkiverse then `resteasy-problem`.

@Stephane, @Gytis: Since your involved into related https://github.com/quarkusio/quarkus/issues/13662 can we streamline our efforts?

Regards,

Lukasz

PS. Stephane, could not found your RedHat email, hope you don't mind sending this to private email I found on your page.

--

Łukasz Usowicz

[Stephane Epardaud]

Hi,

This looks very nice. I wonder if this should not be a new core quarkus extension that both resteasy versions (well, the json modules) depend on, to get them automatically. I don't quite see what the drawback would be, as I can't picture anybody not wanting json errors when producing json.

To view this discussion on the web visit https://groups.google.com/d/msgid/quarkus-dev/CAKxBDyRVGFjcWcP4EW78xXOr%2ByPe6bFzif-9bom%2BBGuK2J7fGA%40mail.gmail.com.

--

Stéphane Épardaud

[Stuart Douglas]

On Wed, 7 Apr 2021 at 23:00, Lukasz Usowicz <luk...@usowicz.pl> wrote:

Just out of curiosity how "split" between: into Quarkus vs into Quarkiverse is made? Asking due to `quarkus-jacoco` case which for me seem to be more Quarkiverse then `resteasy-problem`.

I did think about this, but the reason I decided on core is that code coverage is something that a large percentage of Quarkus users will likely be interested in (similar to quarkus-mockito).

From a technical point of view this also needed changes to the core transformation process, so core changes were always going to be needed.

Stuart

 

To view this discussion on the web visit https://groups.google.com/d/msgid/quarkus-dev/CAKxBDyRVGFjcWcP4EW78xXOr%2ByPe6bFzif-9bom%2BBGuK2J7fGA%40mail.gmail.com.