Hey Guys, Reading all of this makes me truly sad. I started with JAMES roughly two months ago - and even though you are maintining a good documentation it took me 2 month to figure out why I was not capable of starting up the server with the current JDK and and one of the first stable MySQL-NT 5.0 builds. Actually I intended to dig into development and contribute to. However, having anything done with Java/JSPs since three years, I had to learn that there is no strait way into the avalon framework, different logging mechanisms, different connection pooling adapters, etc. I must admit that I was truly a bit naïve thinking to start with developing extensions within a minute, especially considering the fact that I have no much free time at hand. The point that I intend to make: I am able and willing to code, but in order to be able to design a specific part for JAMES I am in the lack of sufficient knowledge; and for my needs I did not find an appropriate compendium - searching the archive is fine, but cumbersome and often misleading when you are new to it. Please do not regard this as criticism - I am in software development for quit a while. I just wanted to submit a view from "outside" the community
Best Regards Bernhard -----Ursprüngliche Nachricht----- Von: Serge Knystautas [mailto:[EMAIL PROTECTED] Gesendet: Donnerstag, 19. Januar 2006 02:58 An: James Users List; [EMAIL PROTECTED] Betreff: Re: James dead? On 1/18/06, Jesper B. Kiær <[EMAIL PROTECTED]> wrote: > What are the > > - visions for project? > - roadmaps > - plans > - ... That's all in the wiki. The near-term changes are in JIRA's release notes (our issue tracker), and of course mailing list archives if you want to search a bit. IMO James is reasonably documented compared to most open source projects, largely because it's stabilized and hasn't had radical changes. We do not have as much active development as other projects, but the developer list has sustained traffic even if at low volume. Please also note that these are surrogate indicators of a project's quality. James is a very excellent replacement for sendmail. I would never consider it a replacement for Exchange, but it does what it tries to do very well. Sendmail has much more documentation and developer traffic, but I have yet to figure out how to edit and compile the sendmail configuration files to manage what I consider basic smtp gateway functionality. Maybe it's our name that causes us problems. When we say "Enterprise Mail Server" we mean enterprise messaging like routing and logging and transforming and processing. I think unfortunately for us, a large number of people hear "Enterprise Mail Server" and they think we should be able to handle imap and calendar and contacts for 20-100 people (Exchange). We do not do that (at least not until someone contributes that). -- Serge Knystautas Lokitech >> software . strategy . design >> http://www.lokitech.com p. 301.656.5501 e. [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
