[jira] [Commented] (NPANDAY-466) Dependencies fail to resolve in multi-module build up to phase verify (but not install)

["Lars Corneliussen (JIRA)" <ji...@apache.org>]

    [ https://issues.apache.org/jira/browse/NPANDAY-466?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13092646#comment-13092646 ] 

Lars Corneliussen commented on NPANDAY-466:
-------------------------------------------

Neat!!

> Dependencies fail to resolve in multi-module build up to phase verify (but not install)
> ---------------------------------------------------------------------------------------
>
>                 Key: NPANDAY-466
>                 URL: https://issues.apache.org/jira/browse/NPANDAY-466
>             Project: NPanday
>          Issue Type: Bug
>          Components: Maven Plugins
>    Affects Versions: 1.4-incubating
>         Environment: >mvn -v
> Apache Maven 2.2.1 (r801777; 2009-08-06 12:16:01-0700)
> Java version: 1.6.0_24
> Java home: C:\Progra~1\Java\jdk1.6.0_24\jre
> Default locale: en_US, platform encoding: Cp1252
> OS name: "windows 7" version: "6.1" arch: "amd64" Family: "windows"
>            Reporter: John R. Fallows
>             Fix For: 1.4.1-incubating
>
>
> During the release preparation of a multi-module build, a multi-module "verify" build occurs, and although dependencies are already resolved by the Maven dependency mechanisms, NPanday does not leverage that information and fails to locate the filesystem path for dependencies residing in a peer module's target directory.
> Note: the artifact has not been installed into the local .m2 repository because of running up to phase "verify" only, stopping before the "install" phase where such artifact copying occurs.

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira