Andrew Newton wrote:
>
> I'd like to preface this e-mail with the fact that I've spent the last year
> and a half off doing servlet development on a commercial Web application server
> and I am really out of touch with the mainstream state of Apache JSERV/Jakarta,
> java.apache.org, and all that. The last time I played with any of it, JSERV
> was 0.9.11 or something and JSP and Jakarta were non-existent.
>
> Given that handicap, I grabbed the Jetspeed code from anonymous cvs yesterday
> and built it today. As a newcomer to Jetspeed, here are the problems I had
> doing the build.
>
> 1) The installation instructions say to get Xerces-J even though it is distributed
> in the lib directory (since Xerces is an Apache project, can't it be distributed
> with Jetspeed?). This is minor, but the fact that it is not put in the build.sh
> file will stop a build.
>
> 2) ECS is not mentioned in the installation notes, but is needed (can't it also
> be distributed with Jetspeed since it is an Apache product?).
>
> 3) Cocoon is not in the build.sh file.
>
> 4) Castor is not in the build.sh file.
>
> 5) Village is in the build.sh file, but apparently not needed.
>
> 6) Turbine is not in the build.sh file.
>
> 7) The build.sh file appears to be for Turbine and not Jetspeed.
Yes. The above isn't perfect but reflects it's beta stage. I would
take a look at the latest CVS as some of the above is corrected. The
docs are tweaked and Cocoon and Xerces are in the build.
> I'd like to contribute to Jetspeed and would be willing to help with such issues.
> In fact, I feel that it would be a good way for me to learn the software. In
> other words, would anyone mind if I got my feet wet by fixing some things which
> seem to be minor details?
Sounds good. I would just start hacking on it and sending off diffs.
If you still want to keep hacking on it then we should give you CVS
write. I agree these are issues to be worked out... I have just been
lazy to fix them.
> I still don't have Jetspeed running, but I believe that has much more to do with
> my lack of understanding Jakarta than anything else. I'm gonna keep plugging
> away at it.
>
> Incidentally, there was some talk about using the IBM 1.1.8 JDK with Jetspeed
> and Jakarta. I've been unable to get Jakarta to work with IBM's JDK under Linux,
> even though it works with the Blackdown/Sun RC2 JDK. After digging around,
> I saw some mention that Tomcat 3.1M1 had a workaround for some JDK's with a
> particular problem. Does anyone know anything about this?
Yes. Actually I do Tomcat work too so I am running the latest version
from CVS. I think 3.1M1 ran fine with JDK 118 but I am not sure. My
cvs build is like a week old. Clearly it is good to say that JDK 118 is
good since Tomcat 3.1 final will support that.
Kevin
--
Kevin A Burton
Senior Software Engineer
Kendara Inc
http://www.kendara.com
Mobile: 408-910-6145
Linux - The revolution will NOT be televised
--
--------------------------------------------------------------
Please read the FAQ! <http://java.apache.org/faq/>
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
Archives and Other: <http://java.apache.org/main/mail.html>
Problems?: [EMAIL PROTECTED]
