[ https://issues.apache.org/jira/browse/JCRVLT-741?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17806513#comment-17806513 ]
Konrad Windszus commented on JCRVLT-741: ---------------------------------------- The issue is that we feed two sibling subdirectories of jackrabbit.apache.org for the Maven plugin: # https://jackrabbit.apache.org/filevault-package-maven-plugin-archives/ # https://jackrabbit.apache.org/filevault-package-maven-plugin/ This is currently not supported by subdirectory publishing. I raised https://issues.apache.org/jira/browse/INFRA-25379 for supporting this use case. > Maven-Plugin: Publish site directly from Git repo > ------------------------------------------------- > > Key: JCRVLT-741 > URL: https://issues.apache.org/jira/browse/JCRVLT-741 > 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)