[
https://issues.apache.org/jira/browse/JCRVLT-741?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17806518#comment-17806518
]
Konrad Windszus commented on JCRVLT-741:
----------------------------------------
A potential workaround is switching to the following layout:
{code}
+ filevault-package-maven-plugin
+ /LATEST (being a link to the latest <version> sibling directory)
+ /<version>
{code}
In addition redirects would need to be maintained for the old URLs (in the main
Git repository https://github.com/apache/jackrabbit-site).
That way only the sub directory {{filevault-package-maven-plugin}} of the
website would be fed from the Maven plugin's Git repository.
> 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)
