Hi , for me the only thing i want to see is that you write that we released now the first rc release ;-) The rest is cool as it is.
+1 for release. bye Norman Am Sonntag, den 23.07.2006, 14:23 +0200 schrieb Stefano Bagnara: > Here I am with a newer version: > http://people.apache.org/~bago/james/site-20060723/ > > Please let me know what is the *minimal* set of changes to receive a +1 > to publish this one instead of the current website. > > Furthermore please enumerate any other change that you'd like to see so > that I can try implementing it while fixing the first ones. > > I think that we can proceed with further improvements in future steps. > > I kept 2.2.0 references by now, so we can even publish this before the > 2.3 final release. > > ----------- > > Here are the steps to create it: > > 1a. Checkout james/site/trunk > 1b. "mvn site" > 1c. copy target/site in the destination root > > 2a. Checkout james/jspf/trunk > 2b. "mvn site" > 2c. copy target/site in destination/jspf folder > > 3a. Checkout james/server/trunk > 3b. "mvn site" > 3c. copy target/site in destination/server folder. > > Maybe this could be improved to be automcatically managed by maven in a > single step, but I don't know how now, and this seems to be easy enough. > > PS: very much thanks to Alan because I took his maven2 pom.xml as a > starting point to be able to generate our "james server" site. > > ------------ > > Please note that to support this new site generation I made this changes > to server repository: > 1) added a pom.xml to the root. > 2) moved src/xdocs to src/site/xdoc > 3) create a src/site/site.xml > 4) changed index.xml to remove "james project" references and keep only > "james server" information. > 5) changed our build.xml to be aware of the xdocs move (so that ant > website still works, generating the old website, even if it will have > the new homepage contnt). > > I hope that you don't have problems with the inclusion of pom.xml in our > root. I needed it to be able to use maven2 site generation. I also > included all the dependency declaration (with needed transitive > exclusions) and now maven is able to download dependencies and run > tests/javadocs/reports. This is not intended as a build mechanism for > james because it currently does not use the correct jars, it does not > generate the sar file, does not separate mailets/mailets-api/server jars. > > Stefano > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > !EXCUBATOR:1,44c36a8343387741317926!
signature.asc
Description: Dies ist ein digital signierter Nachrichtenteil
