Alan Cabrera wrote:
I'm going to investigate what it takes to convert James to maven 2 and
XBean. I realize that others may not like that idea. My thinking is to
convert a small piece and solicit comments.
I think that you should try to split the 2 processes (maven2 / xbean).
Our documentation and our build process is outdated and difficult to
keep updated so I would be happy to evaluate different solutions
(maven2). Other James committers (Noel, for example) don't like the idea
to switch to maven2 (a search in the mailing list archives should return
results for this).
About containers/components I don't know anything about XBeans.
Noel suggested to try to move to OSGi.
I think we should try to move away from Phoenix but we can safely keep
avalon: I read something done by Cocoon to run avalon inside an OSGi
container.
Another step would be to replace cornerstone components in favor of
"jakarta-commons" components.
I also investigated on using ActiveMQ in place of the spoolmanager of
James but I stopped because I think we should change our repository
interface before and we can't do that before 2.3.0 final will be out.
It would make sense if I did this in a sandbox. Would it be ok if I had
a little corner to play in?
I don't think there is a way to give you access to a branch or a
particular folder of the james subversion repository.
Maybe you should start working in your local sandbox and eventually add
a jira issue where submit your work for review.
Stefano
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
