first of all, the "RevisionEntity" is global - you can have only one, and it's created whenever a versioned class changes. (In the future, you'll be able to have severl revision entities, by having severl "revisioning groups").
So you don't want to track the changes to your data, just capture the meta-data (date, user, etc?)?
The most recent version is always in the (original) entities - so I don't quite understand what you mean here?
Sorry for the late response...I must have forgotten to check for email notifications on a reply.
Essentially, I'd like to use a "plug-in-play" versioning system but I don't need to actually compare data between versions. All I care about from one entity version to another is who made the change (i.e. a User) and when (i.e. a Date/Time). That's all I essentially care about in our specific use case.
I'd like to better understand whether Envers is something that should be used for this use case.
you can use Envers here - however I'm not sure if it won't be a bit of an overkill.
The solution would be to version no fields in each entity (except the ID), and create a custom revision entity, which would hold the username (and date, which is held by default anyway). Then, you could retrieve the revision entity + modified entity pairs witha revisions-of-entity query.
Thank you - this is the kind of information I wanted to know in order to determine if Envers was right for my project. I appreciate your time. I might give it a go and do exactly as you said...