From a couple of comments the properties associated with logging are confusing (and I completely agree with that). I believe these suggested new names are better and will make it easier for people to find the related logging properties in their IDE via autocomplete etc.
ServerConfig: Old property names -> New property names useJuliTransactionLogger -> loggingToJavaLogger transactionLogDirectory -> loggingDirectory transactionLogSharing -> loggingLogFileSharing transactionLogging -> loggingLevel iudLogLevel -> loggingLevelIud queryLogLevel -> loggingLevelQuery sqlQueryLogLevel -> loggingLevelSqlQuery transactionDebugLevel -> loggingLevelTxnCommit
The benefit I see with these property names is that someone goes "setLog" in their IDE and autocomplete will show the related "logging" properties. I also think it is easier way to see how the logging level properties are related (loggingLevel being the overall transaction logging level).
Additionally some of the enum names have been changed.
New names of Enum types. Old enums -> New enums TxLogSharing -> LogFileSharing TxLogLevel -> LogLevel TxDebugLevel -> LogLevelTxnCommit StmtLogLevel -> LogLevelStmt
Fixed in HEAD.
Setting these in ebean.properties
## Use java util logging to log transaction details #ebean.loggingToJavaLogger=true ## General logging level: (none, explicit, all) ebean.logging=all ## Sharing log files: (none, explicit, all) ebean.logging.logfilesharing=all ## location of transaction logs ebean.logging.directory=logs #ebean.logging.directory=${catalina.base}/logs/trans ## Specific Log levels (none, summary, binding, sql) ebean.logging.iud=sql ebean.logging.query=sql ebean.logging.sqlquery=sql ## Log level for txn begin, commit and rollback (none, debug, verbose) ebean.logging.txnCommit=none