[
http://jira.codehaus.org/browse/MSITE-177?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=189224#action_189224
]
Jörg Hohwiller commented on MSITE-177:
--------------------------------------
Hi Lukas,
I do NOT agree with what you are saying: You could check if mtime of site.xml
is later than creation date of the according *.html-file so last generation was
before change of site.xml.
BTW: What is the use in not regenerating the *.html files in such case? Saving
performance? If there are problems about performance then its that tests are
executed multiple
times, etc.
> Docs are not updated if only site.xml changed
> ---------------------------------------------
>
> Key: MSITE-177
> URL: http://jira.codehaus.org/browse/MSITE-177
> Project: Maven 2.x Site Plugin
> Issue Type: Bug
> Components: site descriptor
> Affects Versions: 2.0-beta-5
> Reporter: Jörg Hohwiller
> Assignee: Lukas Theussl
>
> If I update site.xml (e.g. add new menu-items) and regenerate my existing
> site, the index gets updated but other existing pages are not rebuild and
> therefore show the menus in the state before the site.xml has changed (so new
> menus are missing). This causes a confusing site where menus appear and
> disappear while surfing.
> I only use xdos (and they are in a subfolder) so I can not tell if this
> happens with apt as well. I reproduced the problem with "mvn site" and "mvn
> site:stage".
> As a workaround I can delete the old site before building. Since I stage the
> site directly to the final destination on the local machine where it is
> served this is not very suitable because then the site is broken until it is
> completely rebuild.
> If you consider to fix this issue please beware that site.xml can inherit
> stuff in multiproject envronments.
> So it is unclear if the optimization to only re-generate if something has
> changed makes sense at all. It might be quite complicated to determine this -
> the question is how much time is saved by this at all.
--
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
