Struts 1.0 does not use the Commons packages, which is why you did not find
them bundled there. It uses its own versions, which in fact is where those
particular Commons packages originated.

The Struts web site reflects the latest in Struts, which is currently 1.1 in
development. Struts 1.1 does use the Commons packages, which is why you
found them there.

--
Martin Cooper


----- Original Message -----
From: "Randall Parker" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Wednesday, August 01, 2001 11:31 PM
Subject: Commons jars not found in v1.0 binary distributions


> I downloaded from here
>    http://jakarta.apache.org/builds/jakarta-struts/release/v1.0/
> both jakarta-struts-1.0.tar.gz  and jakarta.struts-1.0.zip and found that
neither has the commons jar files that this URL leads me to
> expect:
>    http://jakarta.apache.org/struts/installation.html
>  which says:
>   "If you are utilizing a binary distribution of Struts, then the
correspondng JAR files are included in the lib directory."
>
> No, this is not true. The commons-*,jar files mentioned further down the
page are not included in the Struts v1.0 binary distribution.
> Anyone know where these jar files can be downloaded from?
>
> I went here:
>    http://jakarta.apache.org/commons/
>  and hit various links that did not work.
>
> This works:
>    http://jakarta.apache.org/commons/beanutils.html
> but the CVS link off of it:
>    http://jakarta.apache.org/cvsweb/index.cgi/jakarta-commons/beanutils/
> does not work.
>
> Also, these links do not work:
> http://jakarta.apache.org/cvsweb/index.cgi/jakarta-commons/digester/
> http://jakarta.apache.org/cvsweb/index.cgi/jakarta-commons/collections/
>
> I do this to get FOP from CVS:
>   REM Use password: anoncvs
>   cvs -d :pserver:[EMAIL PROTECTED]:/home/cvspublic login
>   cvs -d :pserver:[EMAIL PROTECTED]:/home/cvspublic checkout xml-fop
> Anyone know what names to use to check out the appropriate stuff for the
collections jars?
>
> Better yet, any way to just download the jars already built?
>
>
>
>
>


Reply via email to