> Well, hopefully I'm not the only one looking at this code. > :-) But I'll do a few more tests, and if it doesn't go legs > up, I'll move it to trunk.
I'm applying my local patches and preparing for the tests. > > the merge [is] the foundation upon which [version 3] will evolve. > > For version 3, then ... > > - the last Avalon-specific version? POJO is a v4 branch? > - when we do fork JDK 1.3 off? > > Thoughts? I'm not a committer, but IMHO this new "merge" should be soon a 2.3 release, the last Avalon-specific. v3 will be POJO/jdk1.4 There are no many differences with the current 2.2.1-dev to switch to a 3.0 and I think that it is backward compatible with 2.2.x, isn't it? Stefano --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
