maven-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Lukas Theussl (JIRA)" <j...@codehaus.org>
Subject [jira] Closed: (MSITE-377) empty page for xdoc generated
Date Tue, 12 May 2009 07:51:44 GMT

     [ http://jira.codehaus.org/browse/MSITE-377?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Lukas Theussl closed MSITE-377.
-------------------------------

      Assignee: Lukas Theussl
    Resolution: Not A Bug

> empty page for xdoc generated
> -----------------------------
>
>                 Key: MSITE-377
>                 URL: http://jira.codehaus.org/browse/MSITE-377
>             Project: Maven 2.x Site Plugin
>          Issue Type: Bug
>    Affects Versions: 2.0-beta-7, 2.1
>            Reporter: Jörg Hohwiller
>            Assignee: Lukas Theussl
>
> In my project I have two xdoc files that both use the toc-macro invented with DOXIA-40.
> When I generate the site of my project with "mvn site", I get an entirely empty page
for one of these xdoc files (setup-devel.xml),
> while when I do "mvn site:stage" the same happens about the other xdoc file (conventions.xml).

> This appears to me like a very odd bug.
> If it may help, you can use my project to reproduce this:
> http://m-m-m.svn.sourceforge.net/svnroot/m-m-m/trunk/
> If you run "mvn -N site" (you might only checkout src and pom.xml from trunk) 
> you get the described problem with empty setup-devel.html.
> Staging the site might be a little fiddly though...
> My history about this:
> For my project I am struggeling with maven-site-plugin since years.
> After 2.0-beta-5 was released I was quite happy since I was able to stage the entire
site of my complex multi-module-project.
> However later versions invented new features like an autogenerated table-of-contents
(DOXIA-40) that I started to use.
> Then I figured out that beta-6 and beta-7 were very buggy about creating links to sub-modules
(MSITE-275).
> Now all my hope is up to beta-8 that I am awaiting, where these bugs are fixed. But I
end up with this new problem.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira

       

Mime
View raw message