[
https://jira.codehaus.org/browse/JXR-108?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=355049#comment-355049
]
Michael Osipov edited comment on JXR-108 at 10/27/14 2:56 PM:
--------------------------------------------------------------
Karl-Heinz,
I do not understand the connection between the ban and the JXR bug here. I have
updated the example and replaced the parent POM with my personal from Maven
Central. It does not enforce a bytecode version. You can still observe the same
behavior.
was (Author: michael-o):
Karl Heinz,
I do not understand the connection between the ban and the JXR bug here. I have
updated the example and replaced the parent POM with my personal from Maven
Central. It does not enforce a bytecode version. You can still observe the same
behavior.
> 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)
