On Fri, Jun 17, 2011 at 6:31 PM, Simone Tripodi <simonetrip...@apache.org> wrote: > Thanks a lot for the suggestions Phil, very appreciated!!! > I honestly thought that there was some Maven trick somewhere that I > wasn't aware of :P > So, I think I'll proceed following the first approach, I see it > quicker and easier :) <snip/>
Along these lines: * Check out release sources from SVN tags (or grab source distros) for all prior versions you want sites deployed for * For $version in versions, change site URL in pom to be c.a.o/$component/$version (instead of c.a.o/$component) and deploy (or you could manually upload) * Check out trunk, update site.xml or equivalent (see bottom of [scxml] site.xml [1] for example of menu with other versions) and deploy -Rahul [1] http://svn.apache.org/repos/asf/commons/proper/scxml/trunk/src/site/site.xml > Online soon, stay tuned! :D > Simo > > http://people.apache.org/~simonetripodi/ > http://www.99soft.org/ > > > > On Fri, Jun 17, 2011 at 11:59 PM, Phil Steitz <phil.ste...@gmail.com> wrote: >> On 6/17/11 12:24 PM, Simone Tripodi wrote: >>> Hi all guys, >>> because of my fault, we've been notified more than once - and there's >>> an open Issue[1] - about bad links on Digester site :( >>> Since SNAPSHOT artifacts have already been successfully deployed on >>> Nexus, I would like to publish also the new Digester snapshot site >>> with updated documentation, so users can start to play with the new >>> component version - but I now have the need to fix those links >>> otherwise the 2.X version would lose the doc, and that would be really >>> annoying. >>> Does someone know how we published that documentation in the past >>> (before I join, I mean), so I can apply the fix? >> >> As with all things Commons, a little comparative shopping always >> works best ;) >> >> Have a look at the [beanutils] site, which maintains docs for two >> versions simultaneously, or [math] or [dbcp], which like most other >> commons sites maintains prior version javadocs on the site. What we >> usually do for the javadoc is just manually push the files to p.a.o >> and link them. Same could work for user guide type material. Just >> create an "old" version, tar it, scp it to p.a.o, unpack somewhere >> and adjust links. Alternatively, you can spend n hours trying to >> figure out how to cajole maven into creating a site that includes >> all of the content. I strongly recommend the first route. Maybe >> Niall can chime in with comments on how he did the [beanutils] stuff. >> >> Phil >>> Many thanks in advance, any help would be really appreciated! >>> All the best, >>> Simo >>> >>> [1] https://issues.apache.org/jira/browse/DIGESTER-147 >>> >>> http://people.apache.org/~simonetripodi/ >>> http://www.99soft.org/ >>> --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org For additional commands, e-mail: dev-h...@commons.apache.org