[
https://issues.apache.org/jira/browse/MPIR-322?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14572148#comment-14572148
]
Hudson commented on MPIR-322:
-----------------------------
SUCCESS: Integrated in maven-3.x #1081 (See
[https://builds.apache.org/job/maven-3.x/1081/])
upgraded MPIR plugin to benefit from MPIR-322 (hboutemy: rev
d8527aa9ce3938d20f49ff49dc3c32d744b22fa2)
* pom.xml
> Dependencies Files Details should reuse installed jars instead of
> target/classes
> --------------------------------------------------------------------------------
>
> Key: MPIR-322
> URL: https://issues.apache.org/jira/browse/MPIR-322
> Project: Maven Project Info Reports Plugin
> Issue Type: Improvement
> Components: dependencies
> Affects Versions: 2.7
> Reporter: Hervé Boutemy
> Assignee: Hervé Boutemy
> Fix For: 2.8
>
> 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.3.4#6332)
