Hi all,
Previous release, 1.2, was made in November 2000 [1], and I think it's
time to make a Regexp 1.3 release. I propose to make it asap (this or
next week). Current development version contains fixes to several bugs
which are exposing themselfs often in the real life usage of the
package,
and including the entire message so it has
an opportunity to exercise oversight.
In message [EMAIL PROTECTED], Vadim Gritsenko writes:
Hi all,
Previous release, 1.2, was made in November 2000 [1], and I think it's
time to make a Regexp 1.3 release. I propose to make it asap (this or
next week
The Regexp team announces the availability of Jakarta Regexp 1.3 release.
This is primarily maintenance release containing several bug fixes
accumulated since the last Regexp release. Complete list of changes is
available at: http://jakarta.apache.org/regexp/changes.html
Regexp comes in one
robert burrell donkin wrote:
the apache software foundation policy concerning releases is now that
all releases should be available only through:
1. the main mirrored ASF distribution directories
2. the main ASF archives
the latest 1.3 release is available through the mirrors but the older
Walid Joseph Gedeon wrote:
Hello all,
Euh, ping! (Am I on, or is it really a low traffic list? :)
Yes, you are; and yes, it is.
I was working on an interesting project and found the need to extend
the Regexp functionality by defining a meta-structure that combines
regexps together...
Oleg Sukhodolsky wrote:
Hi,
about two months ago I've submitted suggested fixes for two bugs.
I did it by attaching suggested fixes to bug-reports (one of two ways
suggested by apache) and so I'm not sure if they were noticed.
I think I missed those emails...
Here is a list of the bugs:
|
Oleg Sukhodolsky wrote:
Hi,
We have only two unfixed bugs:
| 9153|New|Nor|2002-05-16|RE.match() hangs when using {n,m} |
unlikely to be fixed soon,
|24234|New|Nor|2003-10-29|Doesn't seem to be a way to use '\' in subst with |
has a fix which can be applied
Also is is marked
Bruno Marquié wrote:
Hi all,
We have a compatibility problem between Open Office and the POI API to
manage Excel Files.
Wrong list? Try POI-dev list.
Vadim
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands,
Henri Yandell wrote:
Anyone mind if I put together a vote and request to infrastructure to
migrate the regexp module from CVS to SVN?
While I'm not a regexp developer, I'd like to a) get an experience of
the migration, and b) help move quieter Jakarta sub-projects over.
I'd be expecting to ask for
Henri Yandell wrote:
I just checked it out, added, moved, removed, branched etc. Seems ok.
svn log returns lots of stuff going back to 2000.
Good :)
So let me know if you're good to go Vadim.
Looks good - but I don't know what is branches/jakarta and tags/start - both
have only LICENSE file.
Ramesh Babu Mandava wrote:
Hi:
I am facing problem in checking out jakarta-regexp module. Is there
any problem with CVS server?
Anybody looking at the problem?
It's in SVN:
http://svn.apache.org/repos/asf/jakarta/regexp/trunk/
Vadim
Manik Surtani wrote:
Where is this wiki?
You can use jakarta wiki:
http://wiki.apache.org/jakarta/
Vadim
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Carsten Ziegeler wrote:
Hi,
could you please upload the 1.4 release (and perhaps older once) to our
apache java-repository at http://www.apache.org/dist/java-repository
If you look at Ibiblio you'll find older releases there under the regexp
directory. So you can either upload them to
Erik Hatcher wrote:
Would it be possible to add a public getter to return this prefix?
Hi Erik,
Given that instructions already have public accessor, I have no issues with it.
Added.
I realize that Jakarta Regexp is not that maintained,
Hey, easy, it's quite well maintained - it has
Sinha, Sahasrangshu(Anshinsoft) wrote:
Hi,
We use regexp package in our application. We have encountered an error
while parsing a long string (with over than 8000 characters) as a value
of a tag during SWIFT processing.
encountered exception
java.lang.StackOverflowError
at
Hi All,
With 5 recent bug fixes [1], one *major* speed improvement for {m,n} closures
[2], with other various optimizations to compiler and runtime, and with previous
release published sometime back in 2005 [3], now is the best, or at the very
least, really good time to to cut next, 1.5
], is that correct?
Vadim
[1] http://jakarta.apache.org/commons/releases/release.html
[2] http://people.apache.org/~vgritsenko/regexp/
[3] http://www.apache.org/legal/src-headers.html
Best regards
Henning
On Tue, 2007-03-13 at 22:12 -0400, Vadim Gritsenko wrote:
Hi All
sebb wrote:
Also I think I need to update
headers as per [3], is that correct?
You also need a NOTICE file [3]
Updated license headers, added NOTICE to zip/tar.gz.
The LICENSE and NOTICE files ought to go into the jar as well, as the
jar may well be used on its own.
Added both files to
18 matches
Mail list logo