A bit of concern here..
I'm working constantly with 3.3 cvs version and have a lot of classloader
issues and class context reloading issues.. (the lot means : it happens a
lot..) Some are solved by moving the jar file to the root lib dir (didn't
find the time to get a nice reproductions scenario yet, to see if a fix
works). The class ,eh actually context reloading, issue is in bugzilla and
didn't get around to fix that either. Reproducing it is for now only
possible in our very big webapp. (reloading the context after a certain
number of servlets is loaded will give state not ready for one servlet,
which, you probably guessed already, our main entry point in the system).
In short : How long do I have to fix the problems and from who can I get
some help for these class(re)loading issues?
TIA
Mvgr,
Martin
> -----Original Message-----
> From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED]]
> Sent: Tuesday, August 14, 2001 11:57 PM
> To: [EMAIL PROTECTED]
> Subject: Nightly builds for 3.3
>
>
> Hi,
>
> Nightly builds for 3.3 are out, it seems somehow they are destabilising
> the system and Pier asked me to find a different machine.
>
> I'll try to do that, the sourceforge build machines seems nice ( but I'll
> have to do some tricks ), or I could use my home machine ( which seems to
> be faster anyway ).
>
> This isn't a big deal, most development in the 3.3 main tree has been
> completed, the code is stable and in beta. The only thing that's going to
> change are modules - but mod_jk and ajp14 were not included in the
> nightly, and all modules I'm working on are just add-ons.
>
>
> As previously discussed, 3.3 core can be considered frozen, we're doing
> the final reviews to make sure it'll be able to handle any kinds of
> modules. Testing 3.3 with those add-on modules is important, and that's
> where I'll focus. Testing 3.3 "basic" every few hours is no longer that
> important.
>
>
> Costin
>
>
>
