[jira] [Commented] (MSHARED-480) Use maven-site-plugin's site.xml to use site's skin instead of default when run as mojo

[ https://issues.apache.org/jira/browse/MSHARED-480?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17644629#comment-17644629 ] Herve Boutemy commented on MSHARED-480: --- another aspect that this now makes clear, and I was

[jira] [Commented] (MSHARED-480) Use maven-site-plugin's site.xml to use site's skin instead of default when run as mojo

[ https://issues.apache.org/jira/browse/MSHARED-480?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17644626#comment-17644626 ] Herve Boutemy commented on MSHARED-480: --- wow, i love the idea of disabling the menus: it now

[jira] [Commented] (MSHARED-480) Use maven-site-plugin's site.xml to use site's skin instead of default when run as mojo

[ https://issues.apache.org/jira/browse/MSHARED-480?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17643784#comment-17643784 ] Michael Osipov commented on MSHARED-480: Let me know what you think. > Use maven-site-plugin's

[jira] [Commented] (MSHARED-480) Use maven-site-plugin's site.xml to use site's skin instead of default when run as mojo

[ https://issues.apache.org/jira/browse/MSHARED-480?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17643783#comment-17643783 ] Michael Osipov commented on MSHARED-480: Here is a comparison from my project: With Maven Site

[jira] [Commented] (MSHARED-480) Use maven-site-plugin's site.xml to use site's skin instead of default when run as mojo

[ https://issues.apache.org/jira/browse/MSHARED-480?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17643765#comment-17643765 ] Michael Osipov commented on MSHARED-480: Here is a solution the issue: 1. Build from

[jira] [Commented] (MSHARED-480) use maven-site-plugin's site.xml to use site's skin instead of default when run as mojo

[ https://issues.apache.org/jira/browse/MSHARED-480?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17561713#comment-17561713 ] Herve Boutemy commented on MSHARED-480: --- yes, let's stop trying to make a standalone report mojo

[jira] [Commented] (MSHARED-480) use maven-site-plugin's site.xml to use site's skin instead of default when run as mojo

[ https://issues.apache.org/jira/browse/MSHARED-480?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17561548#comment-17561548 ] Michael Osipov commented on MSHARED-480: [~hboutemy], I think we have agreed and will burry this

[jira] [Commented] (MSHARED-480) use maven-site-plugin's site.xml to use site's skin instead of default when run as mojo

[ https://issues.apache.org/jira/browse/MSHARED-480?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15083168#comment-15083168 ] Michael Osipov commented on MSHARED-480: Let me rephase the statement you did not understand: A

[jira] [Commented] (MSHARED-480) use maven-site-plugin's site.xml to use site's skin instead of default when run as mojo

[ https://issues.apache.org/jira/browse/MSHARED-480?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15083529#comment-15083529 ] Hervé Boutemy commented on MSHARED-480: --- bq. For the Default Skin, it isn't the case wrong, images

[jira] [Commented] (MSHARED-480) use maven-site-plugin's site.xml to use site's skin instead of default when run as mojo

[ https://issues.apache.org/jira/browse/MSHARED-480?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15082042#comment-15082042 ] Michael Osipov commented on MSHARED-480: I had the very same idea recently. I am not very pleased

[jira] [Commented] (MSHARED-480) use maven-site-plugin's site.xml to use site's skin instead of default when run as mojo

[ https://issues.apache.org/jira/browse/MSHARED-480?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15082137#comment-15082137 ] Hervé Boutemy commented on MSHARED-480: --- bq. I do believe that skin-related must be in the default