You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Stevo Slavic (JIRA)" <ji...@codehaus.org> on 2011/01/07 00:46:57 UTC
[jira] Created: (MSITE-539) Reporting plugin version references in
new configuration example are wrong and misleading
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
[jira] Commented: (MSITE-539) Reporting plugin version references
in new configuration example are wrong and misleading
Posted by "Lukas Theussl (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MSITE-539?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=268324#action_268324 ]
Lukas Theussl commented on MSITE-539:
-------------------------------------
Is this still related to the original topic of a wrong documentation example? If not, please create a new issue, and if yes, please also create a new issue :)
> 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
> Assignee: Lukas Theussl
> Priority: Minor
> Attachments: MSITE-539.zip
>
>
> [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
[jira] Commented: (MSITE-539) Reporting plugin version references
in new configuration example are wrong and misleading
Posted by "Stevo Slavic (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MSITE-539?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=268320#action_268320 ]
Stevo Slavic commented on MSITE-539:
------------------------------------
I managed to reproduce this one. When releasing corporate Maven parent project, release:perform goal checkouts tag created with release:prepare, runs a build with specified goals (-Dgoals=deploy) and for that inner build Maven prints out warnings that version is not set for maven-javadoc-plugin plugin although it is set, maven-site-plugin has reportPlugins and within it, along with other reporting plugins is maven-javadoc-plugin with version 2.8 set.
Environment:
- Maven 3.0.3,
- Java 1.6 update 24 x64,
- Windows 7 x64,
- maven-release-plugin 2.1
- maven-site-plugin 3.0-beta-3
Build output follows:
{noformat}
D:\foo\foo.bar.maven.parent>mvn release:perform -s settings.xml -Dgoals=deploy
[INFO] Scanning for projects...
[INFO]
[INFO] ------------------------------------------------------------------------
[INFO] Building Foo Maven Parent 14-SNAPSHOT
[INFO] ------------------------------------------------------------------------
[INFO]
[INFO] --- maven-release-plugin:2.1:perform (default-cli) @ foo.bar.maven.parent ---
[INFO] Checking out the project to perform the release ...
[INFO] Executing: cmd.exe /X /C "svn --non-interactive checkout https://svn.foo.bar/foo-repo/parent
/tags/releases/foo.bar.maven.parent-13 D:\foo\foo.bar.maven.parent\target\checkout"
[INFO] Working directory: D:\foo\foo.bar.maven.parent\target
[INFO] Executing goals 'deploy'...
[WARNING] Maven will be executed in interactive mode, but no input stream has been configured for this MavenInvoker inst
ance.
[INFO] [INFO] Scanning for projects...
[INFO] [WARNING]
[INFO] [WARNING] Some problems were encountered while building the effective model for foo.bar.maven:foo.bar.maven.p
arent:pom:13
[INFO] [WARNING] 'build.plugins.plugin.version' for org.apache.maven.plugins:maven-javadoc-plugin is missing.
[INFO] [WARNING]
[INFO] [WARNING] It is highly recommended to fix these problems because they threaten the stability of your build.
[INFO] [WARNING]
[INFO] [WARNING] For this reason, future Maven versions might no longer support building such malformed projects.
[INFO] [WARNING]
[INFO] [INFO]
[INFO] [INFO] ------------------------------------------------------------------------
[INFO] [INFO] Building Foo Maven Parent 13
[INFO] [INFO] ------------------------------------------------------------------------
[INFO] [INFO]
[INFO] [INFO] --- maven-enforcer-plugin:1.0:enforce (enforce-versions) @ foo.bar.maven.parent ---
[INFO] [INFO]
[INFO] [INFO] >>> maven-source-plugin:2.1.2:jar (attach-sources) @ foo.bar.maven.parent >>>
[INFO] [INFO]
[INFO] [INFO] --- maven-enforcer-plugin:1.0:enforce (enforce-versions) @ foo.bar.maven.parent ---
[INFO] [INFO]
[INFO] [INFO] <<< maven-source-plugin:2.1.2:jar (attach-sources) @ foo.bar.maven.parent <<<
[INFO] [INFO]
[INFO] [INFO] --- maven-source-plugin:2.1.2:jar (attach-sources) @ foo.bar.maven.parent ---
[INFO] [INFO]
[INFO] [INFO] --- maven-javadoc-plugin:2.8:jar (attach-javadocs) @ foo.bar.maven.parent ---
[INFO] [INFO] Not executing Javadoc as the project is not a Java classpath-capable package
[INFO] [INFO]
[INFO] [INFO] --- maven-site-plugin:3.0-beta-3:attach-descriptor (attach-descriptor) @ foo.bar.maven.parent ---
[INFO] [INFO]
[INFO] [INFO] --- maven-install-plugin:2.3.1:install (default-install) @ foo.bar.maven.parent ---
[INFO] [INFO] Installing D:\foo\foo.bar.maven.parent\target\checkout\pom.xml to C:\Users\s.slavic\
.m2\repository\foo\bar\maven\foo.bar.maven.parent\13\foo.bar.maven.parent-13.pom
[INFO] [INFO] Installing D:\foo\foo.bar.maven.parent\target\checkout\target\foo.bar.maven.parent
-13-site.xml to C:\Users\s.slavic\.m2\repository\foo\bar\maven\foo.bar.maven.parent\13\foo.bar.maven.parent-13-sit
e.xml
[INFO] [INFO]
[INFO] [INFO] --- maven-deploy-plugin:2.6:deploy (default-deploy) @ foo.bar.maven.parent ---
[INFO] Uploading: https://repo.foo.bar/content/repositories/foo-repo/foo/bar/maven/foo.bar.maven.paren
t/13/foo.bar.maven.parent-13.pom
[INFO] 4 KB
[INFO] 8 KB
[INFO] 12 KB
[INFO] 14 KB
[INFO]
[INFO] Uploaded: https://repo.foo.bar/content/repositories/foo-repo/foo/bar/maven/foo.bar.maven.parent
/13/foo.bar.maven.parent-13.pom (14 KB at 5.0 KB/sec)
[INFO] Downloading: https://repo.foo.bar/content/repositories/foo-repo/foo/bar/maven/foo.bar.maven.par
ent/maven-metadata.xml
[INFO]
[INFO] Uploading: https://repo.foo.bar/content/repositories/foo-repo/foo/bar/maven/foo.bar.maven.paren
t/maven-metadata.xml
[INFO] 311 B
[INFO]
[INFO] Uploaded: https://repo.foo.bar/content/repositories/foo-repo/foo/bar/maven/foo.bar.maven.parent
/maven-metadata.xml (311 B at 1.2 KB/sec)
[INFO] Uploading: https://repo.foo.bar/content/repositories/foo-repo/foo/bar/maven/foo.bar.maven.paren
t/13/foo.bar.maven.parent-13-site.xml
[INFO] 751 B
[INFO]
[INFO] Uploaded: https://repo.foo.bar/content/repositories/foo-repo/foo/bar/maven/foo.bar.maven.parent
/13/foo.bar.maven.parent-13-site.xml (751 B at 2.9 KB/sec)
[INFO] [INFO] ------------------------------------------------------------------------
[INFO] [INFO] BUILD SUCCESS
[INFO] [INFO] ------------------------------------------------------------------------
[INFO] [INFO] Total time: 11.294s
[INFO] [INFO] Finished at: Tue May 24 15:15:29 CEST 2011
[INFO] [INFO] Final Memory: 13M/490M
[INFO] [INFO] ------------------------------------------------------------------------
[INFO] Cleaning up after release...
[INFO] ------------------------------------------------------------------------
[INFO] BUILD SUCCESS
[INFO] ------------------------------------------------------------------------
[INFO] Total time: 17.404s
[INFO] Finished at: Tue May 24 15:15:30 CEST 2011
[INFO] Final Memory: 7M/490M
{noformat}
> 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
> Assignee: Lukas Theussl
> Priority: Minor
> Attachments: MSITE-539.zip
>
>
> [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
[jira] Issue Comment Edited: (MSITE-539) Reporting plugin version
references in new configuration example are wrong and misleading
Posted by "Stevo Slavic (JIRA)" <ji...@codehaus.org>.
[ 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
[jira] Updated: (MSITE-539) Reporting plugin version references in
new configuration example are wrong and misleading
Posted by "Lukas Theussl (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MSITE-539?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Lukas Theussl updated MSITE-539:
--------------------------------
Attachment: MSITE-539.zip
> 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
> Attachments: MSITE-539.zip
>
>
> [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
[jira] Commented: (MSITE-539) Reporting plugin version references
in new configuration example are wrong and misleading
Posted by "Stevo Slavic (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MSITE-539?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=262778#action_262778 ]
Stevo Slavic commented on MSITE-539:
------------------------------------
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
[jira] Commented: (MSITE-539) Reporting plugin version references
in new configuration example are wrong and misleading
Posted by "Olivier Lamy (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MSITE-539?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=262777#action_262777 ]
Olivier Lamy commented on MSITE-539:
------------------------------------
Could you provide a sample which doesn't work and the corresponding mvn output execution
> 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
[jira] Closed: (MSITE-539) Reporting plugin version references in
new configuration example are wrong and misleading
Posted by "Lukas Theussl (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MSITE-539?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Lukas Theussl closed MSITE-539.
-------------------------------
Resolution: Not A Bug
Assignee: Lukas Theussl
> 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
> Assignee: Lukas Theussl
> Priority: Minor
> Attachments: MSITE-539.zip
>
>
> [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
[jira] Commented: (MSITE-539) Reporting plugin version references
in new configuration example are wrong and misleading
Posted by "Stevo Slavic (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MSITE-539?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=262784#action_262784 ]
Stevo Slavic commented on MSITE-539:
------------------------------------
Can not reproduce this anymore.
> 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
> Attachments: MSITE-539.zip
>
>
> [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
[jira] Commented: (MSITE-539) Reporting plugin version references
in new configuration example are wrong and misleading
Posted by "Lukas Theussl (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MSITE-539?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=262782#action_262782 ]
Lukas Theussl commented on MSITE-539:
-------------------------------------
Attaching a simple test project, run 'mvn site' using maven-3.0.3 I get no warnings or complains about bad practice.
> 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
> Attachments: MSITE-539.zip
>
>
> [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
[jira] Commented: (MSITE-539) Reporting plugin version references
in new configuration example are wrong and misleading
Posted by "Olivier Lamy (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MSITE-539?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=262776#action_262776 ]
Olivier Lamy commented on MSITE-539:
------------------------------------
do you talked about [http://maven.apache.org/plugins/maven-site-plugin-3.0-beta-3/maven-3.html] section New Configuration ??
> 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