[
https://jira.codehaus.org/browse/JXR-108?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=355055#comment-355055
]
Michael Osipov commented on JXR-108:
------------------------------------
That is the last place where I would check for that behavior. That totally
kills the {{aggregate}} property. Can't we put that to a better place? I guess,
I am not the only one who stepped in that pitfall.
> Reports aggregated when no explicit reports are set
> ---------------------------------------------------
>
> Key: JXR-108
> URL: https://jira.codehaus.org/browse/JXR-108
> Project: Maven JXR
> Issue Type: Bug
> Components: maven2 jxr plugin
> Affects Versions: 2.4
> Environment: Maven 3.1
> Reporter: Michael Osipov
> Fix For: next-release
>
> Attachments: jxr108-parent.zip, jxr108-parent.zip
>
>
> I have declared the plugin in my parent POM reporting plugins section. The
> generated site includes aggregated cross references from my modules though
> this was never set and the aggregate flag is set to {{false}} by default. If
> one declares {{reportSets}} explicitly, the problem goes away.
--
This message was sent by Atlassian JIRA
(v6.1.6#6162)
