Gavin King ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=557058%... ) *created* an issue Hibernate ORM ( https://hibernate.atlassian.net/browse/HHH?atlOrigin=eyJpIjoiODRiOThkYzBj... ) / Deprecation ( https://hibernate.atlassian.net/browse/HHH-15788?atlOrigin=eyJpIjoiODRiOT... ) HHH-15788 ( https://hibernate.atlassian.net/browse/HHH-15788?atlOrigin=eyJpIjoiODRiOT... ) deprecate GenerationTime ( https://hibernate.atlassian.net/browse/HHH-15788?atlOrigin=eyJpIjoiODRiOT... ) Issue Type: Deprecation Assignee: Unassigned Components: hibernate-core Created: 30/Nov/2022 10:07 AM Priority: Major Reporter: Gavin King ( https://hibernate.atlassian.net/secure/ViewProfile.jspa?accountId=557058%... ) I have been trying my hardest to ignore that we have both GenerationTime and, in another package, GenerationTiming , the two enums being isomorphic and differing only by an ing. But today I noticed that GenerationTime isn’t even used consistently in its own package. @CurrenTimestamp is defined in terms of GenerationTiming. So this is super-confusing, and it’s time we deprecate one of them. The obvious candidate is GenerationTime , since GenerationTiming us used by all the value generation stuff. On the other hand, GenerationTiming is in the org.hibernate.tuple package, my least-favorite package, so it’s not quite perfect either. Anyway one of them has to go. ( https://hibernate.atlassian.net/browse/HHH-15788#add-comment?atlOrigin=ey... ) Add Comment ( https://hibernate.atlassian.net/browse/HHH-15788#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#100210- sha1:fb625d0 )