[hibernate-issues] [JIRA] (HHH-16255) Logging "Executing import script" when it's not being executed

Sanne Grinovero ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=557058%... ) *created* an issue Hibernate ORM ( https://hibernate.atlassian.net/browse/HHH?atlOrigin=eyJpIjoiNTU3NWNiNjI0... ) / Bug ( https://hibernate.atlassian.net/browse/HHH-16255?atlOrigin=eyJpIjoiNTU3NW... ) HHH-16255 ( https://hibernate.atlassian.net/browse/HHH-16255?atlOrigin=eyJpIjoiNTU3NW... ) Logging "Executing import script" when it's not being executed ( https://hibernate.atlassian.net/browse/HHH-16255?atlOrigin=eyJpIjoiNTU3NW... ) Issue Type: Bug Affects Versions: 6.2.0.CR3 Assignee: Unassigned Components: hibernate-core Created: 06/Mar/2023 03:31 AM Priority: Major Reporter: Sanne Grinovero ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=557058%... ) The CoreMessageLogger# executingImportScript currently generates this message: Executing import script '%s' However this is being logged each time a ScriptSourceInput instance is created by parsing a provided script - it’s not being executed yet at the time the message is logged. This log has proved confusing with external integrations, e.g. the Quarkus DevUI does invoke the schema tool to generate scripts to be shown in the UI but it’s not “executing” them on the DB. This effectively results in seeing the “Executing import script” INFO log message twice when both the DevUI are activated and the schema tool is run by ORM initialization. I think we should either clarify the message, or only log “Executing” when it’s being performed on the target DB. ( https://hibernate.atlassian.net/browse/HHH-16255#add-comment?atlOrigin=ey... ) Add Comment ( https://hibernate.atlassian.net/browse/HHH-16255#add-comment?atlOrigin=ey... ) Get Jira notifications on your phone! Download the Jira Cloud app for Android ( https://play.google.com/store/apps/details?id=com.atlassian.android.jira.... ) or iOS ( https://itunes.apple.com/app/apple-store/id1006972087?pt=696495&ct=Em... ) This message was sent by Atlassian Jira (v1001.0.0-SNAPSHOT#100217- sha1:f4229d0 )