|
From: Régis D. <de...@us...> - 2018-10-09 18:36:03
|
Hello Gerwin, hello all, *tl;dr: Please enable cirrus-ci <https://github.com/marketplace/cirrus-ci> on bazel_rules* Google open-sourced its build system, bazel <http://bazel.build/>, and it seems it is gaining in popularity. So I've decided to make a Bazel rule to invoke JFlex. I initially defined the rule in jflex/jlex/examples <https://github.com/jflex-de/jflex/tree/09959b62bd8a904d12fc2de4fe315d8f37467586/jflex/examples> but I'm going to simplify and remove most of the code there. Instead, I've created a new separate repo bazel_rules <https://github.com/jflex-de/bazel_rules> to host the rule (and a sample usage with hello world <https://github.com/jflex-de/bazel_rules/tree/master/java/jflex/examples/helloworld> app). People using the rule will transparently clone this repository, so I want to keep it minimal. Since I don't own the jflex-de organization, can you please enable cirrus-ci integration from marketplace <https://github.com/marketplace/cirrus-ci> for the bazel_rules repository. I prefer Cirrus over Travis because it natively offers Bazel. Also, I tried to make all JFlex build with Bazel (#304 <https://github.com/jflex-de/jflex/pull/304>). It has huge benefits. For instance, the regressions tests would take less than 500ms to run when you change a README file (because the results would be cached). It would also make things way more consistent. But it's a large migration effort (particularly because of the maven plugins) and it's not worth the effort, I think. It might be worth it for building the doc, because the source doesn't change often and it's a very isolated module. Thanks in advance, -- Régis -- -- Régis |
