Robert Burrell Donkin wrote:
once i explain some background, it might make a little more sense to you...
apache james is a project: a self-organising community with a single
set of committers developing the source and a single PMC with votes
that bind apache.
apache james server is the flagship product but most development now
goes on in the libraries that compose the server. (one of the current
debates is how far this process of componentisation should go.) each
library is separately versioned and has it's own directory structure
in subversion and subsite on the web.
as you spotted, the downside of this approach is that it's tough to
checkout the latest versions of everything together.
http://svn.apache.org/repos/asf/james/protocols/current/ uses
externals to do this for IMAP and 3.x. so - if people think it would
be useful - i could easily create a 'current' which would checkout
trunk for all 3.x components. not sure whether this would be a good
idea or not. opinions?
this process of componentisation happened mostly in the 3.x
codestream. the 2.x code is monolithic (ATM). to checkout the stable
server source, use
http://svn.apache.org/repos/asf/james/server/branches/v2.3/
- robert
I ran "svn checkout http://svn.apache.org/repos/asf/james/protocols"; and
that downloaded 207 MB in about 10 minutes.
I also ran "svn checkout
http://svn.apache.org/repos/asf/james/server/branches/v2.3";, which
downloaded 30 MB in 2 and a half minutes.
So maybe in the future the docs/wiki could contain your explanation
above about the structure, and maybe a few svn commands. A lot of the
Apache projects seem to just give one svn command to download
everything, which seems to be bad for James.
So for now, is it correct to say that in order to build James from
current source, people should run:
svn checkout http://svn.apache.org/repos/asf/james/server/branches/v2.3
and that to build the new stuff they should run:
svn checkout http://svn.apache.org/repos/asf/james/protocols
Eric MacAdie
---------------------------------------------------------------------
To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org
For additional commands, e-mail: server-dev-h...@james.apache.org
