Consider japi-tracker integration into CI about scijava-scripts

[imagejan]

.. or revapi, as suggested by @ctrueden on the forum.

[imagejan]

Happy to see that @frauzufall and @ctrueden seem to be working on something similar at the KNIME hackathon 🙂
https://gitter.im/knime-ip/hackathon-KNIME-2019?at=5d8739ebab4244767be45619

[frauzufall]

Oh cool! On a first view the reports linked above look way better than what I tried.

[ctrueden]

Ah, thanks @imagejan, I had forgotten all about this. Sorry about that, @frauzufall. Was mostly @frauzufall working on it—I just posted a gist as a quick experiment to see if using javap directly would be reasonable. But of course a dedicated tool (not maintained by us) will be much better.

[frauzufall]

This might be simpler to integrate e.g. into the release script: https://revapi.org/modules/revapi-maven-plugin/. This plugin could also help us to make it impossible or very hard to break the API at all @ctrueden (thinking of the incubator strategy)

[imagejan]

revapi-maven-plugin looks great!

I suggest adding a section like this to <pluginManagement> in pom-scijava (or pom-scijava-base?):

			<plugin>
				<groupId>org.revapi</groupId>
				<artifactId>revapi-maven-plugin</artifactId>
				<version>0.11.4</version>
				<dependencies>
					<dependency>
						<groupId>org.revapi</groupId>
						<artifactId>revapi-java</artifactId>
						<version>0.20.2</version>
					</dependency>
				</dependencies>
				<executions>
					<execution>
						<goals>
							<goal>check</goal>
						</goals>
					</execution>
				</executions>
			</plugin>