Hello,

Our server product is and has been stuck on Java 1.3.1 for quite a
while. This is a customer requirement, not ours. What I would like to
see is ORO either evolve to provide the a thin 1.4 bridge or have a new
commons-regexp as we now have a commons-logging. I do not really care
which one happens but it would be nice to be able to automatically use
the 1.4 libraries if they are there and fall back on ORO if not. I am
assuming that the 1.4 RE support is "better" for a vague enough
definition of "better".

Thank you,
Gary 

> -----Original Message-----
> From: Daniel F. Savarese [mailto:[EMAIL PROTECTED]
> Sent: Tuesday, June 15, 2004 13:07
> To: Jakarta Commons Developers List
> Subject: Re: [vfs][all][poll]regular expression library or jdk1.4 as
> minimum requirement
> 
> 
> In message <[EMAIL PROTECTED]>, "Noel J.
> Bergman" w
> rites:
> >Daniel, are you still interested/trying to move ORO into Commons?
What
> is
> 
> I'm interested in doing whatever it will take to get people using the
> library
> or who should be using the library more involved in development.  At
first
> I thought that moving into Jakarta Commons might do that, then when
Apache
> Commons started up I thought maybe that was the right place.  Now it
looks
> like Jakarta Commons is the right place again, although it would be
nice
> not to have to change the package names.  As far as trying, the best
I've
> been able to do is make some noises, but I haven't taken much action
under
> the theory that a couple of other people would lead the charge like
> happened
> with Commons Net.
> 
> >happening in the ORO project in terms of developers?
> 
> Several important contributions were made by some users, but the
> contributions
> didn't keep on coming, so I've never called for a vote on granting
> committership despite their having expressed interested in becoming
> committers.  So despite the contents of the avail file, we're back
into
> a situation where I'm probably the only active committer (and I only
make
> contributions in widely spaced bursts).  I think the committer deficit
> problem would be solved easily if some existing Apache committers who
have
> needs that can be satisfied with jakarta-oro can be convinced to hack
the
> code a little.  I've also thought that jakarta-oro and jakarta-regexp
> ought
> to interact more and have the same committer base, but I've never
started
> a campaign for that.  Asking jakarta-regexp if they're interested in
> implementing the regexp wrapper engine for oro might get that started.
> For now though, if I can squeeze enough time out to do the couple of
> simple things to meet VFS's needs, that may be enough to get more
> involvement and work things out (whether oro sits where it is or
> moves partially or completely into jakarta commons).
> 
> daniel
> 
> 
> 
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]


---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to