Open adammead opened 1 year ago
This issue is caused by the use of the Annotations to set up the UI instead of using the ConfigurationDeclarer to declare the UI manually. We were trying to make this module too similar to the Vault Connector.
See the sample, decompile the Secure Properties Provider, or check out the Cyberark custom properties provider or Enhanced Mule Properties module. These are all setting up the UIs manually. We just need to replicate what we've been doing with annotations by using the ConfigurationDeclarer instead.
Branch feature/issue25 has some sample changes that were used to test this.
When building applications that use the mule-vault-properties-provider, an error is received when using mule-maven-plugin version 3.6.0 and above. The error is:
Execution default-process-classes of goal org.mule.tools.maven:mule-maven-plugin:3.6.3:process-classes failed: org.mule.tooling.api.ToolingException: java.lang.ArrayStoreException: sun.reflect.annotation.TypeNotPresentExceptionProxy
Full
mvn package -e
output from a simple project: