Hi David & Cameleers, after much arguing with Gulp I created a pull request for the next step in this: to use symbolic links instead of file copies for the documentation. The pull request is up for review and I very much welcome feedback, for example I did not test this other than on a Unix (Linux) machine, so there _might_ be some issues on Windows.
https://github.com/apache/camel/pull/6072 I'm also very interested in usability feedback, I do realize that for non-JavaScript/Gulp/Asciidoc experts this might be a difficult process to understand. I did try to put in as much information in comments to help with understanding. So if there is anything that is not clear I'd like to improve on that. Next step would be to enable creation of symbolic links for Camel JSON metadata files and apply changes from David's[1] PR that use the jsonpath macro to generate tables of options instead of the Maven UpdateReadme mojo. Again, big thanks to David that started this work, this is merely a refinement of his ideas taken piece by piece to prevent a big bang rollout... zoran [1] https://github.com/apache/camel/pull/6040 -- Zoran Regvart
