Noel J. Bergman wrote:
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.
Well, not an issue as I'm faster.. ;-)
Our website and the documentation site for james 2.3.0 is created with
maven2, so this is why I care of it as part of the release.
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.
I prefer to have consistency between what we put in the documentation
site for 2.3.0 and what as been released in 2.3.0: version specific docs
are part of the server distribution.
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.
Non an issue: I think you concentrated too much on this non-issue...
This will not block anything because I worked hard to publish the
updated site including the last documentation.
Invalid (outdated) urls in config files.
http://issues.apache.org/jira/browse/JAMES-626
Fair enough. Non-critical.
I'll fix this tomorrow. We waited 2 years for a release, I don't think
that we want to release with bad urls if we know we have them.
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. :-\
I don't say that the bug does not exists: the bug may be everywhere, so
if we don't know if it is in james or in connector or in the jvm is not
of help.
Norman is running an *Xmx5M* james using mysql since few weeks, and I'm
running an Xmx64M using files repository since a month: so it is nothing
that is triggered so often in standard configurations.
I think we can wait at least for you to send us the cleaned config.xml
before releasing 2.3.0: I think few more eyes looking at your config.xml
worth the wait.
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.
Again, please instead of replying to this messages you could help
sending us more informations to be able to investigate and reproduce it.
you still cannot be sure the bug exists in james source code or in james
bundled libraries. Imo we have to fix this: I'm sorrt but if no one is
able to reproduce it but you then it will be closed as won't fix.
I don't say there is no bug, I simply say that we don't need that issue
opened if we don't have any clue on the cause of the bug and we don't
have complete informations about the environment (and the configuration)
where the bug has been experienced.
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
Please try the time to clean your config.xml and add it to JIRA. If you
don't have this time please at least select some trusted people and send
it privately. I hope you can find at least one people you trust that
will have the time to clean it and upload it to JIRA.
Stefano
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
