I'm wondering what is wrong with exposing only the latest Draft docs and just forget about publishing docs on each release? Thus will simplify keeping page update-2-date and reduce amount of time spend on preparing new release.
Regards -- Łukasz + 48 606 323 122 http://www.lenart.org.pl/ 2013/10/30 Lukasz Lenart <lukaszlen...@apache.org>: > There is one problem - to include docs in the assemblies they must be > downloaded with wget (there is no support for SiteExporter in > Jenkins). > So, I must add a task which will export docs from Confluence and put > them under /docs and then with wget they can be downloaded to Jenkins > and assembled :\ > > ech... bit messy solution, but I don't see other option. > > > Regards > -- > Łukasz > + 48 606 323 122 http://www.lenart.org.pl/ > > 2013/9/10 <umeshawas...@gmail.com>: >> +1 for that >> It will reduce a lot of confusion >> ------Original Message------ >> From: Lukasz Lenart >> To: Struts Developers List >> ReplyTo: Struts Developers List >> Subject: Re-organise docs >> Sent: Sep 10, 2013 12:18 PM >> >> Hi, >> >> I thought a bit about our docs - for each main branch we provide docs, >> i.e. /release/2.3.x/, /release/2.2.x/ etc. We also expose draft docs >> as /development/2.x - all thus leads to mess when we must update >> something or so. >> >> So maybe just instead of many places with docs we should expose the >> latest related to last release under path /docs and redirect to >> Confluence in case of draft docs? >> >> >> Regards >> -- >> Łukasz >> + 48 606 323 122 http://www.lenart.org.pl/ >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: dev-unsubscr...@struts.apache.org >> For additional commands, e-mail: dev-h...@struts.apache.org >> >> >> >> Sent from BlackBerry® on Airtel --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@struts.apache.org For additional commands, e-mail: dev-h...@struts.apache.org
