Describe the bug VaultEnvironmentRepositoryFactory is deprecated in its javadoc but it is not annotated with @Deprecated. This leads to an inconsistent view of whether or not the class is deprecated. From https://docs.oracle.com/javase/8/docs/technotes/guides/javadoc/deprecation/deprecation.html:

The Java Language Specification requires compilers to issue warnings when classes, methods, or fields marked with the @Deprecated annotation are used. Compilers are not required by the Java Language Specification to issue warnings when classes, methods, or fields marked with the @deprecated Javadoc tag are accessed, although the Sun compilers currently do so. However, there is no guarantee that the Sun compiler will always issue such warnings.

Depending on the compiler someone's using, they may not realise that VaultEnvironmentRepositoryFactory is deprecated.

This is causing a problem with AOT where Framework attempts to detect if generated code is calling deprecated APIs. It looks for the @Deprecated annotation and doesn't find it. This results in the AOT-generated code producing deprecation warnings which it tries to avoid.