Re: My Status, and James RoadMap

2004-06-18 Thread Serge Knystautas
Noel J. Bergman wrote: Well, as I said, people can try whatever databases they want. But I don't see the point of using it if you can't distribute it. Seems to me that the primary reason for it is convenience/turnkey distribution. The ASF may not feel it is open source enough, but that's our req

RE: My Status, and James RoadMap

2004-06-18 Thread Noel J. Bergman
>>>Would you not recommend HSQLDB? >> People can try whatever databases they want. But IIRC, the HSQLDB license >> is not compatible with distribution by James. > Does this really matter to anyone but the ASF (or anyone who would > redistribute James)? Well, as I said, people can try whatever dat

Re: My Status, and James RoadMap

2004-06-18 Thread Serge Knystautas
Noel J. Bergman wrote: Would you not recommend HSQLDB? People can try whatever databases they want. But IIRC, the HSQLDB license is not compatible with distribution by James. Does this really matter to anyone but the ASF (or anyone who would redistribute James)? -- Serge Knystautas Lokitech >>>

RE: My Status, and James RoadMap

2004-06-18 Thread Noel J. Bergman
> Would you not recommend HSQLDB? People can try whatever databases they want. But IIRC, the HSQLDB license is not compatible with distribution by James. --- Noel - To unsubscribe, e-mail: [EMAIL PROTECTED] For additio

RE: My Status, and James RoadMap

2004-06-18 Thread mike
Would you not recommend HSQLDB? At 09:19 PM 6/18/2004, Noel J. Bergman wrote: > Where do plans for IMAP getting a permanent store fit in the scheme of > plans? IMAP needs some champions to work on it. Many have offered, few if any have actually contributed. In terms of a persistent store, Jason W

RE: My Status, and James RoadMap

2004-06-18 Thread Noel J. Bergman
> Where do plans for IMAP getting a permanent store fit in the scheme of > plans? IMAP needs some champions to work on it. Many have offered, few if any have actually contributed. In terms of a persistent store, Jason Webb and I had worked out a scheme using the current store technology and a na

cvs commit: james-server/www FAQ.html

2004-06-18 Thread noel
noel2004/06/18 19:44:05 Modified:src/xdocs FAQ.xml www FAQ.html Log: Update upgrade FAQ Revision ChangesPath 1.27 +2 -1 james-server/src/xdocs/FAQ.xml Index: FAQ.xml =

[EMAIL PROTECTED]: james-server/james-server failed

2004-06-18 Thread Gump Build Robot
t-launcher.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant-nodeps.jar:/usr/local/gump/public/workspace/ant/dist/lib/ant.jar:/usr/local/gump/packages/javamail-1.3/mail.jar:/usr/local/gump/public/workspace/avalon/framework/api/target/avalon-framework-api-20040618.jar:/usr/local/gump/public/w

Re: My Status, and James RoadMap

2004-06-18 Thread Mark Livingstone
Hi Noel, Where do plans for IMAP getting a permanent store fit in the scheme of plans? I went to the mentioned WIKI site but no real mention. After Maths exam on Tuesday, I will have a month or so to start testing ;-D Also, I hope to play with IBM's Cloudscape for another project, does James sup

Re: My Status, and James RoadMap

2004-06-18 Thread Serge Knystautas
Noel J. Bergman wrote: We might want to record our collective ideas on the wiki, where we already have others: http://wiki.apache.org/james/JamesV3. Looks like we've already done some, and have new ideas on others. Serge would probably suggest, and he's right, that we start to use JIRA to layout

RE: My Status, and James RoadMap

2004-06-18 Thread Noel J. Bergman
> Are we to consider releasing James with Merlin instead > of Phoenix for instance..? I'm considering what we've been considering for over a year: migrating from the old version of Phoenix to the "current" version of Phoenix in our CVS, and the current Avalon components. Phoenix is a proven and s

Re: My Status, and James RoadMap

2004-06-18 Thread Danny Angus
+1 to everyone else's plans. But.. Noel, what do you have in mind vis-a-vis Avalon? Are we to consider releasing James with Merlin instead of Phoenix for instance..? My own plan.. and in this order.. a) Revisit the Mailet API experimental changes, particularly those which haven't found favo