> If I recall correctly, some MicroProfile specifications had troubles with keeping those annotations up to date,
I am not sure what you meant. I tried to keep the plugin up to date. Besides, as long as the plugin does the job, it is good enough. Once it is in place, you don't need to update it. It will keep running and break the build if any backward incompatible changes got it without acknowledging with the major version changes.
I don't think not understanding it is a valid reason to ignore it. It is pretty straightforward to grasp it if people are willing to learn. I am sure BJ on cc can do a talk on it.
Tangent: if there's a spec (such as Transactions) struggling to figure out the impact of CDI's breaking changes, they should reach out to CDI. I'm sure we'd be glad to help. (My hunch is that they're not affected at all, because the only thing from JTA that depends on CDI is @Transactional and @TransactionScoped, but I didn't really look.)
It is true to talk to a different community to learn more. However, if the artifacts can be self explanatory, it is much more scable. Besides, for figuring out backward incompatible changes, I am afraid it is not trivial sometimes.
Emily