Hi, > Proposal: Create a directory /content which contains the web site contents. > Change the asf.yaml file to publish /content to the web whenever master is > updated. Add a deploy step to the pom.xml to copy target/site to /content.
I started looking into this. - I propose to leave the docs directory and create a symbolic link content -> docs. - I propose to add updating the content directory to the maven lifecycle phase 'install' instead of 'deploy'. Currently we do not store any artifacts in a remote repository, so calling 'maven deploy' does not make sense. > The down side to this proposal is that making a quick change to the site > using only the online version of git cannot publish the site. > > AI Michael check in the changes to site. Other changes include e.g. svn.adoc > and pmf.adoc. I just created a pull request using branch remove-svn. I would help me with the above changes, if someone would review the accept the pull request, accept it and merge it into master. Regards Michael -- Michael Bouschen akquinet tech@spree GmbH Bülowstraße 66 • D-10783 Berlin Tel: +49 30 235520-33 Fax: +49 30 217520-12 E-Mail: michael.bousc...@akquinet.de <mailto:michael.bousc...@akquinet.de> Web: www.akquinet.de <http://www.akquinet.de/> Geschäftsführung: Martin Weber, Dr. Torsten Fink, Heinz Wilming Amtsgericht Berlin HRB 86780 • USt.-Id. Nr.: DE 225 964 680 [Facebook] <http://www.facebook.com/akquinet> [XING] <https://www.xing.com/companies/akquinetag> [LinkedIn] <https://www.linkedin.com/company/akquinet-ag> [Twitter] <https://twitter.com/akquinet>
