> It would be nice to get to a position where patches are not applied
against
> non-development branches (i.e. only accept patches against HEAD).
The point is that we had two development branches. One based upon the
current stable API, and the other with some experimental changes.
> What about migration to maven and some restructuring to-boot.
It could happen, but doesn't help.
> 2. seperation api and impl makes james a more reusable proposition (when
> viewing james a compositie component)
You are missing the point that the API changed, and code relying upon the
new API would not be compatible with the older API. Like how a program
requiring java.nio won't work with JDK 1.3.
> 4. because I can help
Makes it worth looking at, but still doesn't help with the core problem.
> Somewhat off-topic but releated to James is some work I've been doing
> recently on the openim project. Alexis (the guy heading up all of this)
> has been reusing james components as part of work on getting a user
> object model in place.
I have been trying to get Alexis to bring that code here, and make it a
James sub-project to integrate as a new service in the server, but he hasn't
taken up on it.
> the openim/james work has been hampered by a lack of api/impl seperation
> on the individual james components (for example - to reuse the user
> repository the solution ends up being dependent on the mailet impl
> classes, activation.jar and mail-1.3.1.jar - which is kind of icky).
That will change when we switch to using JNDI for the user repository. I've
started to prototype that here, which is one reason I'd like to clean up the
branch split.
> You may want to take a look at the merlin website. Its totally generated
via
> a maven based build. Site updating and distribution building is now
almost
> trivial (ie. around 5 mins for a totally new site and distribution
archive).
Building ours is trivial, too. The problem is that it is in two branches.
We need to move it into the james-site module, and adjust the build process
accordingly. That said, we have looked at both Maven and Forrest (perhaps
Maven with Forrest doing the actual rendering), but no one has stepped
forward to do that work.
--- Noel
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
