Fix runtime/deployment detection and propagate it

[gsmet]

That way, we can assert if the module is a deployment module later in the process.

Related to #43513

/cc @mcruzdev the idea would be to check things in ConfigMappingListener#onConfigRoot(). You have the ExtensionModule in the passed Config config after this patch.

[gsmet]

@mcruzdev to give you more details: the annotation processor operates at a totally different level: we can access the module files relatively easily and that's how we extract the module information.

For now, a deployment module is one that doesn't have a quarkus-extension.properties file and whose name ends with -deployment.
At some point, we will probably make the detection a bit more solid as we are making progress on a Maven plugin for the extension deployment module.

The code is here:

quarkus/core/processor/src/main/java/io/quarkus/annotation/processor/util/ExtensionUtil.java

Lines 189 to 205 in a4d7e2f

	private ExtensionModuleType detectExtensionModuleType(String artifactId) {
	try {
	Path runtimeMarkerFile = Paths
	.get(processingEnv.getFiler().getResource(StandardLocation.CLASS_OUTPUT, "", RUNTIME_MARKER_FILE).toUri());
	if (Files.exists(runtimeMarkerFile)) {
	return ExtensionModuleType.RUNTIME;
	}
	} catch (IOException e) {
	// ignore, the file doesn't exist
	}
	if (artifactId.endsWith(ARTIFACT_DEPLOYMENT_SUFFIX)) {
	return ExtensionModuleType.DEPLOYMENT;
	}
	return ExtensionModuleType.UNKNOWN;
	}

[gsmet]

This was a dumb mistake on my side. It had no consequences until now but we need it to actually work from now on :).

[github-actions]

🎊 PR Preview 7603085 has been successfully built and deployed to https://quarkus-pr-main-44390-preview.surge.sh/version/main/guides/

• Images of blog posts older than 3 months are not available.
• Newsletters older than 3 months are not available.

[quarkus-bot]

Status for workflow Quarkus Documentation CI

This is the status report for running Quarkus Documentation CI on commit a4d7e2f.

✅ The latest workflow run for the pull request has completed successfully.

It should be safe to merge provided you have a look at the other checks in the summary.

Warning

There are other workflow runs running, you probably need to wait for their status before merging.

[quarkus-bot]

Status for workflow Quarkus CI

This is the status report for running Quarkus CI on commit a4d7e2f.

✅ The latest workflow run for the pull request has completed successfully.

It should be safe to merge provided you have a look at the other checks in the summary.

You can consult the Develocity build scans.