After fiddling around a bit I managed to get the SVN history included as well (had to run it multiple times because of a temporary javadoc location at /content/documentation/temp).
All content is included except 'content/documentation/javadoc' and 'content/documentation/temp'. I have renamed the 'release-docs' branch to be called 'javadoc' which indeed makes more sense. Feel free to browse around here [1]. Whenever agreed with jena-site can be requested [2] and the 'master', 'asf-site' and 'javadoc' branches can be pushed. After that I'll create a Jenkins build job and make sure jena.a.o will be moved from the CMS to the git repository. [1] https://github.com/rlenferink/jena-site [2] https://gitbox.apache.org/setup/newrepo.html On 2020/02/26 11:10:56, Andy Seaborne <a...@apache.org> wrote: > That would not carry over the history although the history would include > all the javadoc over time. Importing svn would keep the history > > I don't know if a partial import can be done, without > content/documentation/javadoc/ > > "git svn --ignore-paths=" looks hopeful (I've never run "git svn" before). > > History for the website would be good but personally I don't see it as a > blocker. > > Andy >
