The repo is listed here: https://github.com/apache/incubator-tamaya/blob/master/pom.xml#L142 I'm not sure, but I suspect if you do a mvn site-deploy it'll build and upload to that SVN repo.
We may need to do some other clean up if we're moving away from checking in directly to SVN (I believe last time I asked, we were using direct SVN commits + CMS publishing). I agree its confusing, this is why I brought up gitpubsub (It strikes me that I probably wasn't clear in what I was describing, mostly because I don't understand how we build right now. Anatole, can you confirm what I've described? Looks like we have a mix of static files and markdown in the SVN URL). With gitpubsub, you should be able to just do a "mvn site-deploy" to check into some git repo (e.g. incubator-tamaya-site), which the ASF infra picks up on and uses to publish the website. I mentioned things like jeckyll as that's what many projects are using to build their websites, but nothing would be a hard requirement. At the end of the day, infra just wants a repo that they can point to with the website's contents in it. I think either way we need to move the site code into a separate "tamaya-site" module in SCM so that the site settings aren't applied to every module. Currently with CMS you need to commit to an SVN repo, wait for it to build, then verify in staging and publish via CMS. ( https://cms.apache.org is the URL to do the publishing). John On Fri, Apr 22, 2016 at 6:54 PM Oliver B. Fischer <[email protected]> wrote: > As far as I understand I have to put the whole site in a specific > Subversion repository and then it will be published? I read > http://www.apache.org/dev/cms.html but it wasn't helpfull IMHO. > > Am 22.04.16 um 12:24 schrieb Anatole Tresch: > > +1 for publishing it as is. Can you also update the related part in the > > release guide☺? > > Am 22.04.2016 11:18 schrieb "Oliver B. Fischer" < > [email protected]>: > > > >> John, > >> > >> the site is not perfect at the moment. There are some minor issues in > the > >> layout and the handling of the latest release version and the current > >> development version. For the cleanest solution we have to decide which > part > >> of the documentation is only part of the website and which documents > >> belongs to the released version of Tamaya. This needs some work to be > done. > >> And might be solved only with the release of 0.3-incubating. > >> > >> Therefore I would like to publish the current version. If we have a > >> working deployment chain it is easy to improve the homepage step by > step. > >> > >> WDYT? > >> > >> Oliver > >> > >> Am 20.04.16 um 20:04 schrieb John D. Ament: > >> > >> -- > >> N Oliver B. Fischer > >> A Schönhauser Allee 64, 10437 Berlin, Deutschland/Germany > >> P +49 30 44793251 > >> M +49 178 7903538 > >> E [email protected] > >> S oliver.b.fischer > >> J [email protected] > >> X http://xing.to/obf > >> > >> > > -- > N Oliver B. Fischer > A Schönhauser Allee 64, 10437 Berlin, Deutschland/Germany > P +49 30 44793251 > M +49 178 7903538 > E [email protected] > S oliver.b.fischer > J [email protected] > X http://xing.to/obf > >
