[
https://issues.apache.org/jira/browse/DOXIASITETOOLS-328?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17810996#comment-17810996
]
Konrad Windszus commented on DOXIASITETOOLS-328:
------------------------------------------------
As I said above in the description you can take
https://jackrabbit.apache.org/filevault-package-maven-plugin-archives/1.3.4/dev.html.
as an example (which leverages the pom.xml from
https://github.com/apache/jackrabbit-filevault-package-maven-plugin/blob/6d42fd2ff066ed7543bfb704c83f1b553b0e196d/pom.xml#L261-L299).
> Allow to overwrite the edit source link with an alternative folder
> ------------------------------------------------------------------
>
> Key: DOXIASITETOOLS-328
> URL: https://issues.apache.org/jira/browse/DOXIASITETOOLS-328
> Project: Maven Doxia Sitetools
> Issue Type: Improvement
> Reporter: Konrad Windszus
> Priority: Major
>
> Sometimes regular Maven filtering is used to preprocess the doxia source
> files (for placeholder replacement only) when Velocity is just too much
> overhead/requires workarounds e.g. for level 2 headlines with markdown
> (https://maven.apache.org/plugins/maven-site-plugin/examples/creating-content.html#Filtering),
> compare with DOXIA-677.
> In that case the generated edit button links to the wrong (temporary)
> location which was used as the input directory for the site (but is actually
> below {{target/....}}) and therefore not available in the SCM. For example
> look at the edit button in
> https://jackrabbit.apache.org/filevault-package-maven-plugin-archives/1.3.4/dev.html.
> There should be the possibility to give an alternative source directory for
> generating the edit link (instead of the one given through
> https://maven.apache.org/plugins/maven-site-plugin/site-mojo.html#siteDirectory)
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
