+1! On Sun, Jul 18, 2010 at 3:28 AM, Andreas Veithen <[email protected]>wrote:
> All, > > It looks like one of the major pain points when doing an Axis2 release > is producing and deploying the Maven site. The complexity of this part > of the process stems from the fact that in the (deployed) site we not > only have the documentation for the current release, but also the > pages for previous releases. There are a couple of ant scripts to make > this work, but the stuff is difficult to understand, maintain and use. > I think that the added value of linking to the documentation of > previous releases doesn't justify this complexity, and I would like to > radically simplify this. > > Here is my proposal: > > * Change modules/documentation to make it a simple and straightforward > Maven site, without any links to or inclusion of previous releases. > * When doing a release, we archive the site of the previous release by > moving it to a subfolder. > * Once the new axis.apache.org site developed by Milinda et al is > ready, we can link to the archived Maven sites from there. > > Here is my +1. > > Andreas > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > > -- Sanjiva Weerawarana, Ph.D. Founder, Director & Chief Scientist; Lanka Software Foundation; http://www.opensource.lk/ Founder, Chairman & CEO; WSO2, Inc.; http://www.wso2.com/ Member; Apache Software Foundation; http://www.apache.org/ Director; Sahana Software Foundation; http://www.sahanafoundation.org/ Visiting Lecturer; University of Moratuwa; http://www.cse.mrt.ac.lk/ Blog: http://sanjiva.weerawarana.org/
