Re: Sevak Fork.

Johan,

>> Pico and Type2 compat done for Jetty block.  DNA to do. Jo! and 
>> Tomcat to re-port. Monitor introduced (which Avalon one does not 
>> use). Config object and used by all.
>
>
> Good!
>
> Hopefully my meegapatch hasn't broken too badly ;)
>
Oooops I have missed that. Guess I am not monitoring the other mail list 
in my TW account.

> When adding the Jetty config stuff I came across a problem. How can I 
> add dependencies on extra libraries used by Jetty? All kinds of libs 
> are needed for SSL etc. Argh, I'm really, really bad at Maven builds 
> :( For Sevak I created a download target that downloaded a Jetty dist 
> and included it almoast completely.
>
Dude, you have to get with the Maven programme, it does make life easier 
and does download all the dependancies from Ibiblio for Jetty.  Aslak 
set it up for me, so I guess I had the same original adoption hurdle 
problem you have.

> Btw. do we want to do this? Only Peter D. seemed to want the 
> possibility to use standard Jetty configurations for none Jervlet web 
> applications.
>
I'm not really sure what you're talking about here ?  Elementary Config  
was done in the last commit.

> Paul, did you have a look at Tomcat and Jo! already?

Nahhh, like others I am more keen on the Jetty one.  Unless someone else 
wants to handle getting the source from Sevak and doing the port I'll 
find time in a few weeks.

- Paul

-- 
http://www.thoughtworks.com -> The art of heavy lifting.
Home for many Agile practicing, Open Source activists...