[ https://issues.apache.org/jira/browse/MSITE-802?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16254725#comment-16254725 ]
Allen Wittenauer commented on MSITE-802: ---------------------------------------- Here's a slightly modified example that uses Apache Yetus. This might be too complex for an example though. {code} <plugin> <groupId>org.codehaus.mojo</groupId> <artifactId>exec-maven-plugin</artifactId> <executions> <execution> <id>shelldocs</id> <phase>pre-site</phase> <goals> <goal>exec</goal> </goals> <configuration> <executable>shelldocs</executable> <workingDirectory>${project.build.directory}/generated-site/site/markdown</workingDirectory> <arguments> <argument>--skipprnorep</argument> <argument>--output</argument> <argument>${project.build.directory}/generated-site/markdown/UnixShellAPI.md</argument> <argument>--input</argument> <argument>${basedir}/src/main/bin/hadoop-functions.sh</argument> </arguments> </configuration> </execution> </executions> </plugin> {code} This example runs Apache Yetus' shelldocs command on the hadoop-functions.sh script to generate markdown-formatted documentation. > Support more than one directory > ------------------------------- > > Key: MSITE-802 > URL: https://issues.apache.org/jira/browse/MSITE-802 > Project: Maven Site Plugin > Issue Type: Task > Reporter: Allen Wittenauer > Assignee: Hervé Boutemy > Priority: Minor > Fix For: 3.7 > > > It would be great if maven-site-plugin could support more than one site > directory per module. Specifically, I'm looking for a way to process > generated content without copying all of src/site into target where my > generated content is sitting or using a separate module that only handles > generated content to get aggregated later. -- This message was sent by Atlassian JIRA (v6.4.14#64029)