[
https://issues.apache.org/jira/browse/DOXIASITETOOLS-278?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17681726#comment-17681726
]
Michael Osipov commented on DOXIASITETOOLS-278:
-----------------------------------------------
Now, looking at our parent POMs we have this:
{noformat}
<!-- publish mono-module site with "mvn site-deploy" -->
<plugin>
<groupId>org.apache.maven.plugins</groupId>
<artifactId>maven-site-plugin</artifactId>
<configuration>
<skipDeploy>true</skipDeploy><!-- don't deploy site with
maven-site-plugin -->
</configuration>
</plugin>
</plugins>
{noformat}
This means that if I add the deployment property as well a valid use case will
be killed. Looking at the source code of Maven Site Plugin {{maven.site.skip}}
applies both to generation **and** staging. We cannot make any assumption if
{{maven.site.deploy.skip}} is set to {{true}} that deployment still might
happen by other means since a simply {{rsync ...}} is good enough as well.
Therefore, I will only consider the single property {{maven.site.skip}}.
> Remove menu items link in the sidebar to sub module that do not generate any
> site in the same build
> ---------------------------------------------------------------------------------------------------
>
> Key: DOXIASITETOOLS-278
> URL: https://issues.apache.org/jira/browse/DOXIASITETOOLS-278
> Project: Maven Doxia Sitetools
> Issue Type: Improvement
> Components: Integration Tools
> Affects Versions: 2.0.0-M4
> Environment: Windows7, Maven 3.3.9
> Reporter: Nikolas Falco
> Assignee: Michael Osipov
> Priority: Major
> Fix For: 2.0.0-M5
>
>
> We have some multi-module projects where a few modules are only for scope
> distribution or for integration test.
> These modules are marked with maven.site.skip=true and the site is not
> generated, but in the maven site of parent project they appear in the sidebar
> menu, clearly if you click on those links are broken.
> Debugging the code, the mojo loop on each project in the reactor build and
> add as menu item.
> Is possible add a configuration element of maven-site-plugin to exclude some
> modules from the modules report menu? or implement a check if a site for that
> project exists?
> org.example
> |- module1
> |- module2
> |- module.test (skip generation)
> |- distribution (skip generation)
> the maven site of org.example have in the menu bar links to no available site
> of distribution and module.test
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
