-
Notifications
You must be signed in to change notification settings - Fork 16
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Consider japi-tracker integration into CI #27
Comments
.. or |
Happy to see that @frauzufall and @ctrueden seem to be working on something similar at the KNIME hackathon 🙂 |
Oh cool! On a first view the reports linked above look way better than what I tried. |
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 |
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) |
I suggest adding a section like this to
|
Consider integration of
japi-tracker
in continuous integration to monitor the API state of all components managed on the SciJava/ImageJ maven repository. The reports could be hosted as static webpages similar to the javadoc, e.g. atapi-history.scijava.org
or some such.For libraries released to Maven Central, the reports exist here:
The text was updated successfully, but these errors were encountered: