Branch: refs/heads/7.4 Home: https://github.com/hibernate/hibernate-orm Commit: be356bf7230c97bca03628357e3f731073a574a3 https://github.com/hibernate/hibernate-orm/commit/be356bf7230c97bca036283... Author: Yoann Rodière <yoann(a)hibernate.org&gt; Date: 2026-07-31 (Fri, 31 Jul 2026) Changed paths: M tooling/hibernate-maven-plugin/src/main/java/org/hibernate/orm/tooling/maven/HibernateEnhancerMojo.java M tooling/hibernate-maven-plugin/src/test/java/org/hibernate/orm/tooling/maven/HibernateEnhancerMojoTest.java Log Message: ----------- HHH-20743 Use fileSet base directory for class name resolution in maven plugin determineClassName() was always using classesDirectory (default target/classes) as the base for deriving class names. When a fileSet pointed to a different directory (e.g. target/test-classes), the substring arithmetic stripped the wrong prefix, producing corrupted class names like "sses.org.hibernate.bugs.TestEntity". Track the base directory alongside each collected file using a SourceEntry record, and use Path.relativize() for class name resolution, consistent with the Gradle plugin's Helper.determineClassName(File root, File javaClassFile). Assisted-By: Claude Code <noreply(a)anthropic.com&gt; To unsubscribe from these emails, change your notification settings at https://github.com/hibernate/hibernate-orm/settings/notifications