jflex-devel — developers mailing list for JFlex

Re: [Jflex-devel] next release

[Steve R. <sa...@gm...>]

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

[Jflex-devel] next release

[Gerwin K. <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

Re: [Jflex-devel] Branch protection

[Gerwin K. <ge...@do...>]

> On 10.11.2017, at 09:09, Gerwin Klein <ge...@do...> wrote:
> 
> 
>> On 10.11.2017, at 00:46, Régis Décamps via Jflex-devel <jfl...@li... <mailto:jfl...@li...>> wrote:
>> 
>> Hello all,
>> 
>> I've accidentially 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. 

Have now tentatively switched it on to see how it goes. If we don’t like it, we can always revert.

Cheers,
Gerwin

Re: [Jflex-devel] Branch protection

[Gerwin K. <ge...@do...>]

> On 10.11.2017, at 00:46, Régis Décamps via Jflex-devel <jfl...@li...> wrote:
> 
> Hello all,
> 
> I've accidentially 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.


> <Screenshot from 2017-11-09 14:40:58.png>
> Additionally, this prevents the branch from being deleted.
> 
> The workflow would now be:
> Create a branch or clone repo for any change
> Do a pull request
> When Travis completes tests on the PR with a green status, integrate the branch.
> Also, I personnaly 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.

Cheers,
Gerwin

[Jflex-devel] Branch protection

[Régis D. <re...@go...>]

Hello all,

I've accidentially 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/>.

[image: Screenshot from 2017-11-09 14:40:58.png]
Additionally, this prevents the branch from being deleted.

The workflow would now be:

   1. Create a branch or clone repo for any change
   2. Do a pull request
   3. When Travis completes tests on the PR with a green status, integrate
   the branch.

Also, I personnaly feel that the cleanest way to integrate the branch is to
"Squash and merge", but that's a slightly different topic.

Thoughts?

-- 
Régis

Re: [Jflex-devel] I've deleted stale branches in git

[Gerwin K. <ge...@do...>]

That’s good, thanks for cleaning those up!

Cheers,
Gerwin

> On 09.11.2017, at 07:03, Régis Décamps via Jflex-devel <jfl...@li...> wrote:
> 
> And also, I've renamed 1.6.0 to v1.6.0 because the github interface uses reverse alphanumerical order, and it was strange to see
> v1.6.1
> release_1_5_2
> ...
> ...
> release_1_4_0
> 1.6.0
> 
> 2017-11-08 21:01 GMT+01:00 Régis Décamps <de...@us... <mailto:de...@us...>>:
> Hello,
> 
> There were a couple of old and stale branches in git that I've deleted.
> 
> jflex-1.4.3-fixes [DELETED]
> The head of this branch is now know as 1.4.4-SNAPSHOT <https://github.com/jflex-de/jflex/tree/1.4.4-SNAPSHOT>
> 
> jflex_1_5 [DELETED]
> The head of this branch is now known as 1.5.2-SNAPSHOT <https://github.com/jflex-de/jflex/tree/1.5.2-SNAPSHOT>
>  
> --
> Régis
> 
> 
> 
> 
> -- 
> 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

Re: [Jflex-devel] I've deleted stale branches in git

[Régis D. <de...@us...>]

And also, I've renamed 1.6.0 to v1.6.0 because the github interface uses
reverse alphanumerical order, and it was strange to see

   - v1.6.1
   - release_1_5_2
   - ...
   - ...
   - release_1_4_0
   - 1.6.0


2017-11-08 21:01 GMT+01:00 Régis Décamps <de...@us...>:

> Hello,
>
> There were a couple of old and stale branches in git that I've deleted.
>
> jflex-1.4.3-fixes *[DELETED]*
> The head of this branch is now know as 1.4.4-SNAPSHOT
> <https://github.com/jflex-de/jflex/tree/1.4.4-SNAPSHOT>
>
> jflex_1_5 *[DELETED]*
> The head of this branch is now known as 1.5.2-SNAPSHOT
> <https://github.com/jflex-de/jflex/tree/1.5.2-SNAPSHOT>
>
> --
> Régis
>
>


-- 
Régis Décamps

http://regis.decamps.info/

[Jflex-devel] I've deleted stale branches in git

[Régis D. <de...@us...>]

Hello,

There were a couple of old and stale branches in git that I've deleted.

jflex-1.4.3-fixes *[DELETED]*
The head of this branch is now know as 1.4.4-SNAPSHOT
<https://github.com/jflex-de/jflex/tree/1.4.4-SNAPSHOT>

jflex_1_5 *[DELETED]*
The head of this branch is now known as 1.5.2-SNAPSHOT
<https://github.com/jflex-de/jflex/tree/1.5.2-SNAPSHOT>

--
Régis

Re: [Jflex-devel] Minimum build JDK: 6->7 ?

[Gerwin K. <ge...@do...>]

Hi Steve,

> Done.

Cool!

> One question: previously the docs stated that the runtime Java version was 1.5, but I removed that, since the current build requires 1.7.  Do you want to put it back?  I.e. is there some magic that allows the distributed binary to be built with an older version of Java?

The runtime and compile time dependencies are often different. With the latest change, I think it they are both on 1.7 now, though.


>>> It’d be nice to make the test suite aware of JDK version at the points where it is sensitive to that. If I remember correctly the failure was just a different output order of a Hashtable or similar.
>> 
>> What sort of awareness are you thinking of?  Allowing only a single version of the JDK?  Or switching between expected output depending on JDK version?  Or…?
> 
> I’d appreciate your thoughts on this ^^.

Haven’t completely thought this through yet, but I maybe something along the lines of making the test script aware that there could be different outputs for different JDK and even OS versions, which all are correct. I.e. if there is xxx-flex.output-jdk_v_x_y-osv and it matches the current jdk/os then it’d prefer that over xxx-flex.output  (and xxx-flex.output-jdk_v_x_y-osv over xxx-flex.output-jdk_v_x_y if it exists).

The alternative would be to try and make the test output strictly platform independent, e.g. sort the key when we dump tables and similar things. Wouldn’t help, though, if the interpretation of things like isJavaIdentifierStart change between jdk versions.

Cheers,
Gerwin

Re: [Jflex-devel] Minimum build JDK: 6->7 ?

[Steve R. <sa...@gm...>]

Hi Gerwin,

> On Mar 9, 2017, at 10:45 AM, Steve Rowe <sa...@gm...> wrote:
> 
>> On Mar 8, 2017, at 10:13 PM, Gerwin Klein <ge...@do...> wrote:
>> 
>> Sorry, have overlooked this somehow. Yes, no problem from my side with switching the minimum supported build to 1.7.
> 
>> Do you want to push the change directly?
> 
> Sure, I’ll do that some time this week.

Done.

One question: previously the docs stated that the runtime Java version was 1.5, but I removed that, since the current build requires 1.7.  Do you want to put it back?  I.e. is there some magic that allows the distributed binary to be built with an older version of Java?

>> It’d be nice to make the test suite aware of JDK version at the points where it is sensitive to that. If I remember correctly the failure was just a different output order of a Hashtable or similar.
> 
> What sort of awareness are you thinking of?  Allowing only a single version of the JDK?  Or switching between expected output depending on JDK version?  Or…?

I’d appreciate your thoughts on this ^^.

Thanks,
Steve

Re: [Jflex-devel] Minimum build JDK: 6->7 ?

[Steve R. <sa...@gm...>]

Hi Gerwin,

> On Mar 8, 2017, at 10:13 PM, Gerwin Klein <ge...@do...> wrote:
> 
> Sorry, have overlooked this somehow. Yes, no problem from my side with switching the minimum supported build to 1.7.

Cool, thanks.

> It’d be nice to make the test suite aware of JDK version at the points where it is sensitive to that. If I remember correctly the failure was just a different output order of a Hashtable or similar.

What sort of awareness are you thinking of?  Allowing only a single version of the JDK?  Or switching between expected output depending on JDK version?  Or…?

> Do you want to push the change directly?

Sure, I’ll do that some time this week.

Steve

>> On 14.02.2017, at 01:55, Steve Rowe <sa...@gm...> wrote:
>> 
>> Hi Gerwin,
>> 
>> I’m working on adding Unicode 9.0 support to JFlex, and I noticed that my Maven version (3.3.9) no longer supports Java 6, which is documented as JFlex's minimum supported build version.
>> 
>> When the Travis build for the Add_Unicode-9.0 branch failed <https://travis-ci.org/jflex-de/jflex/builds/201132195>, I noticed that it’s configured to use Java 8.  The docs say that Java 6 is not supported - from <https://docs.travis-ci.com/user/ci-environment/>:
>> 
>>> Sun/Oracle JDK 6 is not provided because it reached End of Life in fall 2012.
>> 
>> On the Add_Unicode-9.0 branch I reconfigured Travis to use Java 7, which stopped the ccl-pre testsuite test from failing (the jflex output differed under Java8). 
>> 
>> I think we should switch the minimum supported build JDK for JFlex from 1.6 to 1.7.
>> 
>> Steve

Re: [Jflex-devel] Minimum build JDK: 6->7 ?

[Gerwin K. <ge...@do...>]

Sorry, have overlooked this somehow. Yes, no problem from my side with switching the minimum supported build to 1.7.

It’d be nice to make the test suite aware of JDK version at the points where it is sensitive to that. If I remember correctly the failure was just a different output order of a Hashtable or similar.

Do you want to push the change directly?

Cheers,
Gerwin

> On 14.02.2017, at 01:55, Steve Rowe <sa...@gm...> wrote:
> 
> Hi Gerwin,
> 
> I’m working on adding Unicode 9.0 support to JFlex, and I noticed that my Maven version (3.3.9) no longer supports Java 6, which is documented as JFlex's minimum supported build version.
> 
> When the Travis build for the Add_Unicode-9.0 branch failed <https://travis-ci.org/jflex-de/jflex/builds/201132195>, I noticed that it’s configured to use Java 8.  The docs say that Java 6 is not supported - from <https://docs.travis-ci.com/user/ci-environment/>:
> 
>> Sun/Oracle JDK 6 is not provided because it reached End of Life in fall 2012.
> 
> On the Add_Unicode-9.0 branch I reconfigured Travis to use Java 7, which stopped the ccl-pre testsuite test from failing (the jflex output differed under Java8). 
> 
> I think we should switch the minimum supported build JDK for JFlex from 1.6 to 1.7.
> 
> Steve
> ------------------------------------------------------------------------------
> 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

[Jflex-devel] Minimum build JDK: 6->7 ?

[Steve R. <sa...@gm...>]

Hi Gerwin,

I’m working on adding Unicode 9.0 support to JFlex, and I noticed that my Maven version (3.3.9) no longer supports Java 6, which is documented as JFlex's minimum supported build version.

When the Travis build for the Add_Unicode-9.0 branch failed <https://travis-ci.org/jflex-de/jflex/builds/201132195>, I noticed that it’s configured to use Java 8.  The docs say that Java 6 is not supported - from <https://docs.travis-ci.com/user/ci-environment/>:

> Sun/Oracle JDK 6 is not provided because it reached End of Life in fall 2012.

On the Add_Unicode-9.0 branch I reconfigured Travis to use Java 7, which stopped the ccl-pre testsuite test from failing (the jflex output differed under Java8). 

I think we should switch the minimum supported build JDK for JFlex from 1.6 to 1.7.

Steve

Re: [Jflex-devel] 1.7 release?

[Mike D. <md...@ap...>]

[ https://sourceforge.net/p/jflex/mailman/message/34931503/ Trying to
respond to a thread from before I subscribed, not sure how well mail
clients will handle it. ]

I created github issues for Steve's #7, #8, and #9 tasks -

https://github.com/jflex-de/jflex/issues/195
https://github.com/jflex-de/jflex/issues/196
https://github.com/jflex-de/jflex/issues/197

I was unable to tag them with 1.7 milestone, I think somebody with more
project permissions will need to do that.

I noticed that Gerwin's #3-6 are also still unresolved. Do we have an
expected time line for these? Most of them were described as 'nice, but not
critical.' Maybe it is easier to plan for an eventual 1.7.1 with them?

Thanks,
Mike

Re: [Jflex-devel] 1.7 release?

[Gerwin K. <kl...@un...>]

Makes sense. Could you add these to the github tracker, please?

7) and 9) are no problem.

8) is interesting. I’d probably try to change the rules instead to avoid indefinite lookahead, but in a large grammar that might not make sense. In any case, it shouldn’t be hard to configure fixed buffers.

This does change the semantics, though: in the Lucene case, the long rule never matches, but if the input was different, it could - and then the scanner with fixed buffer matches different tokens to the one with growing/unbounded buffer. I don’t think it’s a huge problem, but we should document it clearly.

Cheers,
Gerwin

> On 13.03.2016, at 07:33, Steve Rowe <sa...@gm...> wrote:
> 
> Hi Gerwin,
> 
> Sorry I didn’t respond sooner on this.
> 
> Your list looks good. 
> 
> There’s also:
> 
> 7) Remove the option to generate an InputStream-param ctor (previously deprecated and slated for removal in 1.7).
> 
> I have two new features I’d also like to include:
> 
> 8) The ability to disable scanner buffer growth (the Lucene project hacks generated scanners to do this - see <https://issues.apache.org/jira/browse/LUCENE-5897> and <https://issues.apache.org/jira/browse/LUCENE-5400> for background.)
> 
> 9) Reduce RAM usage of the char->char class map by using byte[] rather than char[] when the number of classes is less than 257 - see <https://issues.apache.org/jira/browse/LUCENE-6913>.  This could be an automatic optimization, no option required.
> 
> In addition to the latter two, I’ll take a look at 3, 4, 6, and 7.
> 
> Steve
> 
>> On Feb 28, 2016, at 3:25 AM, Gerwin Klein <kl...@un...> wrote:
>> 
>> Looks more closely, these are the things we had marked for 1.7:
>> 
>> https://github.com/jflex-de/jflex/milestones/release%201.7.0
>> 
>> 1) jflex --{version,info,help} should exit with code 0
>> 2) add previous JDKs to Tavis task
>> 3) Warn for probably wrong unicode escapes such as \u0ffff enhancement
>> 4) Make skeleton pass doclint enhancement
>> 5) Upgrade to cup 0.11b task
>> 6) Input/Output file encoding setting [sf#29] enhancement
>> 
>> 1) is easy and I’ll have a look at it in the next few days. 
>> 2) can be moved to later, it needs test suite refactoring and is not that critical.
>> 3) would be nice to have.
>> 4) could be moved
>> 5) just needs checking
>> 6) would also be nice, but not critical.
>> 
>> What do you think?
>> 
>> Cheers,
>> Gerwin
>> 
>>> On 19.02.2016, at 18:59, Gerwin Klein <kl...@un...> wrote:
>>> 
>>> I don’t have anything specific in my queue, so we could just move ahead.
>>> 
>>> Bit pressed for time at the moment, let me see on the weekend what there is to do and if there is something that makes sense to do concurrently.
>>> 
>>> Cheers,
>>> Gerwin
>>> 
>>>> On 19.02.2016, at 08:48, Steve Rowe <sa...@gm...> wrote:
>>>> 
>>>> Hi Gerwin,
>>>> 
>>>> The Lucene project is asking for Unicode 8.0 support from JFlex: <https://issues.apache.org/jira/browse/LUCENE-6993>.
>>>> 
>>>> I committed Unicode 8.0 support in June 2015.
>>>> 
>>>> Are there other things that should be included in a 1.7 release?
>>>> 
>>>> If you agree that a release is a appropriate, is there anything I can do to help?
>>>> 
>>>> Steve
>>>> 
>>>> 
>>>> ------------------------------------------------------------------------------
>>>> Site24x7 APM Insight: Get Deep Visibility into Application Performance
>>>> APM + Mobile APM + RUM: Monitor 3 App instances at just $35/Month
>>>> Monitor end-to-end web transactions and take corrective actions now
>>>> Troubleshoot faster and improve end-user experience. Signup Now!
>>>> http://pubads.g.doubleclick.net/gampad/clk?id=272487151&iu=/4140
>>>> _______________________________________________
>>>> Jflex-devel mailing list
>>>> Jfl...@li...
>>>> https://lists.sourceforge.net/lists/listinfo/jflex-devel
>>> 
>>> ------------------------------------------------------------------------------
>>> Site24x7 APM Insight: Get Deep Visibility into Application Performance
>>> APM + Mobile APM + RUM: Monitor 3 App instances at just $35/Month
>>> Monitor end-to-end web transactions and take corrective actions now
>>> Troubleshoot faster and improve end-user experience. Signup Now!
>>> http://pubads.g.doubleclick.net/gampad/clk?id=272487151&iu=/4140
>>> _______________________________________________
>>> Jflex-devel mailing list
>>> Jfl...@li...
>>> https://lists.sourceforge.net/lists/listinfo/jflex-devel
>> 
>> ------------------------------------------------------------------------------
>> Site24x7 APM Insight: Get Deep Visibility into Application Performance
>> APM + Mobile APM + RUM: Monitor 3 App instances at just $35/Month
>> Monitor end-to-end web transactions and take corrective actions now
>> Troubleshoot faster and improve end-user experience. Signup Now!
>> http://pubads.g.doubleclick.net/gampad/clk?id=272487151&iu=/4140
>> _______________________________________________
>> Jflex-devel mailing list
>> Jfl...@li...
>> https://lists.sourceforge.net/lists/listinfo/jflex-devel
> 
> 
> ------------------------------------------------------------------------------
> Transform Data into Opportunity.
> Accelerate data analysis in your applications with
> Intel Data Analytics Acceleration Library.
> Click to learn more.
> http://pubads.g.doubleclick.net/gampad/clk?id=278785111&iu=/4140
> _______________________________________________
> Jflex-devel mailing list
> Jfl...@li...
> https://lists.sourceforge.net/lists/listinfo/jflex-devel

Re: [Jflex-devel] 1.7 release?

[Steve R. <sa...@gm...>]

Hi Gerwin,

Sorry I didn’t respond sooner on this.

Your list looks good. 

There’s also:

7) Remove the option to generate an InputStream-param ctor (previously deprecated and slated for removal in 1.7).

I have two new features I’d also like to include:

8) The ability to disable scanner buffer growth (the Lucene project hacks generated scanners to do this - see <https://issues.apache.org/jira/browse/LUCENE-5897> and <https://issues.apache.org/jira/browse/LUCENE-5400> for background.)

9) Reduce RAM usage of the char->char class map by using byte[] rather than char[] when the number of classes is less than 257 - see <https://issues.apache.org/jira/browse/LUCENE-6913>.  This could be an automatic optimization, no option required.

In addition to the latter two, I’ll take a look at 3, 4, 6, and 7.

Steve

> On Feb 28, 2016, at 3:25 AM, Gerwin Klein <kl...@un...> wrote:
> 
> Looks more closely, these are the things we had marked for 1.7:
> 
> https://github.com/jflex-de/jflex/milestones/release%201.7.0
> 
> 1) jflex --{version,info,help} should exit with code 0
> 2) add previous JDKs to Tavis task
> 3) Warn for probably wrong unicode escapes such as \u0ffff enhancement
> 4) Make skeleton pass doclint enhancement
> 5) Upgrade to cup 0.11b task
> 6) Input/Output file encoding setting [sf#29] enhancement
> 
> 1) is easy and I’ll have a look at it in the next few days. 
> 2) can be moved to later, it needs test suite refactoring and is not that critical.
> 3) would be nice to have.
> 4) could be moved
> 5) just needs checking
> 6) would also be nice, but not critical.
> 
> What do you think?
> 
> Cheers,
> Gerwin
> 
>> On 19.02.2016, at 18:59, Gerwin Klein <kl...@un...> wrote:
>> 
>> I don’t have anything specific in my queue, so we could just move ahead.
>> 
>> Bit pressed for time at the moment, let me see on the weekend what there is to do and if there is something that makes sense to do concurrently.
>> 
>> Cheers,
>> Gerwin
>> 
>>> On 19.02.2016, at 08:48, Steve Rowe <sa...@gm...> wrote:
>>> 
>>> Hi Gerwin,
>>> 
>>> The Lucene project is asking for Unicode 8.0 support from JFlex: <https://issues.apache.org/jira/browse/LUCENE-6993>.
>>> 
>>> I committed Unicode 8.0 support in June 2015.
>>> 
>>> Are there other things that should be included in a 1.7 release?
>>> 
>>> If you agree that a release is a appropriate, is there anything I can do to help?
>>> 
>>> Steve
>>> 
>>> 
>>> ------------------------------------------------------------------------------
>>> Site24x7 APM Insight: Get Deep Visibility into Application Performance
>>> APM + Mobile APM + RUM: Monitor 3 App instances at just $35/Month
>>> Monitor end-to-end web transactions and take corrective actions now
>>> Troubleshoot faster and improve end-user experience. Signup Now!
>>> http://pubads.g.doubleclick.net/gampad/clk?id=272487151&iu=/4140
>>> _______________________________________________
>>> Jflex-devel mailing list
>>> Jfl...@li...
>>> https://lists.sourceforge.net/lists/listinfo/jflex-devel
>> 
>> ------------------------------------------------------------------------------
>> Site24x7 APM Insight: Get Deep Visibility into Application Performance
>> APM + Mobile APM + RUM: Monitor 3 App instances at just $35/Month
>> Monitor end-to-end web transactions and take corrective actions now
>> Troubleshoot faster and improve end-user experience. Signup Now!
>> http://pubads.g.doubleclick.net/gampad/clk?id=272487151&iu=/4140
>> _______________________________________________
>> Jflex-devel mailing list
>> Jfl...@li...
>> https://lists.sourceforge.net/lists/listinfo/jflex-devel
> 
> ------------------------------------------------------------------------------
> Site24x7 APM Insight: Get Deep Visibility into Application Performance
> APM + Mobile APM + RUM: Monitor 3 App instances at just $35/Month
> Monitor end-to-end web transactions and take corrective actions now
> Troubleshoot faster and improve end-user experience. Signup Now!
> http://pubads.g.doubleclick.net/gampad/clk?id=272487151&iu=/4140
> _______________________________________________
> Jflex-devel mailing list
> Jfl...@li...
> https://lists.sourceforge.net/lists/listinfo/jflex-devel

Re: [Jflex-devel] 1.7 release?

[Gerwin K. <kl...@un...>]

Looks more closely, these are the things we had marked for 1.7:

https://github.com/jflex-de/jflex/milestones/release%201.7.0

1) jflex --{version,info,help} should exit with code 0
2) add previous JDKs to Tavis task
3) Warn for probably wrong unicode escapes such as \u0ffff enhancement
4) Make skeleton pass doclint enhancement
5) Upgrade to cup 0.11b task
6) Input/Output file encoding setting [sf#29] enhancement

1) is easy and I’ll have a look at it in the next few days. 
2) can be moved to later, it needs test suite refactoring and is not that critical.
3) would be nice to have.
4) could be moved
5) just needs checking
6) would also be nice, but not critical.

What do you think?

Cheers,
Gerwin

> On 19.02.2016, at 18:59, Gerwin Klein <kl...@un...> wrote:
> 
> I don’t have anything specific in my queue, so we could just move ahead.
> 
> Bit pressed for time at the moment, let me see on the weekend what there is to do and if there is something that makes sense to do concurrently.
> 
> Cheers,
> Gerwin
> 
>> On 19.02.2016, at 08:48, Steve Rowe <sa...@gm...> wrote:
>> 
>> Hi Gerwin,
>> 
>> The Lucene project is asking for Unicode 8.0 support from JFlex: <https://issues.apache.org/jira/browse/LUCENE-6993>.
>> 
>> I committed Unicode 8.0 support in June 2015.
>> 
>> Are there other things that should be included in a 1.7 release?
>> 
>> If you agree that a release is a appropriate, is there anything I can do to help?
>> 
>> Steve
>> 
>> 
>> ------------------------------------------------------------------------------
>> Site24x7 APM Insight: Get Deep Visibility into Application Performance
>> APM + Mobile APM + RUM: Monitor 3 App instances at just $35/Month
>> Monitor end-to-end web transactions and take corrective actions now
>> Troubleshoot faster and improve end-user experience. Signup Now!
>> http://pubads.g.doubleclick.net/gampad/clk?id=272487151&iu=/4140
>> _______________________________________________
>> Jflex-devel mailing list
>> Jfl...@li...
>> https://lists.sourceforge.net/lists/listinfo/jflex-devel
> 
> ------------------------------------------------------------------------------
> Site24x7 APM Insight: Get Deep Visibility into Application Performance
> APM + Mobile APM + RUM: Monitor 3 App instances at just $35/Month
> Monitor end-to-end web transactions and take corrective actions now
> Troubleshoot faster and improve end-user experience. Signup Now!
> http://pubads.g.doubleclick.net/gampad/clk?id=272487151&iu=/4140
> _______________________________________________
> Jflex-devel mailing list
> Jfl...@li...
> https://lists.sourceforge.net/lists/listinfo/jflex-devel

Re: [Jflex-devel] 1.7 release?

[Gerwin K. <kl...@un...>]

I don’t have anything specific in my queue, so we could just move ahead.

Bit pressed for time at the moment, let me see on the weekend what there is to do and if there is something that makes sense to do concurrently.

Cheers,
Gerwin

> On 19.02.2016, at 08:48, Steve Rowe <sa...@gm...> wrote:
> 
> Hi Gerwin,
> 
> The Lucene project is asking for Unicode 8.0 support from JFlex: <https://issues.apache.org/jira/browse/LUCENE-6993>.
> 
> I committed Unicode 8.0 support in June 2015.
> 
> Are there other things that should be included in a 1.7 release?
> 
> If you agree that a release is a appropriate, is there anything I can do to help?
> 
> Steve
> 
> 
> ------------------------------------------------------------------------------
> Site24x7 APM Insight: Get Deep Visibility into Application Performance
> APM + Mobile APM + RUM: Monitor 3 App instances at just $35/Month
> Monitor end-to-end web transactions and take corrective actions now
> Troubleshoot faster and improve end-user experience. Signup Now!
> http://pubads.g.doubleclick.net/gampad/clk?id=272487151&iu=/4140
> _______________________________________________
> Jflex-devel mailing list
> Jfl...@li...
> https://lists.sourceforge.net/lists/listinfo/jflex-devel

[Jflex-devel] 1.7 release?

[Steve R. <sa...@gm...>]

Hi Gerwin,

The Lucene project is asking for Unicode 8.0 support from JFlex: <https://issues.apache.org/jira/browse/LUCENE-6993>.

I committed Unicode 8.0 support in June 2015.

Are there other things that should be included in a 1.7 release?

If you agree that a release is a appropriate, is there anything I can do to help?

Steve

Re: [Jflex-devel] Commit email configured for all 4 jflex-de Github repositories

[Gerwin K. <Ger...@ni...>]

Yes, seems to work, at least I got them as well. Thanks for setting it up.

Cheers,
Gerwin

On 24.06.2015, at 05:39, Steve Rowe <sa...@gm...<mailto:sa...@gm...>> wrote:

I added the "Email" service to each of the 4 repositories (from Settings|Webhooks&Services), and had event notifications (including commits) go to <kle...@cs...<mailto:kle...@cs...>>.

I clicked the "test service" button for each repository, which apparently caused an email to be generated for the most recent commit; I received those emails, so it appears to be working.

Steve
------------------------------------------------------------------------------
Monitor 25 network devices or servers for free with OpManager!
OpManager is web-based network management software that monitors
network devices and physical & virtual servers, alerts via email & sms
for fault. Monitor 25 devices for free with no restriction. Download now
http://ad.doubleclick.net/ddm/clk/292181274;119417398;o_______________________________________________
Jflex-devel mailing list
Jfl...@li...
https://lists.sourceforge.net/lists/listinfo/jflex-devel


________________________________

The information in this e-mail may be confidential and subject to legal professional privilege and/or copyright. National ICT Australia Limited accepts no liability for any damage caused by this email or its attachments.

[Jflex-devel] Commit email configured for all 4 jflex-de Github repositories

[Steve R. <sa...@gm...>]

I added the "Email" service to each of the 4 repositories (from
Settings|Webhooks&Services), and had event notifications (including
commits) go to <kle...@cs...>.

I clicked the "test service" button for each repository, which apparently
caused an email to be generated for the most recent commit; I received
those emails, so it appears to be working.

Steve

Re: [Jflex-devel] Be material: a little color and animation for jflex.de

[Gerwin K. <kl...@cs...>]

No worries, thanks for the fix, seems to work well and is deployed.

Haven’t seen the github logo linebreak issue yet, but feel free to tweak.

Cheers,
Gerwin

> On 19 Apr 2015, at 7:49 pm, Régis Décamps <re...@de...> wrote:
> 
> OK, the anchor position was easy to fix. Sorry for this bug.
> 
> Le dim. 19 avr. 2015 à 20:30, Régis Décamps <re...@de... <mailto:re...@de...>> a écrit :
> Thanks for the pointer, I'll have a look.
> 
> There is another minor glitch I ran into: for done browser window width, the content is not collapsed in the menu, yet there isn't enough discs abd and the github logo goes on its own line.
> 
> 
> Le jeu. 16 avr. 2015 11:00, Gerwin Klein <Ger...@ni... <mailto:Ger...@ni...>> a écrit :
> Thanks, makes sense to just use #content.
> 
> I’ve merged the pull requests and can deploy later today when I have a better internet connection.
> 
> There is a problem with the fixed navbar that I also ran into previously: when clicking a link like #content, the browser will set that to the top of the page, ignoring the body offset, so that the target is partially obscured by the nav bar. This trick seems to solve it:
> 
> http://stackoverflow.com/questions/18948440/when-navigating-to-id-element-is-hidden-under-fixed-position-header/18948554#18948554 <http://stackoverflow.com/questions/18948440/when-navigating-to-id-element-is-hidden-under-fixed-position-header/18948554#18948554>
> 
> Should we do that, or do you know a better solution?
> 
> Cheers,
> Gerwin
> 
> 
> 
>> On 15 Apr 2015, at 11:16 pm, Régis Décamps <re...@de... <mailto:re...@de...>> wrote:
>> 
> 
>> Thanks. I don't know why I haven't initially made a pull request.
>> 
>> Le mer. 15 avr. 2015 à 16:15, Gerwin Klein <kl...@cs... <mailto:kl...@cs...>> a écrit :
>> Had some unexpected free time: looks very nice!
>> 
>> Two small issues: the brand link in the navbar still goes to http://jflex.de <http://jflex.de/>. That made sense when it was always labeled `jflex.de <http://jflex.de/>`, but now it’s the title of the page, so we should link to the top of the current page instead.
>> 
>> Good point. Done in https://github.com/regisd/jflex-web/commit/ca49d6f3cf98e131a07d8b6fce459d9b467b5625 <https://github.com/regisd/jflex-web/commit/ca49d6f3cf98e131a07d8b6fce459d9b467b5625>
>>  
>> Related to that, the #top anchor seems to have disappeared. It’s used in the page footer to navigate up again (mostly only useful on mobiles and small screens).
>> 
>> It wasn't removed.
>> 
>> But, it can actually be replaced https://github.com/regisd/jflex-web/commit/53ee94d1c96e60a89e4a108ef3afd8a0553ff8b5 <https://github.com/regisd/jflex-web/commit/53ee94d1c96e60a89e4a108ef3afd8a0553ff8b5>
>>  
>> -- 
>> Régis
>> 
>> 
>>> On 15 Apr 2015, at 9:49 am, Gerwin Klein <kl...@cs... <mailto:kl...@cs...>> wrote:
>>> 
>>> Sounds cool. I’m travelling again, so might be a few days before I can have a closer look.
>>> 
>>> Cheers,
>>> Gerwin
>>> 
>>>> On 13 Apr 2015, at 9:45 pm, Régis Décamps <re...@de... <mailto:re...@de...>> wrote:
>>>> 
>>>> Hello Gerwin and others,
>>>> 
>>>> I tried to give a touch of material design to jflex.de <http://jflex.de/>. That's mainly the use of headers for now (self implement with jquery, there is no new dependency)
>>>> 
>>>> I also chose new colors from the palette <http://www.google.ch/design/spec/style/color.html#color-color-palette>: indogo and orange.
>>>> 
>>>> The patch is in branch "material" (oops, the same branch also fixes some issues with the titles).
>>>> 
>>>> -- 
>>>> Régis
>>>> PJ: Screenshot top of page, after a scroll
>> 
> 
>> ------------------------------------------------------------------------------
>> BPM Camp - Free Virtual Workshop May 6th at 10am PDT/1PM EDT
>> Develop your own process in accordance with the BPMN 2 standard
>> Learn Process modeling best practices with Bonita BPM through live exercises
>> http://www.bonitasoft.com/be-part-of-it/events/bpm-camp-virtual- <http://www.bonitasoft.com/be-part-of-it/events/bpm-camp-virtual-> event?utm_
>> source=Sourceforge_BPM_Camp_5_6_15&utm_medium=email&utm_campaign=VA_SF_______________________________________________
>> 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>
> 
> 
> 
> 
> The information in this e-mail may be confidential and subject to legal professional privilege and/or copyright. National ICT Australia Limited accepts no liability for any damage caused by this email or its attachments.
> ------------------------------------------------------------------------------
> BPM Camp - Free Virtual Workshop May 6th at 10am PDT/1PM EDT
> Develop your own process in accordance with the BPMN 2 standard
> Learn Process modeling best practices with Bonita BPM through live exercises
> http://www.bonitasoft.com/be-part-of-it/events/bpm-camp-virtual- <http://www.bonitasoft.com/be-part-of-it/events/bpm-camp-virtual-> event?utm_
> source=Sourceforge_BPM_Camp_5_6_15&utm_medium=email&utm_campaign=VA_SF_______________________________________________
> 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>
> ------------------------------------------------------------------------------
> BPM Camp - Free Virtual Workshop May 6th at 10am PDT/1PM EDT
> Develop your own process in accordance with the BPMN 2 standard
> Learn Process modeling best practices with Bonita BPM through live exercises
> http://www.bonitasoft.com/be-part-of-it/events/bpm-camp-virtual- event?utm_
> source=Sourceforge_BPM_Camp_5_6_15&utm_medium=email&utm_campaign=VA_SF_______________________________________________
> Jflex-devel mailing list
> Jfl...@li...
> https://lists.sourceforge.net/lists/listinfo/jflex-devel

Re: [Jflex-devel] Be material: a little color and animation for jflex.de

[Régis D. <re...@de...>]

OK, the anchor position was easy to fix. Sorry for this bug.

Le dim. 19 avr. 2015 à 20:30, Régis Décamps <re...@de...> a écrit :

> Thanks for the pointer, I'll have a look.
>
> There is another minor glitch I ran into: for done browser window width,
> the content is not collapsed in the menu, yet there isn't enough discs abd
> and the github logo goes on its own line.
>
> Le jeu. 16 avr. 2015 11:00, Gerwin Klein <Ger...@ni...> a
> écrit :
>
>>  Thanks, makes sense to just use #content.
>>
>>  I’ve merged the pull requests and can deploy later today when I have a
>> better internet connection.
>>
>>  There is a problem with the fixed navbar that I also ran into
>> previously: when clicking a link like #content, the browser will set that
>> to the top of the page, ignoring the body offset, so that the target is
>> partially obscured by the nav bar. This trick seems to solve it:
>>
>>
>> http://stackoverflow.com/questions/18948440/when-navigating-to-id-element-is-hidden-under-fixed-position-header/18948554#18948554
>>
>>  Should we do that, or do you know a better solution?
>>
>>  Cheers,
>> Gerwin
>>
>>
>>  On 15 Apr 2015, at 11:16 pm, Régis Décamps <re...@de...> wrote:
>>
>>  Thanks. I don't know why I haven't initially made a pull request.
>>
>>  Le mer. 15 avr. 2015 à 16:15, Gerwin Klein <kl...@cs...> a
>> écrit :
>>
>>> Had some unexpected free time: looks very nice!
>>>
>>>  Two small issues: the brand link in the navbar still goes to
>>> http://jflex.de. That made sense when it was always labeled `jflex.de`,
>>> but now it’s the title of the page, so we should link to the top of the
>>> current page instead.
>>>
>>
>>  Good point. Done in
>> https://github.com/regisd/jflex-web/commit/ca49d6f3cf98e131a07d8b6fce459d9b467b5625
>>
>>
>>>  Related to that, the #top anchor seems to have disappeared. It’s used
>>> in the page footer to navigate up again (mostly only useful on mobiles and
>>> small screens).
>>>
>>
>>  It wasn't removed.
>>
>>  But, it can actually be replaced
>> https://github.com/regisd/jflex-web/commit/53ee94d1c96e60a89e4a108ef3afd8a0553ff8b5
>>
>> --
>> Régis
>>
>>
>>>  On 15 Apr 2015, at 9:49 am, Gerwin Klein <kl...@cs...>
>>> wrote:
>>>
>>>  Sounds cool. I’m travelling again, so might be a few days before I can
>>> have a closer look.
>>>
>>>  Cheers,
>>> Gerwin
>>>
>>>  On 13 Apr 2015, at 9:45 pm, Régis Décamps <re...@de...> wrote:
>>>
>>>  Hello Gerwin and others,
>>>
>>>  I tried to give a touch of material design to jflex.de. That's mainly
>>> the use of headers for now (self implement with jquery, there is no new
>>> dependency)
>>>
>>>  I also chose new colors from the palette
>>> <http://www.google.ch/design/spec/style/color.html#color-color-palette>:
>>> indogo and orange.
>>>
>>>  The patch is in branch "material" (oops, the same branch also fixes
>>> some issues with the titles).
>>>
>>>  --
>>> Régis
>>> PJ: Screenshot top of page, after a scroll
>>>
>>>
>>>
>> ------------------------------------------------------------------------------
>> BPM Camp - Free Virtual Workshop May 6th at 10am PDT/1PM EDT
>> Develop your own process in accordance with the BPMN 2 standard
>> Learn Process modeling best practices with Bonita BPM through live
>> exercises
>> http://www.bonitasoft.com/be-part-of-it/events/bpm-camp-virtual-
>> event?utm_
>>
>> source=Sourceforge_BPM_Camp_5_6_15&utm_medium=email&utm_campaign=VA_SF_______________________________________________
>> Jflex-devel mailing list
>> Jfl...@li...
>> https://lists.sourceforge.net/lists/listinfo/jflex-devel
>>
>>
>>
>> ------------------------------
>>
>> The information in this e-mail may be confidential and subject to legal
>> professional privilege and/or copyright. National ICT Australia Limited
>> accepts no liability for any damage caused by this email or its attachments.
>>
>> ------------------------------------------------------------------------------
>> BPM Camp - Free Virtual Workshop May 6th at 10am PDT/1PM EDT
>> Develop your own process in accordance with the BPMN 2 standard
>> Learn Process modeling best practices with Bonita BPM through live
>> exercises
>> http://www.bonitasoft.com/be-part-of-it/events/bpm-camp-virtual-
>> event?utm_
>>
>> source=Sourceforge_BPM_Camp_5_6_15&utm_medium=email&utm_campaign=VA_SF_______________________________________________
>> Jflex-devel mailing list
>> Jfl...@li...
>> https://lists.sourceforge.net/lists/listinfo/jflex-devel
>>
>

Re: [Jflex-devel] Be material: a little color and animation for jflex.de

[Régis D. <re...@de...>]

Thanks for the pointer, I'll have a look.

There is another minor glitch I ran into: for done browser window width,
the content is not collapsed in the menu, yet there isn't enough discs abd
and the github logo goes on its own line.

Le jeu. 16 avr. 2015 11:00, Gerwin Klein <Ger...@ni...> a
écrit :

>  Thanks, makes sense to just use #content.
>
>  I’ve merged the pull requests and can deploy later today when I have a
> better internet connection.
>
>  There is a problem with the fixed navbar that I also ran into
> previously: when clicking a link like #content, the browser will set that
> to the top of the page, ignoring the body offset, so that the target is
> partially obscured by the nav bar. This trick seems to solve it:
>
>
> http://stackoverflow.com/questions/18948440/when-navigating-to-id-element-is-hidden-under-fixed-position-header/18948554#18948554
>
>  Should we do that, or do you know a better solution?
>
>  Cheers,
> Gerwin
>
>
>  On 15 Apr 2015, at 11:16 pm, Régis Décamps <re...@de...> wrote:
>
>  Thanks. I don't know why I haven't initially made a pull request.
>
>  Le mer. 15 avr. 2015 à 16:15, Gerwin Klein <kl...@cs...> a
> écrit :
>
>> Had some unexpected free time: looks very nice!
>>
>>  Two small issues: the brand link in the navbar still goes to
>> http://jflex.de. That made sense when it was always labeled `jflex.de`,
>> but now it’s the title of the page, so we should link to the top of the
>> current page instead.
>>
>
>  Good point. Done in
> https://github.com/regisd/jflex-web/commit/ca49d6f3cf98e131a07d8b6fce459d9b467b5625
>
>
>>  Related to that, the #top anchor seems to have disappeared. It’s used
>> in the page footer to navigate up again (mostly only useful on mobiles and
>> small screens).
>>
>
>  It wasn't removed.
>
>  But, it can actually be replaced
> https://github.com/regisd/jflex-web/commit/53ee94d1c96e60a89e4a108ef3afd8a0553ff8b5
>
> --
> Régis
>
>
>>  On 15 Apr 2015, at 9:49 am, Gerwin Klein <kl...@cs...> wrote:
>>
>>  Sounds cool. I’m travelling again, so might be a few days before I can
>> have a closer look.
>>
>>  Cheers,
>> Gerwin
>>
>>  On 13 Apr 2015, at 9:45 pm, Régis Décamps <re...@de...> wrote:
>>
>>  Hello Gerwin and others,
>>
>>  I tried to give a touch of material design to jflex.de. That's mainly
>> the use of headers for now (self implement with jquery, there is no new
>> dependency)
>>
>>  I also chose new colors from the palette
>> <http://www.google.ch/design/spec/style/color.html#color-color-palette>:
>> indogo and orange.
>>
>>  The patch is in branch "material" (oops, the same branch also fixes
>> some issues with the titles).
>>
>>  --
>> Régis
>> PJ: Screenshot top of page, after a scroll
>>
>>
>>
> ------------------------------------------------------------------------------
> BPM Camp - Free Virtual Workshop May 6th at 10am PDT/1PM EDT
> Develop your own process in accordance with the BPMN 2 standard
> Learn Process modeling best practices with Bonita BPM through live
> exercises
> http://www.bonitasoft.com/be-part-of-it/events/bpm-camp-virtual-
> event?utm_
>
> source=Sourceforge_BPM_Camp_5_6_15&utm_medium=email&utm_campaign=VA_SF_______________________________________________
> Jflex-devel mailing list
> Jfl...@li...
> https://lists.sourceforge.net/lists/listinfo/jflex-devel
>
>
>
> ------------------------------
>
> The information in this e-mail may be confidential and subject to legal
> professional privilege and/or copyright. National ICT Australia Limited
> accepts no liability for any damage caused by this email or its attachments.
>
> ------------------------------------------------------------------------------
> BPM Camp - Free Virtual Workshop May 6th at 10am PDT/1PM EDT
> Develop your own process in accordance with the BPMN 2 standard
> Learn Process modeling best practices with Bonita BPM through live
> exercises
> http://www.bonitasoft.com/be-part-of-it/events/bpm-camp-virtual-
> event?utm_
>
> source=Sourceforge_BPM_Camp_5_6_15&utm_medium=email&utm_campaign=VA_SF_______________________________________________
> Jflex-devel mailing list
> Jfl...@li...
> https://lists.sourceforge.net/lists/listinfo/jflex-devel
>

Re: [Jflex-devel] Be material: a little color and animation for jflex.de

[Gerwin K. <Ger...@ni...>]

Thanks, makes sense to just use #content.

I’ve merged the pull requests and can deploy later today when I have a better internet connection.

There is a problem with the fixed navbar that I also ran into previously: when clicking a link like #content, the browser will set that to the top of the page, ignoring the body offset, so that the target is partially obscured by the nav bar. This trick seems to solve it:

http://stackoverflow.com/questions/18948440/when-navigating-to-id-element-is-hidden-under-fixed-position-header/18948554#18948554

Should we do that, or do you know a better solution?

Cheers,
Gerwin


On 15 Apr 2015, at 11:16 pm, Régis Décamps <re...@de...<mailto:re...@de...>> wrote:

Thanks. I don't know why I haven't initially made a pull request.

Le mer. 15 avr. 2015 à 16:15, Gerwin Klein <kl...@cs...<mailto:kl...@cs...>> a écrit :
Had some unexpected free time: looks very nice!

Two small issues: the brand link in the navbar still goes to http://jflex.de<http://jflex.de/>. That made sense when it was always labeled `jflex.de<http://jflex.de/>`, but now it’s the title of the page, so we should link to the top of the current page instead.

Good point. Done in https://github.com/regisd/jflex-web/commit/ca49d6f3cf98e131a07d8b6fce459d9b467b5625

Related to that, the #top anchor seems to have disappeared. It’s used in the page footer to navigate up again (mostly only useful on mobiles and small screens).

It wasn't removed.

But, it can actually be replaced https://github.com/regisd/jflex-web/commit/53ee94d1c96e60a89e4a108ef3afd8a0553ff8b5

--
Régis


On 15 Apr 2015, at 9:49 am, Gerwin Klein <kl...@cs...<mailto:kl...@cs...>> wrote:

Sounds cool. I’m travelling again, so might be a few days before I can have a closer look.

Cheers,
Gerwin

On 13 Apr 2015, at 9:45 pm, Régis Décamps <re...@de...<mailto:re...@de...>> wrote:

Hello Gerwin and others,

I tried to give a touch of material design to jflex.de<http://jflex.de/>. That's mainly the use of headers for now (self implement with jquery, there is no new dependency)

I also chose new colors from the palette<http://www.google.ch/design/spec/style/color.html#color-color-palette>: indogo and orange.

The patch is in branch "material" (oops, the same branch also fixes some issues with the titles).

--
Régis
PJ: Screenshot top of page, after a scroll

------------------------------------------------------------------------------
BPM Camp - Free Virtual Workshop May 6th at 10am PDT/1PM EDT
Develop your own process in accordance with the BPMN 2 standard
Learn Process modeling best practices with Bonita BPM through live exercises
http://www.bonitasoft.com/be-part-of-it/events/bpm-camp-virtual- event?utm_
source=Sourceforge_BPM_Camp_5_6_15&utm_medium=email&utm_campaign=VA_SF_______________________________________________
Jflex-devel mailing list
Jfl...@li...<mailto:Jfl...@li...>
https://lists.sourceforge.net/lists/listinfo/jflex-devel


________________________________

The information in this e-mail may be confidential and subject to legal professional privilege and/or copyright. National ICT Australia Limited accepts no liability for any damage caused by this email or its attachments.