Discovering artifacts from classpath

[rquinio1A]

Reason/Context

In cases of shared schemas, primary artifacts may already be in a Maven artifact alongside generated Java interface /POJOs.
For instance:

• a Maven multi-module project with a shared api-binding module where the same API is implemented or consumed by multiple modules.
• an oidc-test artifact which would contain an OpenAPI spec to be able to mock OIDC calls, alongside public/private keys to generate JWT tokens.

The solution today is to copy the primary artifact in the quarkus app so it's discovered for mocking, but that creates duplication.

Description

Today quarkus.microcks.devservices.artifacts.primaries and quarkus.microcks.devservices.artifacts.secondaries allow relative paths.
If a jar contains a META-INF/order-service-openapi.yaml, it should be possible to reference classpath:META-INF/order-service-openapi.yaml
Ideally the automatic discovery should work as well, potentially limited to resources under META-INF/ folder.

Implementation ideas

No response

[github-actions]

This issue has been automatically marked as stale because it has not had recent activity 😴

It will be closed in 30 days if no further activity occurs. To unstale this issue, add a comment with a detailed explanation.

There can be many reasons why some specific issue has no activity. The most probable cause is lack of time, not lack of interest. Microcks is a Cloud Native Computing Foundation project not owned by a single for-profit company. It is a community-driven initiative ruled under open governance model.

Let us figure out together how to push this issue forward. Connect with us through one of many communication channels we established here.

Thank you for your patience ❤️