[BUG] azure-core/native-image.properties has too many entries with wide implications

[credmond]

https://github.com/Azure/azure-sdk-for-java/blob/main/sdk/core/azure-core/src/main/resources/META-INF/native-image/com.azure/azure-core/native-image.properties

I feel this file has too many build-time initialisations, SLF4J, etc.

This forces client projects of this library, who want to build a native image, to make every class that a logging provider ultimately reaches during initialisation (which can be a lot of classes), to be build-time too. There are some reasons why this can be a) impossible with GraalVM or b) cause other unacceptable problems.

Not everyone uses logback, and the other logging frameworks might cause problems.

[github-actions]

Thank you for your feedback. Tagging and routing to the team member best able to assist.

[alzimmermsft]

Thank you for filing this issue @credmond

@srnagar could you look into why the logback classes were added there even though we don't formally use logback as a dependency ourselves.

[credmond]

I described the problem in more detail here on GraalVM: oracle/graal#10201

I feel like you might have added so many build-time configs to this project because of issues with netty. Basically, GraalVM choosing safe classes as build-time safe causes errors about your classes not being build-time, etc, etc.

In my view, the fix is to actually force such classes to be run-time as much as possible, instead of making your classes build-time. The former is an approach you see some people using.

As it stands, for me to use your library, I need to fork it, and change the settings to be run-time, not build-time, build the JAR and use that.