maven-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Myron (JIRA)" <j...@codehaus.org>
Subject [jira] (MPIR-256) "About" report generated even though index.apt is available in "generated-site"
Date Thu, 18 Oct 2012 07:30:37 GMT

    [ https://jira.codehaus.org/browse/MPIR-256?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=311756#comment-311756
] 

Myron commented on MPIR-256:
----------------------------

I second that request (came across the same issues days ago)

Maybe we could express this more globally:
First the target/generated-site/* should be rendered, then then the src/site/*, and if there's
still no index, then generate this aswell.

eg: if i have a generated-site/apt/test.apt AND a site/apt/test.apt, the src variant is always
rendered first, making the generated one useless.
IMHO, the generated ones should always have precedence... (for all files, not only for index)
WDYT?
                
> "About" report generated even though index.apt is available in "generated-site"
> -------------------------------------------------------------------------------
>
>                 Key: MPIR-256
>                 URL: https://jira.codehaus.org/browse/MPIR-256
>             Project: Maven 2.x Project Info Reports Plugin
>          Issue Type: Bug
>          Components: index
>    Affects Versions: 2.5.1
>            Reporter: Andrius Velykis
>         Attachments: mvn-site-index.zip
>
>
> Normally, if there is an apt/index.apt file in the /src/site directory, About report
is not generated, and the following message is displayed: Skipped "About" report, file "index.html"
already exists for the English version.
> Expecting the same behaviour, I have a situation, where the index.apt file is generated
automatically (e.g. copied from somewhere) during `pre-site` phase. maven-site-plugin allows
specifying an additional `generatedSiteDirectory` parameter for these files (see http://maven.apache.org/plugins/maven-site-plugin/site-mojo.html).
> However, in this case, the "About" report is generated and overrides the copied file
from `generatedSiteDirectory` parameter.
> I would expect the "About" report to be not generated, if index.apt is available in the
`generatedSiteDirectory`.
> I have attached a sample project, which uses `antrun` to copy a file to /target/generated-site/apt/index.apt.
When you run `mvn site`, it will still display the default "About" page. As an example that
`generatedSiteDirectory` works, I also copy the same file to index-copy.apt and an index-copy.html
is generated correctly.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://jira.codehaus.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

Mime
View raw message