Keep the custom Class-Path in the manifest file

[h2cone]

Currently we can specify custom manifest entries, but we cannot keep the custom Class-Path because generating the manifest would overwrite this existing entry.

By adding additional JAR files and directories to the class path, we can not only avoid specifying a long -classpath flag, but also load resources via relative paths.

[h2cone]

PTAL @geoand

[geoand]

I don't think this is going to work for fast-jar to be honest...

[h2cone]

I don't think this is going to work for fast-jar to be honest...

Thanks, could you please explain it in detail?

In my case, the app.jar and resources are separated into the same directory because they are often changed independently:

.
├── app.jar
└── resources
    ├── application.properties
    ├── init
    │   └── my.json
    ├── static
    └── templates

I need to load a resource by its name, for example using the method getResourceAsStream, so I try to customize the class path:

quarkus.package.manifest.attributes."Class-Path"=resources/

Use ./mvnw package -Dquarkus.package.type=uber-jar to output uber-jar, the following method returns null after startup:

Thread.currentThread().getContextClassLoader().getResourceAsStream("init/my.json");

Why must the Class-Path of uber-jar be overwritten with blank when generating manifest?

[geoand]

Why must the Class-Path of uber-jar be overwritten with blank when generating manifest?

My comment was about fast-jar, not uber-jar :)

[quarkus-bot]

Failing Jobs - Building b4d132e

Status	Name	Step	Failures	Logs	Raw logs
✖	Devtools Tests - JDK 11	Build	Failures	Logs	Raw logs
✖	Devtools Tests - JDK 17	Build	Failures	Logs	Raw logs

Full information is available in the Build summary check run.

Failures

⚙️ Devtools Tests - JDK 11 #

- Failing: integration-tests/devtools 

📦 integration-tests/devtools

✖ io.quarkus.platform.catalog.RegistrySnapshotCatalogCompatibilityTest.testRegistrySnapshotPlatformCatalog line 30 - More details - Source on GitHub

java.lang.IllegalStateException: Failed to locate the dev tools config file (.quarkus/config.yaml)
	at io.quarkus.devtools.testing.registry.client.TestRegistryClient.<init>(TestRegistryClient.java:33)
	at io.quarkus.devtools.testing.registry.client.TestRegistryClientFactory.buildRegistryClient(TestRegistryClientFactory.java:32)

---

⚙️ Devtools Tests - JDK 17 #

- Failing: integration-tests/devtools 

📦 integration-tests/devtools

✖ io.quarkus.platform.catalog.RegistrySnapshotCatalogCompatibilityTest.testRegistrySnapshotPlatformCatalog line 30 - More details - Source on GitHub

java.lang.IllegalStateException: Failed to locate the dev tools config file (.quarkus/config.yaml)
	at io.quarkus.devtools.testing.registry.client.TestRegistryClient.<init>(TestRegistryClient.java:33)
	at io.quarkus.devtools.testing.registry.client.TestRegistryClientFactory.buildRegistryClient(TestRegistryClientFactory.java:32)

[gsmet]

I'm not sure this really makes sense, especially with the closed world assumption we have in Quarkus. We want jars to be detectable by Quarkus and not pushed to it via the classpath.

What is your requirement exactly and why do you want to do that, rather than say add a new dependency to your build file?

[gsmet]

Closing for lack of feedback.