[
https://jira.codehaus.org/browse/MPIR-238?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=359262#comment-359262
]
Christian Schulte commented on MPIR-238:
----------------------------------------
Thanks for bringing this up. The solution to MPIR-322 as it got committed is
incorrect in my opinion. Searching for a {{jar}} file in {{target}} is not what
should be done. Resolution is to take place solely in the core. Issues with the
solution to MPIR-322 are things like:
{{mvn package|install|deploy clean site}}
No {{jar}} in {{target}} will be found. The same problem exists for artifacts
not installed locally. For example, checking out some multi-module project
release version and just executing {{mvn site}} needs to make Maven 3 download
the deployed artifacts of the modules from the remote repositories. Exactly the
same way Maven 2 behaves. There are use cases where falling back to loose class
files isn't wanted/needed/expected. I am thinking about introducing a new
command line flag similar to the {{legacy-local-repository}}. Maybe
{{legacy-reactor-resolution}}. I could provide a patch doing this. However,
there would need to be some consensus on how to solve MPIR-322 and MPIR-238
properly.
> 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)
