You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@jackrabbit.apache.org by "Konrad Windszus (Jira)" <ji...@apache.org> on 2024/01/14 14:31:00 UTC

[jira] [Moved] (JCRVLT-740) Publish site directly from Git repo

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

Konrad Windszus moved OAK-10602 to JCRVLT-740:
----------------------------------------------

    Component/s:     (was: docs)
            Key: JCRVLT-740  (was: OAK-10602)
       Workflow: no-reopen-closed, patch-avail  (was: no-reopen-closed)
        Project: Jackrabbit FileVault  (was: Jackrabbit Oak)

> Publish site directly from Git repo
> -----------------------------------
>
>                 Key: JCRVLT-740
>                 URL: https://issues.apache.org/jira/browse/JCRVLT-740
>             Project: Jackrabbit FileVault
>          Issue Type: Improvement
>            Reporter: Konrad Windszus
>            Assignee: Konrad Windszus
>            Priority: Major
>
> As outlined in https://cwiki.apache.org/confluence/pages/viewpage.action?spaceKey=INFRA&title=git+-+.asf.yaml+features#Git.asf.yamlfeatures-Specifyingasub-directorytopublishto the website should be directly published from the Git repository instead of pushing to SVN first. This requires
> - adjusting the [maven-scm-publish-plugin|https://maven.apache.org/plugins/maven-scm-publish-plugin/] to publish to a branch of the source repository
> - adjusting the .asf.yaml



--
This message was sent by Atlassian Jira
(v8.20.10#820010)