Since HHH-8122, the values of javax.persistence.jdbc.password and hibernate.connection.password are "masked" with ****.
This breaks components re-using that information for data initialization etc.
In my case it is a JUnit rule which triggers Liquibase. In that test scenario, the password is not sensitive at all!
Please introduce a new EMF property to control whether or not to "scrub" settings (default value can be true).