[
https://jira.codehaus.org/browse/MPIR-322?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Herve Boutemy updated MPIR-322:
-------------------------------
Attachment: MPIR-322.zip
here is an IT to easily reproduce the problem
now we need IMHO a hack to detect such a situation and use packaged content
> Dependencies Files Details should reuse installed jars instead of
> target/classes
> --------------------------------------------------------------------------------
>
> Key: MPIR-322
> URL: https://jira.codehaus.org/browse/MPIR-322
> Project: Maven Project Info Reports Plugin
> Issue Type: Improvement
> Components: dependencies
> Affects Versions: 2.7
> Reporter: Herve Boutemy
> Attachments: MPIR-322.zip
>
>
> in general, site is generated in a mvn run separate from initial build:
> {noformat}mvn install
> mvn site{noformat}
> what I expect is that the {{mvn site}} command reuse packaged artifacts from
> {{mvn install}} (or even {{mvn package}})
> but that's not what happens, and I can't tell it's a bug: AFAIK, there is no
> feature in Maven for the site phase to reuse
> the result is unfortunate in multi-module builds with dependencies inside the
> reactor: Dependencies Files Details display {{xxx/target/classes}} instead of
> {{xxx-version.jar}}
> see real world example:
> http://maven.apache.org/wagon-archives/wagon-2.8/wagon-providers/wagon-file/dependencies.html#Dependency_File_Details
> {{wagon-provider-api/target/classes}}
--
This message was sent by Atlassian JIRA
(v6.1.6#6162)
