|
From: Gerwin K. <ge...@do...> - 2018-10-09 22:21:41
|
Sounds very nice, I’m keen to try it out! > tl;dr: Please enable cirrus-ci <https://github.com/marketplace/cirrus-ci> on bazel_rules This is now done (I think) — please have a look and let me know if there is anything more that is needed. > 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. Let’s see how things go over time. We should probably consolidate and/or finish our current projects first, but over time it would be nice to migrate away from maven as the main build system. We’d still want to support it, of course, but not necessarily use it for building jflex itself. There’s no hurry, though. The current setup works, so we can focus on other things first. If we test multiple build systems for the examples, I’m now also more comfortable with removing the ant build for jflex itself to reduce complexity. Cheers, Gerwin |
