spring-data-envers pulls in various javax and JBoss spec jars when their jakarta.* equivalents are preferred #331
Labels
for: team-attention
An issue we need to discuss as a team to make progress
status: waiting-for-triage
An issue we've not yet triaged
We had an initiative a few years ago across the Spring portfolio to consistently use jakarta.* spec jars. spring-data-envers has got out of step with this, pulling in the following:
javax.activation:javax.activation-api
javax.persistence:javax.persistence-api
javax.xml.bind:jaxb-api
org.jboss.spec.javax.transaction:jboss-transaction-api_1.2_spec
Could these please be excluded and their Jakarta equivalents depended upon instead?
The text was updated successfully, but these errors were encountered: