Shouldn't the patchs URL be : http://svn.apache.org/repos/asf/james/project/trunk/*
instead of http://svn.apache.org/repos/asf/james/trunk/* ? Maybe you should also provide a patch for : http://svn.apache.org/repos/asf/james/current/pom.xml I'm not a SVN expert, so can someone else review the SVN process ? Cheers, Benoit Le 21/09/2015 10:57, Matthieu Baechler a écrit :
Hi, I tried to describe all steps needed to merge the james modules as proposed previously. Compared with previous proposition, I just changed the "james" folder into the "server" folder for more consistency. We should get the following tree into james-project module : james-project |---- server |---- mailbox |---- mailet |---- mpt |---- protocols If you agree, we should do : in https://svn.apache.org/repos/asf/james/project/trunk : svn mv http://svn.apache.org/repos/asf/james/server server svn mv http://svn.apache.org/repos/asf/james/mailbox mailbox svn mv http://svn.apache.org/repos/asf/james/mailet mailet svn mv http://svn.apache.org/repos/asf/james/mpt mpt svn mv http://svn.apache.org/repos/asf/james/protocols protocols I chose "svn mv" to prevent confusion about where are modules actual trunk located. Then we have to update http://svn.apache.org/repos/asf/james/current accordingly with the following command : svn propset svn:externals http://svn.apache.org/repos/asf/james/current hupa https://svn.apache.org/repos/asf/james/hupa/trunk jdkim https://svn.apache.org/repos/asf/james/jdkim/trunk jspf https://svn.apache.org/repos/asf/james/jspf/trunk mime4j https://svn.apache.org/repos/asf/james/mime4j/trunk postage https://svn.apache.org/repos/asf/james/postage/trunk jsieve https://svn.apache.org/repos/asf/james/jsieve/trunk project https://svn.apache.org/repos/asf/james/project/trunk skin https://svn.apache.org/repos/asf/james/skin/trunk Then, to update the documentation and the "project" pom, you have to apply the attached patches and finally commit all this. Please review this process then I'll ask a commiter to kindly apply it if people agree. I can put everything in a JIRA if needed. Cheers, --------------------------------------------------------------------- To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org For additional commands, e-mail: server-dev-h...@james.apache.org
--------------------------------------------------------------------- To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org For additional commands, e-mail: server-dev-h...@james.apache.org