[ http://jira.codehaus.org/browse/MPIR-143?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=247838#action_247838 ]
Lukas Theussl commented on MPIR-143: ------------------------------------ There is no "package" value for requiresDependencyResolution and test already resolves all dependency scopes, see http://maven.apache.org/developers/mojo-api-specification.html. Maybe you can attach a small test project? > Wrong scope/phase requirement documented on project-info-reports:dependencies > page > ---------------------------------------------------------------------------------- > > Key: MPIR-143 > URL: http://jira.codehaus.org/browse/MPIR-143 > Project: Maven 2.x Project Info Reports Plugin > Issue Type: Task > Affects Versions: 2.1 > Environment: maven 2.0.9 > Reporter: Stevo Slavic > Priority: Minor > > After discussion on maven user mailing list (see > http://markmail.org/search/?q=sslavic%20list%3Aorg.apache.maven.users#query:sslavic%20list%3Aorg.apache.maven.users+page:2+mid:kkzcdmruemiwpeei+state:results > ) conclusion was that wrong scope is documented on following page: > http://maven.apache.org/plugins/maven-project-info-reports-plugin/dependencies-mojo.html > in Attributes section where instead of "test" in "Requires dependency > resolution of artifacts in scope: test." it should stand "package". -- 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