[
http://jira.codehaus.org/browse/MSITE-539?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=262778#action_262778
]
Stevo Slavic edited comment on MSITE-539 at 4/7/11 4:28 AM:
------------------------------------------------------------
Yes, I found example there misleading, version element for every reporting
plugin listed under reportPlugins was not respected - if I remember well, if
reporting plugins were only defined in reportingPlugins Maven 3 would report
that it's not good practice that reporting plugin version is not specified,
even though version was specified as in example. Only by specifying reporting
plugins in pluginManagement I was able to configure required version, and have
Maven not complain about bad practice. After specifying version of reporting
plugins in pluginManagement section, I could, and now typically do remove
version of plugins in reportPlugins section.
was (Author: sslavic):
Yes, I found example there misleading, version element for every reporting
plugin listed under reportPlugins was not respected - if I remember well, if
reporting plugins were only defined in reportingPlugins Maven 3 would report
that it's not good practice that reporting plugin version is not specified.
Only by specifying reporting plugins in pluginManagement I was able to
configure required version, and have Maven not complain about bad practice.
After specifying version of reporting plugins in pluginManagement section, I
could, and now typically do remove version of plugins in reportPlugins section.
> Reporting plugin version references in new configuration example are wrong
> and misleading
> -----------------------------------------------------------------------------------------
>
> Key: MSITE-539
> URL: http://jira.codehaus.org/browse/MSITE-539
> Project: Maven 2.x and 3.x Site Plugin
> Issue Type: Bug
> Components: Maven 3
> Affects Versions: 3.0-beta-3
> Reporter: Stevo Slavic
> Priority: Minor
>
> [New configuration
> example|http://maven.apache.org/plugins/maven-site-plugin-3.0-beta-3/maven-3.html#New_Configuration]
> shows invalid reference to maven-javadoc-plugin version - version info there
> won't break a build but it is simply not used by Maven 3 or site plugin
> (maven reports that version info is not available for such reporting plugin).
> Such wrong example might mislead users that this is expected way of
> specifying version of reporting plugin used within maven site plugin
> configuration. Example following new configuration example, related to
> version resolution, is valid, it specifies reporting plugin version info in
> pluginManagement section.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
