On Wed, Mar 23, 2016 at 12:36 PM, Vincent Massol <[email protected]> wrote:
Hi devs,
I’ve been thinking about how to improve our release process regarding the backward compat checks (we were using clirr for this and now revapi).
In short the idea is:
* Store the revapi config (containing the list of breakages to ignore) in a wiki page on xwiki.org, associated with a given release note. For example in ReleaseNotes.BackwardCompatibilityForXWiki${xwiki.version.major}${xwiki.version.minor} (using http://www.mojohaus.org/build-helper-maven-plugin/parse-version-mojo.html) * Configure our build to download that json file and store it in target/ for revapi, see https://github.com/revapi/revapi/issues/31#issuecomment-200286810
* Work on making it not fail the build when offline (see https://github.com/revapi/revapi/issues/31#issuecomment-200286810)
download-maven-plugin is caching the downloaded files by default (I'm using it to download the CKEditor sources only once). I guess we won't be able to use this feature because the revapi config can be modified multiple times during a release dev. Unless we modify the URL in the pom whenever we modify the wiki page (instead of modifying the URL only after each release).
* Write some groovy script in the release notes template page to automatically generate the “API Breakage” section from the parsed json from ReleaseNotes.BackwardCompatibilityForXWiki${xwiki.version.major}${xwiki.version.minor}
WDYT?
Sound good. I'm only worried about the offline build issue. Thanks, Marius
Thanks -Vincent
_______________________________________________ devs mailing list [email protected] http://lists.xwiki.org/mailman/listinfo/devs