[
https://jira.codehaus.org/browse/JXR-108?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=355054#comment-355054
]
Karl-Heinz Marbaise commented on JXR-108:
-----------------------------------------
The ban was a result of the wrong parent you used. After checking your example
update. I had to find out that the used parent contains a snapshot of
maven-fluido-skin 1.3.1-SNAPSHOT (version:6). After upgrade to version 7 i got
it to work. After diving into this problem i found out this is not bug is
intended behaviour.
[Excerpt from the
documentation:|http://maven.apache.org/plugins/maven-site-plugin/examples/configuring-reports.html]
last line on the page:
bq. Notice: don't forget to define reportSets for plugins which provide
aggregator reports, like maven-javadoc-plugin, maven-jxr-plugin or
maven-checkstyle-plugin or you'll have these aggregate reports run by default
in addition to non-aggregate reports.
> 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)
