jflex-devel Mailing List for JFlex (Page 2)
The fast lexer generator for Java
Brought to you by:
lsf37,
steve_rowe
Menu
▾
▴
jflex-devel — developers mailing list for JFlex
You can subscribe to this list here.
| 2008 |
Jan
(11) |
Feb
(17) |
Mar
(18) |
Apr
(4) |
May
(15) |
Jun
|
Jul
|
Aug
(5) |
Sep
|
Oct
|
Nov
|
Dec
(2) |
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| 2009 |
Jan
(11) |
Feb
(21) |
Mar
(3) |
Apr
|
May
|
Jun
(8) |
Jul
(5) |
Aug
(24) |
Sep
(8) |
Oct
(5) |
Nov
(23) |
Dec
|
| 2010 |
Jan
|
Feb
|
Mar
|
Apr
(5) |
May
(5) |
Jun
(2) |
Jul
(2) |
Aug
|
Sep
|
Oct
(10) |
Nov
|
Dec
|
| 2011 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
(8) |
Jul
|
Aug
|
Sep
(2) |
Oct
|
Nov
|
Dec
(1) |
| 2012 |
Jan
(2) |
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
(3) |
Sep
|
Oct
|
Nov
|
Dec
|
| 2013 |
Jan
|
Feb
(1) |
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
(19) |
Oct
(26) |
Nov
(5) |
Dec
(4) |
| 2014 |
Jan
(20) |
Feb
(15) |
Mar
(14) |
Apr
|
May
(6) |
Jun
(28) |
Jul
|
Aug
(2) |
Sep
|
Oct
|
Nov
|
Dec
|
| 2015 |
Jan
(3) |
Feb
(4) |
Mar
(4) |
Apr
(18) |
May
|
Jun
(2) |
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
| 2016 |
Jan
|
Feb
(3) |
Mar
(2) |
Apr
(1) |
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
| 2017 |
Jan
|
Feb
(1) |
Mar
(4) |
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
(10) |
Dec
(1) |
| 2018 |
Jan
|
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
(7) |
Oct
(18) |
Nov
|
Dec
|
| 2019 |
Jan
(4) |
Feb
|
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
(2) |
Dec
(9) |
| 2020 |
Jan
|
Feb
(5) |
Mar
|
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
| 2021 |
Jan
|
Feb
(1) |
Mar
(1) |
Apr
|
May
|
Jun
|
Jul
|
Aug
|
Sep
|
Oct
|
Nov
|
Dec
|
|
From: Régis D. <re...@de...> - 2018-10-22 17:28:54
|
I think I have my answer on https://status.github.com/messages October 22, 2018 18:51 Central European Summer TimeWe have resumed Pages builds and will continue to monitor as we process a delayed backlog of events. 18:45 Central European Summer TimeWe have resumed delivery of webhooks and will continue to monitor as we process a delayed backlog of events. 18:24 Central European Summer TimeWe've completed validation of data consistency and have enabled some background jobs. We're continuing to monitor as the system recovers and expect to resume delivering webhooks at 16:45UTC. 17:09 Central European Summer TimeBackground jobs remain paused as we near completion of validation of data consistency. 15:18 Central European Summer TimeWe are validating the consistency of information across all data stores. Webhooks and Pages builds remain paused. 13:56 Central European Summer TimeThe majority of restore processes have completed. We anticipate all data stores will be fully consistent within the next hour. 11:47 Central European Summer TimeWe continue to monitor restores which are taking longer than anticipated. We estimate they will be caught up in an hour and a half. 10:19 Central European Summer TimeOur restore operations are still on track to serve consistent data within the hour. We've posted an update at https://blog.github.com/2018-10-21-october21-incident-report/. 09:35 Central European Summer TimeOur restore operations are proceeding as expected, on track for serving fully consistent data within the next 1.5 hours. 08:51 Central European Summer TimeWe are currently in the later stages of a restore operation, with the aim of serving fully consistent data within the next 2 hours. 08:18 Central European Summer TimeWe continue work to repair a data storage system for GitHub.com. You may see inconsistent results during this process. 07:05 Central European Summer TimeWe continue working to repair a data storage system for GitHub.com. You may see inconsistent results during this process. 06:12 Central European Summer TimeWe are continuing work to repair a data storage system for GitHub.com. You may see inconsistent results during this process. 05:28 Central European Summer TimeWe continue working to repair a data storage system for GitHub.com. You may see inconsistent results during this process. 05:00 Central European Summer TimeWe are continuing to repair a data storage system for GitHub.com. You may see inconsistent results during this process. 04:42 Central European Summer TimeWe continue to repair a data storage system for GitHub.com. You may see inconsistent results during this process. 04:23 Central European Summer TimeWe are continuing to repair a data storage system for GitHub.com. You may see inconsistent results during this process. 04:01 Central European Summer TimeWe continue work to repair a data storage system for GitHub.com. You may see inconsistent results during this process. 03:41 Central European Summer TimeWe are continuing to work to migrate a data storage system in order to restore access to GitHub.com. 03:22 Central European Summer TimeWe continue to work to migrate a data storage system in order to restore access to GitHub.com. 03:02 Central European Summer TimeWe continue to migrate a data storage system in order to restore full access to GitHub.com. 02:43 Central European Summer TimeWe continue to work on migrating a data storage system in order to restore access to GitHub.com. 02:23 Central European Summer TimeWe're continuing to work on migrating a data storage system in order to restore access to GitHub.com. 02:05 Central European Summer TimeWe're failing over a data storage system in order to restore access to GitHub.com. 01:43 Central European Summer TimeWe're investigating problems accessing GitHub.com. 01:13 Central European Summer TimeWe are investigating reports of service unavailability. 01:09 Central European Summer TimeWe are investigating reports of elevated error rates. 2018-10-22 19:25 GMT+02:00 Régis Décamps <re...@de...>: > Gerwin, > > Have-you changed something in the GitHub integration/webhooks? Nothing is > triggering (no travis, no cirrus, no lgtm). If it's not you, then it's an > outage aat GitHub > > -- > Régis Décamps > > http://regis.decamps.info/ > -- Régis Décamps http://regis.decamps.info/ |
|
From: Régis D. <re...@de...> - 2018-10-22 17:26:39
|
Gerwin, Have-you changed something in the GitHub integration/webhooks? Nothing is triggering (no travis, no cirrus, no lgtm). If it's not you, then it's an outage aat GitHub -- Régis Décamps http://regis.decamps.info/ |
|
From: Régis D. <re...@go...> - 2018-10-18 20:15:39
|
Hello Gerwin, How do you feel about making a proposal for a summer of code project (hence for next summer, but applications will be until Jan 2019 I assume). The idea of summer of code (g.co/gsoc <https://summerofcode.withgoogle.com/>) is to offer students an opportunity to contribute to an open-source project for 3 months and even get paid by Google in return. I think we could offer a very nice project, for instance: - refactor the code to have an AST. Stretch: produce code from this AST, rather than with println() - support antlr - have our own parser generator - revamp the syntax of the lexer specification. Any other idea? For instance, those were the proposals for gRPC <https://github.com/grpc/grpc/blob/master/summerofcode/ideas.md> or proposal for a compiler in open-chemistry <https://gist.github.com/kunalsharma05/c95b1d53ed1bcdf347fb0cbf43d0c014> What do you think? -- Régis Google Lens |
|
From: Gerwin K. <ge...@do...> - 2018-10-17 10:12:24
|
No worries! Cheers, Gerwin > On 17.10.2018, at 20:39, Régis Décamps <de...@us...> wrote: > > Nope, I'm good. I just noticed today it was enabled indeed. Sorry for the noise. > > > Le mer. 17 oct. 2018 à 09:09, Gerwin Klein <ge...@do... <mailto:ge...@do...>> a écrit : > >> On 17 Oct 2018, at 07:08, Régis Décamps via Jflex-devel <jfl...@li... <mailto:jfl...@li...>> wrote: >> >> Can you also enable Cirrus-CI on the main JFlex repo. I'm curious to compare their respective build times. > > Cirrus-CI should already be enabled for all jflex-de org repos. Is there anything you need me to do in addition? > > >> I’m now also more comfortable with removing the ant build for jflex itself to reduce complexity. >> >> And that's done in #432 <https://github.com/jflex-de/jflex/pull/432> > > Yup, thanks for that. > > Cheers, > Gerwin > > -- > -- > Régis > |
|
From: Régis D. <re...@de...> - 2018-10-17 09:48:15
|
https://sourceforge.net/p/jflex/mailman/ was failing yesterday with a 503 and now works. So it was a temporary sf outage. Le mer. 17 oct. 2018 à 09:11, Gerwin Klein <ge...@do...> a écrit : > > On 17 Oct 2018, at 07:11, Régis Décamps <re...@de...> wrote: > > Just curious: did you announce 1.7.0, on the mailing list? > > > Yes, it went out on jflex announce. > > Does this page work for you? > https://sourceforge.net/p/jflex/mailman/message/36421574/ (If no, I can > forward to jflex-devel if you want) > > Cheers, > Gerwin > > _______________________________________________ > Jflex-devel mailing list > Jfl...@li... > https://lists.sourceforge.net/lists/listinfo/jflex-devel > -- -- Régis |
|
From: Régis D. <de...@us...> - 2018-10-17 09:40:01
|
Nope, I'm good. I just noticed today it was enabled indeed. Sorry for the noise. Le mer. 17 oct. 2018 à 09:09, Gerwin Klein <ge...@do...> a écrit : > > On 17 Oct 2018, at 07:08, Régis Décamps via Jflex-devel < > jfl...@li...> wrote: > > Can you also enable Cirrus-CI on the main JFlex repo. I'm curious to > compare their respective build times. > > > Cirrus-CI should already be enabled for all jflex-de org repos. Is there > anything you need me to do in addition? > > > I’m now also more comfortable with removing the ant build for jflex itself >> to reduce complexity. >> > > And that's done in #432 <https://github.com/jflex-de/jflex/pull/432> > > > Yup, thanks for that. > > Cheers, > Gerwin > > -- -- Régis |
|
From: Gerwin K. <ge...@do...> - 2018-10-17 07:11:39
|
> On 17 Oct 2018, at 07:11, Régis Décamps <re...@de...> wrote: > > Just curious: did you announce 1.7.0, on the mailing list? Yes, it went out on jflex announce. Does this page work for you? https://sourceforge.net/p/jflex/mailman/message/36421574/ <https://sourceforge.net/p/jflex/mailman/message/36421574/> (If no, I can forward to jflex-devel if you want) Cheers, Gerwin |
|
From: Gerwin K. <ge...@do...> - 2018-10-17 07:09:56
|
> On 17 Oct 2018, at 07:08, Régis Décamps via Jflex-devel <jfl...@li...> wrote: > > Can you also enable Cirrus-CI on the main JFlex repo. I'm curious to compare their respective build times. Cirrus-CI should already be enabled for all jflex-de org repos. Is there anything you need me to do in addition? > I’m now also more comfortable with removing the ant build for jflex itself to reduce complexity. > > And that's done in #432 <https://github.com/jflex-de/jflex/pull/432> Yup, thanks for that. Cheers, Gerwin |
|
From: Régis D. <re...@de...> - 2018-10-16 20:11:26
|
Gerwin, Just curious: did you announce 1.7.0, on the mailing list? Sourceforge broke their own archive page, so I can't check on https://sourceforge.net/p/jflex/mailman/jflex-announce/ (and I assumed I would be aware, so I didn't subscribe myself) -- Régis -- -- Régis |
|
From: Régis D. <de...@us...> - 2018-10-16 20:08:42
|
Gerwin, Can you also enable Cirrus-CI on the main JFlex repo. I'm curious to compare their respective build times. Le mer. 10 oct. 2018 à 00:21, Gerwin Klein <ge...@do...> a écrit : > 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. > Indeed, thanks. > I’m now also more comfortable with removing the ant build for jflex itself > to reduce complexity. > And that's done in #432 <https://github.com/jflex-de/jflex/pull/432> -- Régis -- -- Régis |
|
From: Gerwin K. <ge...@do...> - 2018-10-09 22:40:25
|
> On 7 Oct 2018, at 9:02 pm, Régis Décamps <re...@de...> wrote: > > Hello Gerwin, > > Le jeu. 9 nov. 2017 à 23:10, Gerwin Klein <ge...@do... <mailto:ge...@do...>> a écrit : >> On 10.11.2017, at 00:46, Régis Décamps via Jflex-devel <jfl...@li... <mailto:jfl...@li...>> wrote: >> >> Hello all, >> >> I've accidentally submitted to master a couple of times. >> >> Github has a nice feature to protect branches. How do you feel about protecting master <https://github.com/jflex-de/jflex/settings/branches/master>? >> >> I propose to restrict master to PR only ; and we can even enforce CI status check as well <https://help.github.com/articles/enabling-required-status-checks/>. > > I’d be happy with that. > > Just to close the loop, I think I feel very happy with the protection of the branches. Yes, I agree, this has worked quite nicely. > Also the status check from Travis comes fast enough and provides a nice safety bet. I feel almost in the same environment than at work. :-) > I tentatively enabled a more restrictive "Require branches to be up to date before merging". It was annoying. You have to press the merge button and wait again. If you submit multiple things, it's really annoying that you need to press "Merge". I think it would be nice if github had auto-merge, but until then,I dislike this protection. I’m happy either way. It’s Ok to leave that one off, I don’t think we’ve had a test failure yet that was caused by a merge itself. We will probably get one at some point, but I don’t think that’s a big problem. > Now, as you can read in #410 <https://github.com/jflex-de/jflex/pull/410> I'm experimenting with a few code quality services. I really like Semmle lgtm.com <lgtm.comhttps://lgtm.com/projects/g/jflex-de/jflex> the most so far. Yes, this one looks fairly nice. >> >> Also, I personally feel that the cleanest way to integrate the branch is to "Squash and merge", but that's a slightly different topic. > > The merge pattern depends for me. I like topical commits that pertain to one specific thing. A pull request is often just one of these, then squash and merge is good, but it’s also reasonably common that there are multiple things on one theme that each make sense on their own in a PR, and then I’d usually prefer rebase and merge. I do tend towards smaller commits myself, but I don’t think everyone has to do that. > > The advantage of smaller topical commits is that you can isolate features and still revert/reorder things afterwards if necessary, e.g. when you later figure out that some feature doesn’t quite interact so well with the rest and you have to remove or change it. > > I still prefer the squash ; I believe a PR should be topical in the first place. I think commits should also be topical (potentially smaller units than a PR), but I’m not really opposed to squashing. My usual process is it have potentially messy commits on a feature branch first until I’m reasonably happy with the result, and then clean up the commits into more logical units for a PR, then rebase for the merge. It mostly depends on the size of the PR if that makes sense or not. I’m also quite fine with work-in-progress commits on the PR and then squash at the end if the entire thing is small enough for a single commit. We could just go with both, depending what the person who submits and merges the PR prefers. > I really dislike the standard merge commit. It creates a complex history that shows the temporary feature branch.<Screen Shot 2018-10-07 at 11.57.50.png> > (I think merge makes more sense in case you merge a maintenance branch into master/devel branch). I completely agree with that. The recent merge commit that sneaked in was just me clicking the wrong button on GitHub. Cheers, Gerwin |
|
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 |
|
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 |
|
From: Régis D. <re...@de...> - 2018-10-07 10:02:51
|
Hello Gerwin, Le jeu. 9 nov. 2017 à 23:10, Gerwin Klein <ge...@do...> a écrit : > On 10.11.2017, at 00:46, Régis Décamps via Jflex-devel < > jfl...@li...> wrote: > > Hello all, > > I've accidentally submitted to master a couple of times. > > Github has a nice feature to protect branches. How do you feel about protecting > master <https://github.com/jflex-de/jflex/settings/branches/master>? > > I propose to restrict master to PR only ; and we can even enforce CI status > check as well > <https://help.github.com/articles/enabling-required-status-checks/>. > > > I’d be happy with that. > Just to close the loop, I think I feel very happy with the protection of the branches. Also the status check from Travis comes fast enough and provides a nice safety bet. I feel almost in the same environment than at work. I tentatively enabled a more restrictive "Require branches to be up to date before merging". It was annoying. You have to press the merge button and wait again. If you submit multiple things, it's really annoying that you need to press "Merge". I think it would be nice if github had auto-merge, but until then,I dislike this protection. Now, as you can read in #410 <https://github.com/jflex-de/jflex/pull/410> I'm experimenting with a few code quality services. I really like Semmle lgtm.com <lgtm.comhttps://lgtm.com/projects/g/jflex-de/jflex> the most so far. > Also, I personally feel that the cleanest way to integrate the branch is > to "Squash and merge", but that's a slightly different topic. > > > The merge pattern depends for me. I like topical commits that pertain to > one specific thing. A pull request is often just one of these, then squash > and merge is good, but it’s also reasonably common that there are multiple > things on one theme that each make sense on their own in a PR, and then I’d > usually prefer rebase and merge. I do tend towards smaller commits myself, > but I don’t think everyone has to do that. > > The advantage of smaller topical commits is that you can isolate features > and still revert/reorder things afterwards if necessary, e.g. when you > later figure out that some feature doesn’t quite interact so well with the > rest and you have to remove or change it. > I still prefer the squash ; I believe a PR should be topical in the first place. I really dislike the standard merge commit. It creates a complex history that shows the temporary feature branch.[image: Screen Shot 2018-10-07 at 11.57.50.png] (I think merge makes more sense in case you merge a maintenance branch into master/devel branch). If the initial PR has only one commit or if the few commits are very topical, I like rebase and merge. In all other situations, squash is my favourite strategy. Régis -- -- Régis |
|
From: Régis D. <re...@de...> - 2018-10-05 18:22:21
|
Hello Gerwin, hello all, The current logo is clean ; but minimalist and a bit sad with the grey colour. Please find a few explorations for a new logo <https://docs.google.com/presentation/d/1vu7irmVJgQTd5yldR7cRQdRrsmnSOOIdlYRpcR05tbA> ; let me know what you think! -- Régis |
|
From: Gerwin K. <ge...@do...> - 2018-09-22 01:55:48
|
:-) Thanks for all your help on this one! In the end it turned out I just needed enough uninterrupted time to read enough of the maven docs to get the deployment working properly again. Cheers, Gerwin > On 22.09.2018, at 08:53, Régis Décamps <re...@de...> wrote: > > Hooray for releasing v1.7 🚀 > > > Le ven. 14 sept. 2018 à 10:05, Régis Décamps <re...@de... <mailto:re...@de...>> a écrit : > Cool, thanks! > > 2018-09-13 12:43 GMT+02:00 Gerwin Klein <ge...@do... <mailto:ge...@do...>>: > Hi Régis, > > I’ll have a look at how far I get with publishing the release on the weekend! > > Cheers, > Gerwin > > >> On 12.09.2018, at 02:29, Régis Décamps <re...@de... <mailto:re...@de...>> wrote: >> >> Hey Gerwin, >> >> Can you publish the 1.7.0 release? >> >> Once the cut is done, I'll feel more confident to make the changes for multi-threading (which are not trivial). >> >> Also, shall we consider dripping the jdk7 in Travis? In the worse case, we can use the -target version of javac to keep building for Java 7. >> >> -- >> Régis >> >> Le mar. 19 déc. 2017 à 11:17, Gerwin Klein <ge...@do... <mailto:ge...@do...>> a écrit : >> Looks like I didn’t get anything done at all in the week I thought I had. I’m fine with making it a smaller release, but I’m off travelling again from tomorrow, so my part at least will have to wait until early Jan. >> >> Cheers, >> Gerwin >> >>> On 25.11.2017, at 22:34, Régis Décamps <re...@de... <mailto:re...@de...>> wrote: >>> >>> I'd be happy to have a release, even if it's not huge. I'll feel more confident to have thread-safety in 1.7.1, for instance. >>> >>> >>> 2017-11-22 12:04 GMT+01:00 Gerwin Klein <ge...@do... <mailto:ge...@do...>>: >>> Hi Régis, Steve, >>> >>> just wanted to let you know that I’ll be away the next 3 weeks, but I think we might still manage a release before Christmas (or early next year if we miss Christmas). >>> >>> It looks like things are coming together and it would be good to use the momentum. >>> >>> What do you think? >>> >>> Cheers, >>> Gerwin >>> >>> >>> ------------------------------------------------------------------------------ >>> Check out the vibrant tech community on one of the world's most >>> engaging tech sites, Slashdot.org <http://slashdot.org/>! http://sdm.link/slashdot <http://sdm.link/slashdot> >>> _______________________________________________ >>> Jflex-devel mailing list >>> Jfl...@li... <mailto:Jfl...@li...> >>> https://lists.sourceforge.net/lists/listinfo/jflex-devel <https://lists.sourceforge.net/lists/listinfo/jflex-devel> >>> >>> >>> >>> -- >>> Régis Décamps >>> >>> http://regis.decamps.info/ <http://regis.decamps.info/>------------------------------------------------------------------------------ >>> Check out the vibrant tech community on one of the world's most >>> engaging tech sites, Slashdot.org <http://slashdot.org/>! http://sdm.link/slashdot_______________________________________________ <http://sdm.link/slashdot_______________________________________________> >>> Jflex-devel mailing list >>> Jfl...@li... <mailto:Jfl...@li...> >>> https://lists.sourceforge.net/lists/listinfo/jflex-devel <https://lists.sourceforge.net/lists/listinfo/jflex-devel> >> >> ------------------------------------------------------------------------------ >> Check out the vibrant tech community on one of the world's most >> engaging tech sites, Slashdot.org <http://slashdot.org/>! http://sdm.link/slashdot <http://sdm.link/slashdot>_______________________________________________ >> Jflex-devel mailing list >> Jfl...@li... <mailto:Jfl...@li...> >> https://lists.sourceforge.net/lists/listinfo/jflex-devel <https://lists.sourceforge.net/lists/listinfo/jflex-devel> >> -- >> -- >> Régis >> >> _______________________________________________ >> Jflex-devel mailing list >> Jfl...@li... <mailto:Jfl...@li...> >> https://lists.sourceforge.net/lists/listinfo/jflex-devel <https://lists.sourceforge.net/lists/listinfo/jflex-devel> > > > > _______________________________________________ > Jflex-devel mailing list > Jfl...@li... <mailto:Jfl...@li...> > https://lists.sourceforge.net/lists/listinfo/jflex-devel <https://lists.sourceforge.net/lists/listinfo/jflex-devel> > > > > > -- > Régis Décamps > > http://regis.decamps.info/ <http://regis.decamps.info/>-- > -- > Régis > > _______________________________________________ > Jflex-devel mailing list > Jfl...@li... > https://lists.sourceforge.net/lists/listinfo/jflex-devel |
|
From: Régis D. <re...@de...> - 2018-09-21 22:54:06
|
Hooray for releasing v1.7 🚀 Le ven. 14 sept. 2018 à 10:05, Régis Décamps <re...@de...> a écrit : > Cool, thanks! > > 2018-09-13 12:43 GMT+02:00 Gerwin Klein <ge...@do...>: > >> Hi Régis, >> >> I’ll have a look at how far I get with publishing the release on the >> weekend! >> >> Cheers, >> Gerwin >> >> >> On 12.09.2018, at 02:29, Régis Décamps <re...@de...> wrote: >> >> Hey Gerwin, >> >> Can you publish the 1.7.0 release? >> >> Once the cut is done, I'll feel more confident to make the changes for >> multi-threading (which are not trivial). >> >> Also, shall we consider dripping the jdk7 in Travis? In the worse case, >> we can use the *-target *version of javac to keep building for Java 7. >> >> -- >> Régis >> >> Le mar. 19 déc. 2017 à 11:17, Gerwin Klein <ge...@do...> a écrit : >> >>> Looks like I didn’t get anything done at all in the week I thought I >>> had. I’m fine with making it a smaller release, but I’m off travelling >>> again from tomorrow, so my part at least will have to wait until early Jan. >>> >>> Cheers, >>> Gerwin >>> >>> On 25.11.2017, at 22:34, Régis Décamps <re...@de...> wrote: >>> >>> I'd be happy to have a release, even if it's not huge. I'll feel more >>> confident to have thread-safety in 1.7.1, for instance. >>> >>> >>> 2017-11-22 12:04 GMT+01:00 Gerwin Klein <ge...@do...>: >>> >>>> Hi Régis, Steve, >>>> >>>> just wanted to let you know that I’ll be away the next 3 weeks, but I >>>> think we might still manage a release before Christmas (or early next year >>>> if we miss Christmas). >>>> >>>> It looks like things are coming together and it would be good to use >>>> the momentum. >>>> >>>> What do you think? >>>> >>>> Cheers, >>>> Gerwin >>>> >>>> >>>> >>>> ------------------------------------------------------------------------------ >>>> Check out the vibrant tech community on one of the world's most >>>> engaging tech sites, Slashdot.org <http://slashdot.org/>! >>>> http://sdm.link/slashdot >>>> _______________________________________________ >>>> Jflex-devel mailing list >>>> Jfl...@li... >>>> https://lists.sourceforge.net/lists/listinfo/jflex-devel >>>> >>> >>> >>> >>> -- >>> Régis Décamps >>> >>> http://regis.decamps.info/ >>> >>> ------------------------------------------------------------------------------ >>> Check out the vibrant tech community on one of the world's most >>> engaging tech sites, Slashdot.org <http://slashdot.org/>! >>> http://sdm.link/slashdot_______________________________________________ >>> Jflex-devel mailing list >>> Jfl...@li... >>> https://lists.sourceforge.net/lists/listinfo/jflex-devel >>> >>> >>> >>> ------------------------------------------------------------------------------ >>> Check out the vibrant tech community on one of the world's most >>> engaging tech sites, Slashdot.org! http://sdm.link/slashdot >>> _______________________________________________ >>> Jflex-devel mailing list >>> Jfl...@li... >>> https://lists.sourceforge.net/lists/listinfo/jflex-devel >>> >> -- >> >> -- >> Régis >> _______________________________________________ >> Jflex-devel mailing list >> Jfl...@li... >> https://lists.sourceforge.net/lists/listinfo/jflex-devel >> >> >> >> >> _______________________________________________ >> Jflex-devel mailing list >> Jfl...@li... >> https://lists.sourceforge.net/lists/listinfo/jflex-devel >> >> > > > -- > Régis Décamps > > http://regis.decamps.info/ > -- -- Régis |
|
From: Régis D. <re...@de...> - 2018-09-14 08:05:59
|
Cool, thanks! 2018-09-13 12:43 GMT+02:00 Gerwin Klein <ge...@do...>: > Hi Régis, > > I’ll have a look at how far I get with publishing the release on the > weekend! > > Cheers, > Gerwin > > > On 12.09.2018, at 02:29, Régis Décamps <re...@de...> wrote: > > Hey Gerwin, > > Can you publish the 1.7.0 release? > > Once the cut is done, I'll feel more confident to make the changes for > multi-threading (which are not trivial). > > Also, shall we consider dripping the jdk7 in Travis? In the worse case, we > can use the *-target *version of javac to keep building for Java 7. > > -- > Régis > > Le mar. 19 déc. 2017 à 11:17, Gerwin Klein <ge...@do...> a écrit : > >> Looks like I didn’t get anything done at all in the week I thought I had. >> I’m fine with making it a smaller release, but I’m off travelling again >> from tomorrow, so my part at least will have to wait until early Jan. >> >> Cheers, >> Gerwin >> >> On 25.11.2017, at 22:34, Régis Décamps <re...@de...> wrote: >> >> I'd be happy to have a release, even if it's not huge. I'll feel more >> confident to have thread-safety in 1.7.1, for instance. >> >> >> 2017-11-22 12:04 GMT+01:00 Gerwin Klein <ge...@do...>: >> >>> Hi Régis, Steve, >>> >>> just wanted to let you know that I’ll be away the next 3 weeks, but I >>> think we might still manage a release before Christmas (or early next year >>> if we miss Christmas). >>> >>> It looks like things are coming together and it would be good to use the >>> momentum. >>> >>> What do you think? >>> >>> Cheers, >>> Gerwin >>> >>> >>> ------------------------------------------------------------ >>> ------------------ >>> Check out the vibrant tech community on one of the world's most >>> engaging tech sites, Slashdot.org <http://slashdot.org/>! >>> http://sdm.link/slashdot >>> _______________________________________________ >>> Jflex-devel mailing list >>> Jfl...@li... >>> https://lists.sourceforge.net/lists/listinfo/jflex-devel >>> >> >> >> >> -- >> Régis Décamps >> >> http://regis.decamps.info/ >> ------------------------------------------------------------ >> ------------------ >> Check out the vibrant tech community on one of the world's most >> engaging tech sites, Slashdot.org <http://slashdot.org/>! >> http://sdm.link/slashdot_______________________________________________ >> Jflex-devel mailing list >> Jfl...@li... >> https://lists.sourceforge.net/lists/listinfo/jflex-devel >> >> >> ------------------------------------------------------------ >> ------------------ >> Check out the vibrant tech community on one of the world's most >> engaging tech sites, Slashdot.org! http://sdm.link/slashdot______ >> _________________________________________ >> Jflex-devel mailing list >> Jfl...@li... >> https://lists.sourceforge.net/lists/listinfo/jflex-devel >> > -- > > -- > Régis > _______________________________________________ > Jflex-devel mailing list > Jfl...@li... > https://lists.sourceforge.net/lists/listinfo/jflex-devel > > > > > _______________________________________________ > Jflex-devel mailing list > Jfl...@li... > https://lists.sourceforge.net/lists/listinfo/jflex-devel > > -- Régis Décamps http://regis.decamps.info/ |
|
From: Gerwin K. <ge...@do...> - 2018-09-13 10:43:25
|
Hi Régis, I’ll have a look at how far I get with publishing the release on the weekend! Cheers, Gerwin > On 12.09.2018, at 02:29, Régis Décamps <re...@de...> wrote: > > Hey Gerwin, > > Can you publish the 1.7.0 release? > > Once the cut is done, I'll feel more confident to make the changes for multi-threading (which are not trivial). > > Also, shall we consider dripping the jdk7 in Travis? In the worse case, we can use the -target version of javac to keep building for Java 7. > > -- > Régis > > Le mar. 19 déc. 2017 à 11:17, Gerwin Klein <ge...@do... <mailto:ge...@do...>> a écrit : > Looks like I didn’t get anything done at all in the week I thought I had. I’m fine with making it a smaller release, but I’m off travelling again from tomorrow, so my part at least will have to wait until early Jan. > > Cheers, > Gerwin > >> On 25.11.2017, at 22:34, Régis Décamps <re...@de... <mailto:re...@de...>> wrote: >> >> I'd be happy to have a release, even if it's not huge. I'll feel more confident to have thread-safety in 1.7.1, for instance. >> >> >> 2017-11-22 12:04 GMT+01:00 Gerwin Klein <ge...@do... <mailto:ge...@do...>>: >> Hi Régis, Steve, >> >> just wanted to let you know that I’ll be away the next 3 weeks, but I think we might still manage a release before Christmas (or early next year if we miss Christmas). >> >> It looks like things are coming together and it would be good to use the momentum. >> >> What do you think? >> >> Cheers, >> Gerwin >> >> >> ------------------------------------------------------------------------------ >> Check out the vibrant tech community on one of the world's most >> engaging tech sites, Slashdot.org <http://slashdot.org/>! http://sdm.link/slashdot <http://sdm.link/slashdot> >> _______________________________________________ >> Jflex-devel mailing list >> Jfl...@li... <mailto:Jfl...@li...> >> https://lists.sourceforge.net/lists/listinfo/jflex-devel <https://lists.sourceforge.net/lists/listinfo/jflex-devel> >> >> >> >> -- >> Régis Décamps >> >> http://regis.decamps.info/ <http://regis.decamps.info/>------------------------------------------------------------------------------ >> Check out the vibrant tech community on one of the world's most >> engaging tech sites, Slashdot.org <http://slashdot.org/>! http://sdm.link/slashdot_______________________________________________ <http://sdm.link/slashdot_______________________________________________> >> Jflex-devel mailing list >> Jfl...@li... <mailto:Jfl...@li...> >> https://lists.sourceforge.net/lists/listinfo/jflex-devel <https://lists.sourceforge.net/lists/listinfo/jflex-devel> > > ------------------------------------------------------------------------------ > Check out the vibrant tech community on one of the world's most > engaging tech sites, Slashdot.org! http://sdm.link/slashdot <http://sdm.link/slashdot>_______________________________________________ > Jflex-devel mailing list > Jfl...@li... <mailto:Jfl...@li...> > https://lists.sourceforge.net/lists/listinfo/jflex-devel <https://lists.sourceforge.net/lists/listinfo/jflex-devel> > -- > -- > Régis > > _______________________________________________ > Jflex-devel mailing list > Jfl...@li... > https://lists.sourceforge.net/lists/listinfo/jflex-devel |
|
From: Régis D. <re...@de...> - 2018-09-11 16:29:44
|
Hey Gerwin, Can you publish the 1.7.0 release? Once the cut is done, I'll feel more confident to make the changes for multi-threading (which are not trivial). Also, shall we consider dripping the jdk7 in Travis? In the worse case, we can use the *-target *version of javac to keep building for Java 7. -- Régis Le mar. 19 déc. 2017 à 11:17, Gerwin Klein <ge...@do...> a écrit : > Looks like I didn’t get anything done at all in the week I thought I had. > I’m fine with making it a smaller release, but I’m off travelling again > from tomorrow, so my part at least will have to wait until early Jan. > > Cheers, > Gerwin > > On 25.11.2017, at 22:34, Régis Décamps <re...@de...> wrote: > > I'd be happy to have a release, even if it's not huge. I'll feel more > confident to have thread-safety in 1.7.1, for instance. > > > 2017-11-22 12:04 GMT+01:00 Gerwin Klein <ge...@do...>: > >> Hi Régis, Steve, >> >> just wanted to let you know that I’ll be away the next 3 weeks, but I >> think we might still manage a release before Christmas (or early next year >> if we miss Christmas). >> >> It looks like things are coming together and it would be good to use the >> momentum. >> >> What do you think? >> >> Cheers, >> Gerwin >> >> >> >> ------------------------------------------------------------------------------ >> Check out the vibrant tech community on one of the world's most >> engaging tech sites, Slashdot.org! http://sdm.link/slashdot >> _______________________________________________ >> Jflex-devel mailing list >> Jfl...@li... >> https://lists.sourceforge.net/lists/listinfo/jflex-devel >> > > > > -- > Régis Décamps > > http://regis.decamps.info/ > > ------------------------------------------------------------------------------ > Check out the vibrant tech community on one of the world's most > engaging tech sites, Slashdot.org! > http://sdm.link/slashdot_______________________________________________ > Jflex-devel mailing list > Jfl...@li... > https://lists.sourceforge.net/lists/listinfo/jflex-devel > > > > ------------------------------------------------------------------------------ > Check out the vibrant tech community on one of the world's most > engaging tech sites, Slashdot.org! http://sdm.link/slashdot > _______________________________________________ > Jflex-devel mailing list > Jfl...@li... > https://lists.sourceforge.net/lists/listinfo/jflex-devel > -- -- Régis |
|
From: Gerwin K. <ge...@do...> - 2018-09-03 12:10:35
|
Hi Régis, thanks for taking care of this! It’s a bit sad that Travis got so flaky, but then again, it’s a free service. Cheers, Gerwin > On 03.09.2018, at 19:03, Régis Décamps <re...@de...> wrote: > > Hello all, > > The JFlex build has been broken due to 2 failures on Travis. > The jdk environment mixing java 8 with javac 9 > I worked around iths by using oraclejdk8 instead of openjdk8 https://github.com/jflex-de/jflex/pull/283 <https://github.com/jflex-de/jflex/pull/283> > Travis being flaky in downloading resources from the internet > This was harder to fix. I've decided to cache the ~/.m2/repository in Travis ; but that lead to side effects. In the end the build workflow (for TEST_SUITE="unit") is > before_install: the snapshot artifacts are cleared > script: the code is compiled, the unit tests are run > cache: ~/.m2/ and jflex/lib are saved > before-deploy: Th esite is built > > -- > Régis > ------------------------------------------------------------------------------ > Check out the vibrant tech community on one of the world's most > engaging tech sites, Slashdot.org! http://sdm.link/slashdot_______________________________________________ > Jflex-devel mailing list > Jfl...@li... > https://lists.sourceforge.net/lists/listinfo/jflex-devel |
|
From: Régis D. <re...@de...> - 2018-09-03 09:03:52
|
Hello all, The JFlex build has been broken due to 2 failures on Travis. - The jdk environment mixing java 8 with javac 9 I worked around iths by using oraclejdk8 instead of openjdk8 https://github.com/jflex-de/jflex/pull/283 - Travis being flaky in downloading resources from the internet This was harder to fix. I've decided to cache the ~/.m2/repository in Travis ; but that lead to side effects. In the end the build workflow (for TEST_SUITE="unit") is 1. before_install: the snapshot artifacts are cleared 2. script: the code is compiled, the unit tests are run 3. cache: ~/.m2/ and jflex/lib are saved 4. before-deploy: Th esite is built -- Régis |
|
From: Gerwin K. <ge...@do...> - 2017-12-19 10:17:52
|
Looks like I didn’t get anything done at all in the week I thought I had. I’m fine with making it a smaller release, but I’m off travelling again from tomorrow, so my part at least will have to wait until early Jan. Cheers, Gerwin > On 25.11.2017, at 22:34, Régis Décamps <re...@de...> wrote: > > I'd be happy to have a release, even if it's not huge. I'll feel more confident to have thread-safety in 1.7.1, for instance. > > > 2017-11-22 12:04 GMT+01:00 Gerwin Klein <ge...@do... <mailto:ge...@do...>>: > Hi Régis, Steve, > > just wanted to let you know that I’ll be away the next 3 weeks, but I think we might still manage a release before Christmas (or early next year if we miss Christmas). > > It looks like things are coming together and it would be good to use the momentum. > > What do you think? > > Cheers, > Gerwin > > > ------------------------------------------------------------------------------ > Check out the vibrant tech community on one of the world's most > engaging tech sites, Slashdot.org! http://sdm.link/slashdot <http://sdm.link/slashdot> > _______________________________________________ > Jflex-devel mailing list > Jfl...@li... <mailto:Jfl...@li...> > https://lists.sourceforge.net/lists/listinfo/jflex-devel <https://lists.sourceforge.net/lists/listinfo/jflex-devel> > > > > -- > Régis Décamps > > http://regis.decamps.info/ <http://regis.decamps.info/>------------------------------------------------------------------------------ > Check out the vibrant tech community on one of the world's most > engaging tech sites, Slashdot.org! http://sdm.link/slashdot_______________________________________________ > Jflex-devel mailing list > Jfl...@li... > https://lists.sourceforge.net/lists/listinfo/jflex-devel |
|
From: Régis D. <re...@de...> - 2017-11-25 11:35:45
|
I'd be happy to have a release, even if it's not huge. I'll feel more confident to have thread-safety in 1.7.1, for instance. 2017-11-22 12:04 GMT+01:00 Gerwin Klein <ge...@do...>: > Hi Régis, Steve, > > just wanted to let you know that I’ll be away the next 3 weeks, but I > think we might still manage a release before Christmas (or early next year > if we miss Christmas). > > It looks like things are coming together and it would be good to use the > momentum. > > What do you think? > > Cheers, > Gerwin > > > ------------------------------------------------------------ > ------------------ > Check out the vibrant tech community on one of the world's most > engaging tech sites, Slashdot.org! http://sdm.link/slashdot > _______________________________________________ > Jflex-devel mailing list > Jfl...@li... > https://lists.sourceforge.net/lists/listinfo/jflex-devel > -- Régis Décamps http://regis.decamps.info/ |
|
From: Gerwin K. <ge...@do...> - 2017-11-22 21:30:17
|
Cool! I’ll be back on Dec 12. I mostly need some uninterrupted time to do the refactor for macros in char classes when I’m back. Cheers, Gerwin > On 23 Nov 2017, at 06:35, Steve Rowe <sa...@gm...> wrote: > > Hi Gerwin, > > +1 to push for a release. > > I have a few things I want to get in, chiefly Unicode 10 support, which I’ve already done most of the work on. > > Steve > >> On Nov 22, 2017, at 6:04 AM, Gerwin Klein <ge...@do...> wrote: >> >> Hi Régis, Steve, >> >> just wanted to let you know that I’ll be away the next 3 weeks, but I think we might still manage a release before Christmas (or early next year if we miss Christmas). >> >> It looks like things are coming together and it would be good to use the momentum. >> >> What do you think? >> >> Cheers, >> Gerwin >> >> >> ------------------------------------------------------------------------------ >> Check out the vibrant tech community on one of the world's most >> engaging tech sites, Slashdot.org! http://sdm.link/slashdot >> _______________________________________________ >> Jflex-devel mailing list >> Jfl...@li... >> https://lists.sourceforge.net/lists/listinfo/jflex-devel > > > ------------------------------------------------------------------------------ > Check out the vibrant tech community on one of the world's most > engaging tech sites, Slashdot.org! http://sdm.link/slashdot > _______________________________________________ > Jflex-devel mailing list > Jfl...@li... > https://lists.sourceforge.net/lists/listinfo/jflex-devel |
