2010/1/3 Norman Maurer <nor...@apache.org>: > Hi all, > > the last days I worked on getting a pure spring deployment complete > for James so we could remove the whole phoenix stuff etc. The code is > now complete and is working here in production without problems.
Good! > You can find the code under: > > https://svn.apache.org/repos/asf/james/server/sandbox/active/pure_spring_deployment/ > > The pure spring deployment use JSR250 todo all the dependency > injection. It still support the Avalon lifecycle stuff to be able to > use the cornerstone components in the deployment. I'd like to see http://svn.apache.org/repos/asf/james/server/sandbox/active/pure_spring_deployment/spring-deployment/lib/ removed (or the libs moved to stage) and the stage folder cleaned up to remove dependencies no more needed, too. > I would like to merge it to trunk and remove the phoenix deployment at > all. This would allow us to just have one deployment (which is still > active developed) and hopefully more new developers will get > interested in James again. When its merged I will add some docs howto > "migrate" from phoenix deployment to the new one (its straight > forward). After this is done I would like to cut a milestone so we get > some more testers. > > So here we go: [X] +1 Yes please merge it so we can get rid of all the "dead" stuff ;) I didn't deeply review the changes, but I think james trunk is getting too old, we should stop looking at the past and simply move on. I'm not sure spring is the container I'd like to see in the next james, but spring can be a needed step. Maybe from spring we can then move to spring-dm, osgi bluprints, karaf. Stefano --------------------------------------------------------------------- To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org For additional commands, e-mail: server-dev-h...@james.apache.org
