Any sense in separating mapping annotations from the rest of the API?

[rbygrave]

So given the package change to jakarta.persistence I wonder if this is an opportunity to separate the mapping annotations:

• from the rest of the API as a separate artifact?
• in the same artifact but under a mapping package?

That is part of me wonders if in moving forward it would be useful to separate the mapping annotations such that mapping changes / improvements could be released more easily / frequently? (It might be easier to get agreement on mapping improvements separately from other API improvements?).

Just a thought but given the package change it seems like an opportunity to consider it.

(Maybe this has been discussed in email so I'll go and have a look / search - apologies if it's already been discussed).

Cheers, Rob.