The build files for tc4 refer to jakarta-regexp-1.2.jar.

However, the regexp project currently builds a file called
"jakarta-regexp-1.3-dev.jar".  The jakarta-regexp-1.2.jar is nowhere
to be found, so the build breaks for someone (like me) following the
instructions for a clean checkout-and-build.

To forestall this sort of thing from happening in the future, let's
just check a binary jar file into jakarta-tomcat-4.0 as
jakarta-tomcat-4.0/lib/jakarta-regexp.jar

That way our build will work even if jakarta-regexp changes the name
of their jar, or breaks the interfaces, or whatever.  Plus, if they do
rev their release, and we want to incorporate it, we can do it by
checking in their new jar as our old name, and then we don't even have
to change the build files.

I've made the changes locally... Tell me if I shouldn't check it in.

 - Alex

P.S.  I'd like to propose that jakarta-regexp project name all their
jars jakarta-regexp.jar no matter what version they are.  This doesn't
affect the decision here.


-- 
Alex Chaffee                       mailto:[EMAIL PROTECTED]
jGuru - Java News and FAQs         http://www.jguru.com/alex/
Creator of Gamelan                 http://www.gamelan.com/
Founder of Purple Technology       http://www.purpletech.com/
Curator of Stinky Art Collective   http://www.stinky.com/

Reply via email to