> -----Original Message----- > From: Thorsten Scherler [mailto:scher...@gmail.com] > Sent: Montag, 29. August 2011 14:16 > To: dev@cocoon.apache.org > Subject: Re: svn commit: r1162745 - in /cocoon/cocoon3/trunk: cocoon- > optional/pom.xml cocoon-stax/pom.xml parent/pom.xml > > On Mon, 2011-08-29 at 14:00 +0200, Francesco Chicchiriccò wrote: > ... > > Since Jakarta RegExp is retired (see [1]), do you think it would be hard > > to rework the DirectoryGenerator in order to make use of > > java.util.regexp.* instead? > > Otherwise you can just add this dependency - with version - in > > parent/pom.xml and with optional modifier in cocoon-optional/pom.xml. > > > > One less dependency - even though optional - is better :-) > > Hmm, Jakarta RegExp does some things different and IMO much better then > java.util. Even if it is retired that does not mean it is not worth > using it, more since this way the component works exactly as in our > prior versions. Not sure when I will find the time to look into a > rewrite to use java regex.
I second Francesco that we should get rid of Jakarta RegExp before 3.0. In the long run will pay off to use a good standard rather than a better non-standard. When you say Jakarta does it different and better do you refer to the API or the regexp syntax? If it is just converting the API calls, I can help. I wonder whether for the average user it would not be more convenient if DirectoryGenerator would accept the same Ant-style globs as map:match rather than full-blown Perl-style regexps. Cheers, Alfred. The content of this e-mail is intended only for the confidential use of the person addressed. If you are not the intended recipient, please notify the sender and delete this e-mail immediately. Thank you.
