You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When a config item like the database URL is modified in the rule configuration, enforcer outputs log information, but when the same config item is configured via a system property, there is no logging.
Worse still, if both values have been set, the database config from the rule is logged, but it is the system property which takes precedence!
By the way, you might find it helpful to integrate the logging for victims-lib-java and victims-enforcer.
zanata-maven-plugin uses com.pyx4j:maven-plugin-log4j plus org.slf4j:slf4j-log4j12to allow generic (non-Maven) code in zanata-client-commands to log to Maven's log system by using slf4j calls.
Regarding the integrated logging, it looks like this library might be a little simpler than combining com.pyx4j:maven-plugin-log4j with org.slf4j:slf4j-log4j12: http://slf4j.jcabi.com/
When a config item like the database URL is modified in the rule configuration, enforcer outputs log information, but when the same config item is configured via a system property, there is no logging.
Worse still, if both values have been set, the database config from the rule is logged, but it is the system property which takes precedence!
By the way, you might find it helpful to integrate the logging for
victims-lib-java
andvictims-enforcer
.zanata-maven-plugin
usescom.pyx4j:maven-plugin-log4j
plusorg.slf4j:slf4j-log4j12
to allow generic (non-Maven) code inzanata-client-commands
to log to Maven's log system by using slf4j calls.See https://github.com/zanata/zanata-client/blob/client-3.4.0/zanata-maven-plugin/src/main/java/org/zanata/maven/ConfigurableMojo.java#L106 for the setup code.
The text was updated successfully, but these errors were encountered: