You are viewing a plain text version of this content. The canonical link for it is here.
Posted to oak-issues@jackrabbit.apache.org by "Konrad Windszus (Jira)" <ji...@apache.org> on 2024/01/24 12:14:00 UTC
[jira] [Resolved] (OAK-10601) Publish site directly from Git repo
[ https://issues.apache.org/jira/browse/OAK-10601?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Konrad Windszus resolved OAK-10601.
-----------------------------------
Resolution: Won't Fix
This doesn't make sense: https://issues.apache.org/jira/browse/JCRSITE-55?focusedCommentId=17810346&page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-17810346
> Publish site directly from Git repo
> -----------------------------------
>
> Key: OAK-10601
> URL: https://issues.apache.org/jira/browse/OAK-10601
> Project: Jackrabbit Oak
> Issue Type: Improvement
> Components: docs
> 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)