You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@calcite.apache.org by "Julian Hyde (JIRA)" <ji...@apache.org> on 2015/09/13 07:14:45 UTC

[jira] [Resolved] (CALCITE-882) Update site to adhere to a `baseurl` property

     [ https://issues.apache.org/jira/browse/CALCITE-882?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Julian Hyde resolved CALCITE-882.
---------------------------------
       Resolution: Fixed
    Fix Version/s:     (was: next)
                   1.5.0-incubating

Fixed in http://git-wip-us.apache.org/repos/asf/incubator-calcite/commit/ad4bdca3 and deployed to http://calcite.incubator.apache.org/. Thanks for the patch, [~elserj]!

> Update site to adhere to a `baseurl` property
> ---------------------------------------------
>
>                 Key: CALCITE-882
>                 URL: https://issues.apache.org/jira/browse/CALCITE-882
>             Project: Calcite
>          Issue Type: Improvement
>          Components: site
>            Reporter: Josh Elser
>            Assignee: Josh Elser
>            Priority: Trivial
>             Fix For: 1.5.0-incubating
>
>
> Noticed while working CALCITE-866, the trick to deploy a Jekyll site to a subdirectory (instead of the root of some vhost) doesn't work because Calcite has hard-coded anchors at "/".
> We can work around this by using 
> {noformat}
> {{site.baseurl}}
> {noformat}
> There's a description on how to do this at https://jekyllrb.com/docs/github-pages/#project-page-url-structure. Would be convenient to be able to deploy at any location, not just the root of some vhost.



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