P4
JVMCI currently includes an annotation based mechanism to simplify the implementation of service providers. In particular, it removes the need to manually create the necessary provider-configuration files in META-INF/services.
Having an annotation based mechanism in JVMCI means adding non-standard steps to the JDK9 build system for building the relevant annotation processor. This is overkill since JVMCI itself only has these 3 providers (AArch64HotSpotJVMCIBackendFactory, AMD64HotSpotJVMCIBackendFactory and SPARCHotSpotJVMCIBackendFactory) for a single service (HotSpotJVMCIBackendFactory). What's more, its yet more code that needs to be taken into account should JVMCI be back-ported.
For the above reasons, this issue will remove ServiceProvider and ServiceProviderProcessor from JVMCI.
Having an annotation based mechanism in JVMCI means adding non-standard steps to the JDK9 build system for building the relevant annotation processor. This is overkill since JVMCI itself only has these 3 providers (AArch64HotSpotJVMCIBackendFactory, AMD64HotSpotJVMCIBackendFactory and SPARCHotSpotJVMCIBackendFactory) for a single service (HotSpotJVMCIBackendFactory). What's more, its yet more code that needs to be taken into account should JVMCI be back-ported.
For the above reasons, this issue will remove ServiceProvider and ServiceProviderProcessor from JVMCI.