Oops, sorry. I already got one -- from Mark for missing this. But I did document the issue in the Jira and the code, so it should be clear to everybody. -W
On 25 December 2010 13:06, Geoffrey De Smet <[email protected]> wrote: > Nice :) Thanks for fixing. So JBRULES-2849 can be closed? > > Next time add the jira issue id in the commit comment JBRULES-2849 > that way the commit will be shown in the jira issue (once they enable > git integration in jira) > > With kind regards / Met vriendelijke groeten, > Geoffrey De Smet > > Op 25-12-10 11:57, Wolfgang Laun schreef: > > JDK 5 doesn't handle lookbehind assertions correctly if they contain > > alternatives. The fallout from this bug has been cleared up by my > > release > > > https://github.com/droolsjbpm/droolsjbpm/commit/f3a50273c91ac697b6f1a0936ce96a44c3b38250 > > > > I have added comments to clarify the nature of the "strange" workaround > > regex part that's now being used, which also affects the JUnit tests. If > > JDK 5 is dropped from the has-to-be-compatible-with list of Java > > releases, the simpler regex construct might be used again. > > > > Cheers > > Wolfgang > > > > > > > > _______________________________________________ > > rules-dev mailing list > > [email protected] > > https://lists.jboss.org/mailman/listinfo/rules-dev > > _______________________________________________ > rules-dev mailing list > [email protected] > https://lists.jboss.org/mailman/listinfo/rules-dev >
_______________________________________________ rules-dev mailing list [email protected] https://lists.jboss.org/mailman/listinfo/rules-dev
