[bp} Create tycho-baseline:check-dependencies mojo to validate versions

If version ranges on packages or bundles are used it is currently quite
hard to ensure these are actually work for the provided ranges
especially if they evolve over a long time.

This now adds a new tycho-baseline:check-dependencies mojo that can help
in this task by inspecting the byte-code of the project and the
dependencies if there is any inconsistency in any of the dependencies
matching the version range.

RELEASE_NOTES.md

@@ -42,6 +42,7 @@ This is now fixed, but might result in build previously working now fail due to
 
 backports:
 - Support for implicit dependencies in target definitions
+- Add tycho-baseline:check-dependencies mojo
 
 ## 4.0.10
 

pom.xml

@@ -511,6 +511,20 @@
 					<artifactId>maven-invoker-plugin</artifactId>
 					<version>3.9.0</version>
 				</plugin>
+				<plugin>
+		        	<groupId>org.eclipse.sisu</groupId>
+		        	<artifactId>sisu-maven-plugin</artifactId>
+		        	<version>${sisu-version}</version>
+		        	<executions>
+			          <execution>
+			            <id>index-project</id>
+			            <goals>
+			              <goal>main-index</goal>
+			              <goal>test-index</goal>
+			            </goals>
+			          </execution>
+			        </executions>
+	            </plugin>
 			</plugins>
 		</pluginManagement>
 	</build>

tycho-baseline-plugin/pom.xml

@@ -53,13 +53,27 @@
 			<artifactId>asciitable</artifactId>
 			<version>0.3.2</version>
 		</dependency>
+		<dependency>
+			<groupId>org.ow2.asm</groupId>
+			<artifactId>asm</artifactId>
+			<version>9.7.1</version>
+		</dependency>
+		<dependency>
+			<groupId>org.eclipse.emf</groupId>
+			<artifactId>org.eclipse.emf.ecore</artifactId>
+			<version>2.38.0</version>
+		</dependency>
 	</dependencies>
 	<build>
 		<plugins>
 			<plugin>
 				<groupId>org.codehaus.plexus</groupId>
 				<artifactId>plexus-component-metadata</artifactId>
 			</plugin>
+			<plugin>
+				<groupId>org.eclipse.sisu</groupId>
+				<artifactId>sisu-maven-plugin</artifactId>
+			</plugin>
 			<plugin>
 				<groupId>org.apache.maven.plugins</groupId>
 				<artifactId>maven-plugin-plugin</artifactId>