Stefano wrote: > In roadmap for the 2.3.0 final we have: > Fix m2 projects to not lookup dependencies on ibiblio
Huh? Why do we care about Maven 2 for 2.3.0? I don't care about Maven 2 for anything ever, but it certainly should not be a blocker for JAMES 2.3.0. > to simplify the website build and to include 2.2.0 and 2.3.0 docs We can update our web site indepedendently of the release cycle for the product. > Move server-site documents from james/server repository to > james/site/server repository JAMES 2.3 is a product release, and should not be blocked on anything related to Maven repositories. > Invalid (outdated) urls in config files. > http://issues.apache.org/jira/browse/JAMES-626 Fair enough. Non-critical. > We would also have more feedback on the leak issue opened by Noel The bug exists. I have no time right now to track it down, and everytime I have tried, the JVMs have hung early. :-\ > Either we decide this is not confirmed and close it until we can > confirm it, or we investigate on the cause of the leak. I won't close something that exists. And no one else seems to have either the time or awareness of the problem to look. Whatever is leaking, and I still see it, is slow enough that it can be worked around. I have so far not found any evidence to suggest that it is related to volume. So I'd release with a caveat. > one of my production james (something near rc2) is up since 1 month > and with a default Xmx (64MB) and I had no OOM (this is an almost > default 2.3 configuration with file repositories). I wish I could say the same. :-( --- Noel --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
