Exclude old artifactIds in favor of new ones

* javax.annotation:jsr250-api -> javax.annotation:javax.annotation-api
* javax.transaction:jta -> javax.transaction:javax.transaction-api

Unfortunately, this may result in runtime issues if the artifacts in
question (jetty-jspc-maven-plugin and omero-model, respectively) are
depended upon without the newer artifacts on the classpath as well.
But Maven does not have a built-in way to add dependencies to a managed
artifact, so what can you do? Maybe we add a smart dependency checking
step to scijava-maven-plugin the future to catch these sorts of things?

Author: ctrueden

pom.xml

@@ -2515,6 +2515,13 @@
 				<groupId>org.openmicroscopy</groupId>
 				<artifactId>omero-model</artifactId>
 				<version>${omero-model.version}</version>
+				<exclusions>
+					<exclusion>
+						<!-- Conflicts with javax.transaction:javax.transaction-api -->
+						<groupId>javax.transaction</groupId>
+						<artifactId>jta</artifactId>
+					</exclusion>
+				</exclusions>
 			</dependency>
 
 			<!-- OMERO Renderer - https://github.com/ome/omero-renderer -->
@@ -3399,6 +3406,13 @@
 				<groupId>org.eclipse.jetty</groupId>
 				<artifactId>jetty-jspc-maven-plugin</artifactId>
 				<version>${jetty-jspc-maven-plugin.version}</version>
+				<exclusions>
+					<exclusion>
+						<!-- Conflicts with javax.annotation:javax.annotation-api -->
+						<groupId>javax.annotation</groupId>
+						<artifactId>jsr250-api</artifactId>
+					</exclusion>
+				</exclusions>
 			</dependency>
 			<dependency>
 				<groupId>org.eclipse.jetty</groupId>