infra-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Svante Schubert (JIRA)" <>
Subject [jira] [Commented] (INFRA-15596) Make ODF TOOLKIT SVN repo read-only and activate two Git repos on GitHub for writing
Date Sun, 28 Jan 2018 16:42:00 GMT


Svante Schubert commented on INFRA-15596:

I would like to get further advise on regard of the site process transition.
I am stuck in finding a solution of the SVN+CMS combo, see very below the two points beyond

1) With moving the site repro from SVN to GIT, I heard the project is not able to use the
CMS any longer. The CMS & SVN combination was standard construct for Apache site creation.

2) We also need to deployment our JavaDoc. Currently we are using the SVN site repro as well
for deployment of our JavaDoc via the CMS: 
	see incubator-odftoolkit-site/content/odftoolkit/0.6.2-incubating/odfdom
	see ncubator-odftoolkit-site/content/odftoolkit/mvn-site

1) We would like transform the maintenance of our site to some existing process, without the
need to adopt too much (the site is nor our main focus of development) 
2) We would like to be close to the infrastructure process that most projects are using (being
mainstream to adopt as many tools as possible)
3) We would like to allow automation, like Jenkens

Maven the site process allows the creation of HTML vom Markdown, Maven is used by our main
projects and is supported by Jenkins I started some prototype.
Here are my working steps:
a) I have started the maven-site branch to add my testing:
b) I have adopted the directory structure according to Maven standards, by copying 
keeping the original files for later
c) I have copied the pom.xml from our ODFDOM project and stripped it to execute "mvn site"
from command line
d) Moved CSS and Image resources to src/site/resources
e) Exchanged all <br> to <br/> in ppmc-faqs.mdtext (otherwise build error)
f) renamed odf.css to site.css (also possible references in markdown files)
g) I removed for now the JavaDoc sites from the src package. Question remains where to deploy
the former site with JavaDoc (see requirment above)
h) Exchanged markup file suffix from .mdtext to .md to make them visible to Maven

The generated site still look terrible, as obviously the templates are not being used.
I) We need to map the existing templates from /templates to the site.xml file.
II) In addition, I am uncertain if and how the former Perl files from the /library folders
can be mapped

I have to switch to other tasks, uncertain how much time I am able to spend this week, so
my question is does this approach to switch to Maven makes sense or will it fail due to the
templates and perl scripts? Can someone help here?
How did other before did the SVN&CMS to git transformation? 
Is there no recipe, painting by numbers description?

Thanks in advance..

> Make ODF TOOLKIT SVN repo read-only and activate two Git repos on GitHub for writing
> ------------------------------------------------------------------------------------
>                 Key: INFRA-15596
>                 URL:
>             Project: Infrastructure
>          Issue Type: SVN->GIT Migration
>          Components: Github
>            Reporter: Svante Schubert
>            Assignee: Chris Lambertus
>            Priority: Major
>         Attachments: apache-git-site-repository-request.png

This message was sent by Atlassian JIRA

View raw message