Still no response from infra https://issues.apache.org/jira/browse/INFRA-5657
So I don't know how to start importing content... What to do is: * upgrade to parent <version>28-SNAPSHOT</version> * add a property <commons.site.path>exec</commons.site.path> which contains the project path relative to commons.a.o And that's it :-) parent will need a change regarding a property <commons.scmPubUrl>https://svn.apache.org/repos/asf/commons/cms-site/trunk/${commons.site.path}</commons.scmPubUrl> which will be probably <commons.scmPubUrl>https://svn.apache.org/repos/infra/websites/production/commons/content/${commons.site.path}</commons.scmPubUrl> No way to test/deploy content atm. 2012/12/28 Phil Steitz <phil.ste...@gmail.com>: > On 12/18/12 2:32 PM, Olivier Lamy wrote: >> 2012/12/18 Olivier Lamy <ol...@apache.org>: >>> 2012/12/18 Ralph Goers <ralph.go...@dslextreme.com>: >>>> On Dec 18, 2012, at 2:11 PM, Olivier Lamy wrote: >>>> >>>>> 2012/12/18 Ralph Goers <ralph.go...@dslextreme.com>: >>>>>> On Dec 18, 2012, at 1:03 PM, Olivier Lamy wrote: >>>>>> >>>>>>> Maybe could be simpler with committing your staged versionned site to >>>>>>> log4j2-xxx (tru the maven plugin) for review and then modifying >>>>>>> .htaccess file (too prevent huge checkout on your machine and to >>>>>>> modify a symlink this probably won't work for windauze folks). >>>>>>> With this, just to do: deploy the site tru scm-pub plugin then when >>>>>>> vote passed only modify the .htaccess file >>>>>>> (that's just an idea) >>>>>> If you follow the instructions on the wiki the checkout doesn't have to >>>>>> be huge. You will get the main part of the web site and then you can >>>>>> get the subproject parts you want individually. >>>>>> >>>>>> I noticed that when you check out the site on Windows you get a file >>>>>> that represents the symlink. Of course, it doesn't do anything useful on >>>>>> windows as it would on a unix-based system, but I would expect you could >>>>>> hand modify it to update the link. >>>>>> >>>>>> What does the scm-plugin do to deploy the site that makes it easier than >>>>>> doing a cp and svn commit? >>>>> Part of the build so no manual steps (add, commit etc...) >>>>> And do some cleanup: If content generated doesn't produce anymore >>>>> file(s) which were in svn path they will be "svn rm". >>>> Is this the plugin that has to checkout a copy and do a diff so that it >>>> can then figure out what to remove? If so, then it is going to take >>>> longer than the process I outlined as each commit to the production goes >>>> to a new location in svn. >>>> >>> yup. >>> In your case (only versionned site/new location) that doesn't help. >> But in the maven site case that helps as there is huge content. >> Having a full copy is a bit too huge and not very useful. >> So with using the plugin, just say you want to commit to >> http:///blabla/bar/beer/wine, if the path doesn't exists it will be >> created then content committed in. > > Tick, tock, guys. We are about to turn into a pumpkin :) > > I have some time over the next few days to help, but I have sort of > lost the plot. Sorry to be slow and ignorant, but can someone post > or point to a "horsey, ducky, lamby" set of instructions that I can > use to start helping migrate stuff? I will start with [math], > [dbcp] and [pool] if I can get pointed in the right direction. > > Thanks! > > Phil >> >>>> Ralph >>>> >>>> >>>> --------------------------------------------------------------------- >>>> To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org >>>> For additional commands, e-mail: dev-h...@commons.apache.org >>>> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org >> For additional commands, e-mail: dev-h...@commons.apache.org >> >> > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org > For additional commands, e-mail: dev-h...@commons.apache.org > -- Olivier Lamy Talend: http://coders.talend.com http://twitter.com/olamy | http://linkedin.com/in/olamy --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org For additional commands, e-mail: dev-h...@commons.apache.org
