You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Jörg Hohwiller (JIRA)" <ji...@codehaus.org> on 2006/08/22 09:29:50 UTC
[jira] Created: (MSITE-177) Docs are not updated if only site.xml
changed
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
Affects Versions: 2.0-beta-5
Reporter: Jörg Hohwiller
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
[jira] Commented: (MSITE-177) Docs are not updated if only site.xml
changed
Posted by "John Allen (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MSITE-177?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_102985 ]
John Allen commented on MSITE-177:
----------------------------------
Same here, the logic is obviously broken in regards to what requires a rebuild. if site.xml has changed then everything bar external reports needs to be recreated.
> 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
> Affects Versions: 2.0-beta-5
> Reporter: Jörg Hohwiller
> Fix For: 2.0-beta-7
>
>
> 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
[jira] Commented: (MSITE-177) Docs are not updated if only site.xml
changed
Posted by "Lukas Theussl (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MSITE-177?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=189228#action_189228 ]
Lukas Theussl commented on MSITE-177:
-------------------------------------
bq. check if mtime of site.xml is later than creation date of the according *.html-file
which according .html file?
> 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
[jira] Updated: (MSITE-177) Docs are not updated if only site.xml
changed
Posted by "Dennis Lundberg (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MSITE-177?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Dennis Lundberg updated MSITE-177:
----------------------------------
Component/s: site descriptor
> 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
> Fix For: 2.0-beta-7
>
>
> 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
[jira] Closed: (MSITE-177) Docs are not updated if only site.xml
changed
Posted by "Lukas Theussl (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MSITE-177?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Lukas Theussl closed MSITE-177.
-------------------------------
Assignee: Lukas Theussl
Resolution: Won't Fix
The site.xml is not copied to the site, so there is no way to find out if it has changed since the last build. The same applies to any relevant sections in the pom, properties or resource files, etc, that might affect the site. I have [documented|http://svn.apache.org/viewvc?view=rev&revision=799533] this.
> 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
[jira] Commented: (MSITE-177) Docs are not updated if only site.xml
changed
Posted by "Jörg Hohwiller (JIRA)" <ji...@codehaus.org>.
[ 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
[jira] Updated: (MSITE-177) Docs are not updated if only site.xml
changed
Posted by "Brett Porter (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MSITE-177?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Brett Porter updated MSITE-177:
-------------------------------
Fix Version/s: 2.0-beta-7
> 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
> Affects Versions: 2.0-beta-5
> Reporter: Jörg Hohwiller
> Fix For: 2.0-beta-7
>
>
> 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
[jira] Commented: (MSITE-177) Docs are not updated if only site.xml
changed
Posted by "Martin Ahrer (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MSITE-177?page=comments#action_79708 ]
Martin Ahrer commented on MSITE-177:
------------------------------------
I'm experienceing the same problem with apt files.. I usually do mvn clean site ... whenever I change a site.xml
> 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
> Affects Versions: 2.0-beta-5
> Reporter: Jörg Hohwiller
>
> 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
[jira] Updated: (MSITE-177) Docs are not updated if only site.xml
changed
Posted by "Dennis Lundberg (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MSITE-177?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Dennis Lundberg updated MSITE-177:
----------------------------------
Fix Version/s: (was: 2.0-beta-7)
2.0-beta-8
> 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
> Fix For: 2.0-beta-8
>
>
> 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