Client configuration should prefer system properties

[yahavi]

• [x] All tests passed. If this feature is not already covered by the tests, I added new tests.

Fix https://github.com/jfrog/jfrog-cli/issues/2373

The setup for the client should prioritize Java system properties over the default properties set by the JFrog CLI. Take this command, for instance, where the JFrog CLI specifies artifactory.publish.artifacts=true, but a conflicting false value is set by a system property:

jf mvn clean install -Dartifactory.publish.artifacts=false

In this case, the system property should take precedence over the default value from the JFrog CLI.

[github-actions[bot]]

[](https://docs.jfrog-applications.jfrog.io/jfrog-applications/frogbot)

---

[🐸 JFrog Frogbot](https://docs.jfrog-applications.jfrog.io/jfrog-applications/frogbot)