A user reports problems with a secured JFrog repository. When making compiles from a terminal in the workspace, things can be made to work by changing Maven's settings.xml (to point to JFrog, not Maven Central) and by providing command line flags to include an SSL certificate for JFrog. The CLI compile works.

The IDE fails, though. It seems the Language Server uses it's own settings for Maven and these do not include the changed settings.xml or the flags for the certificates.

The result is a compile failure, sometimes unrequested from the user. (i.e. when a new workspace is made and a project is imported. A compile is started automatically, this is doomed to failure.)

Please make some provision so a secured corporate artifact repository can be used.