[
https://jira.codehaus.org/browse/MPIR-238?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=359268#comment-359268
]
Christian Schulte commented on MPIR-238:
----------------------------------------
There are ways to solve this without having to change the core and without
having to work around anything. Just updating the reports expecting a packaged
archive to {{@execute phase="package"}} will already make the core resolve to
the {{jar}} instead of {{target/classes}} as expected. Meanwhile I've opened a
pull request https://github.com/apache/maven/pull/32 to add the option
mentioned above.
> Dependency File Details section of the dependencies report shows
> 'target/classes' for reactor artifacts.
> --------------------------------------------------------------------------------------------------------
>
> Key: MPIR-238
> URL: https://jira.codehaus.org/browse/MPIR-238
> Project: Maven Project Info Reports Plugin
> Issue Type: Bug
> Components: dependency-info
> Affects Versions: 2.4
> Reporter: Christian Schulte
> Priority: Minor
>
> Generating the dependencies report in a multi-module project leads to
> incorrect entries in the 'Dependency File Details' section of the
> dependencies report. For example, the [Maven Release Plugin Dependency File
> Details|http://maven.apache.org/plugins/maven-release-plugin/dependencies.html#Dependency_File_Details]
> report contains the following entry:
> ||Filename||Size||Entries||Classes||Packages||JDK Rev||Debug||
> |maven-release-manager/target/classes|-|0|0|0|-|release|
> Building the site of a single module ('mvn site' in that modules directory),
> the correct entries are shown.
--
This message was sent by Atlassian JIRA
(v6.1.6#6162)
