You are viewing a plain text version of this content. The canonical link for it is here.
Posted to infrastructure-issues@apache.org by "Hervé Boutemy (JIRA)" <ji...@apache.org> on 2015/10/29 23:43:27 UTC

[jira] [Created] (INFRA-10688) unionfs for maven site merging between site and components documentation

Hervé Boutemy created INFRA-10688:
-------------------------------------

             Summary: unionfs for maven site merging between site and components documentation
                 Key: INFRA-10688
                 URL: https://issues.apache.org/jira/browse/INFRA-10688
             Project: Infrastructure
          Issue Type: Wish
          Components: CMS, SvnPubSub, Website
         Environment: http://maven.apache.org/
            Reporter: Hervé Boutemy


Maven site is composed of a main site + components documentation: http://maven.apache.org/developers/website/website-overview.html

Currently it is done with 2 svnpubsub entries + .htaccess:
- / is https://svn.apache.org/repos/infra/websites/production/maven/content/
- /components is https://svn.apache.org/repos/infra/websites/production/maven/components/
- end of .htaccess rewrite rules https://svn.apache.org/repos/infra/websites/production/maven/content/.htaccess rewrites to /components if file not found in /

It works not so bad but there are 2 shortcomings:
- wrong redirect for directories not ending with /: see http://maven.apache.org/ref
- download.cgi script (for mirrors) does not work: try "download" link from http://maven.apache.org/ant-tasks/index.html


After looking for solutions for these shortcomings, I found that in fact, what we are trying to do with .htaccess rewrite rules would in fact be perfectly done with something like an unionfs (or any equivalent tool) that merges /components into /
This would solve both shortcomings and be less cryptic than the .htaccess rewrite rules

could such unionfs be configured for http://maven.apache.org/ , please?



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)