Improve computation of Quarkus/MicroProfile properties

[angelozerr]

Today JDTQuarkusManager compute Quarkus properties from sources and dependencies, but there are several issues about computing properties like :

• Kubernetes properties don't show up vscode-quarkus#129
• Add support for MicroProfile REST properties vscode-quarkus#104
• Get extension name from the META-INF/quarkus-extensions.(yaml | json) #133

which shows several limitations:

• the properties are computed only for Quarkus and not for Microprofile annotations. The compute of properties should be extensible via an Eclipse extension point
• the microprofile property name can be complex and composed with dynamic part and static part. The property name should reference a list of values

For instance using @RegisterRestClient annotation gives the capability to customize the url:

com.example.BeerGateway/mp-rest/url=https://api.punkapi.com

• com.example.BeerGateway is a dynamic part (a class bound with @RegisterRestClient
• /mp-rest/url is a static part

To support this microprofile @RegisterRestClient annotation, we should provide in application.properties :

• completion for class annotated with @RegisterRestClient
• validation for class annotated with @RegisterRestClient
• hover for class annotated with @RegisterRestClient
• definition for class annotated with @RegisterRestClient

Refactor JDTQuarkusManager

JDTQuarkusManager should be renamed to JDTMicroprofileManager or perhaps JDTApplicationPropertiesManager?. The compute of properties should use extension point to manage any annotations (microprofile, quarkus) or without annotation like kubernetes.

Instead returning a list of properties like JDTQuarkusManager ,The JDTMicroprofileManager should return a list of types (ex : properties, classes-for-microprofile_restclient, quarkus-extensions, enumeration-values) and for each type a list of ExtendedConfigDescriptionBuildItem (it should be perhaps renamed). The property name can reference an another type.

Given this microprofile sample:

com.example.BeerGateway/mp-rest/url=https://api.punkapi.com, the JDTMicroprofileManager will return this JSON:

{
	"types": [
		{
			"name": "classes-for-microprofile_restclient",
			"items": [
				{
					"propertyName": "com.example.BeerGateway",
					"type": ....
				}
			]
		},
		{
			"name": "properties",
			"items": [
				{
					"propertyName": "quarkus.log.enabled",
					"type": ....
				},
				{
					"propertyName": "${classes-for-microprofile_restclient}/mp-rest/url"
				}
			]
		}
	]
}

Eclipse extension point

An eclipse extension point should give the capability to update classpath (ex: deployment JAR for Quarkus), create pattern search (ex: search ConfigRoot for Quarkus), compute properties.

What about com.redhat.microprofile.core.propertiesProvider as name?

The property name should reference a list of values

See ${classes-for-microprofile_restclient}/mp-rest/url sample