[
http://jira.codehaus.org/browse/MNG-740?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_117236
]
Espen Wiborg commented on MNG-740:
----------------------------------
This appears to be fixed as of 2.0.8; at least I cannot reproduce it with
either of the attached test cases.
> dependencies resolution not work using pom on local source tree - special case
> ------------------------------------------------------------------------------
>
> Key: MNG-740
> URL: http://jira.codehaus.org/browse/MNG-740
> Project: Maven 2
> Issue Type: Bug
> Components: Artifacts and Repositories
> Affects Versions: 2.0-beta-1
> Environment: xp
> Reporter: Dan Tran
> Fix For: 2.1
>
> Attachments: c.log, jira.zip, mng-740-test-case.zip
>
>
> Folks, I would like to make sure i am able to build my artitfact with it
> parent poms are not either in local or remote repo.
> Attached is the dummy m2 structure to repoduce the problem.
> Here are detail
> somedir
> root
> pom.xml
> subprojects
> pom.xml
> A
> pom.xml
> BC-parent
> B
> pom.xml <--- depend on A
> C
> pom.xml <--- depends on B
> Here are the step the reproduce
> 1. Install root's pom ( m2 install )
> 2. Install A ( m2 install in subproejcts/A
> 3. install B ( m2 install in subprojects/BC-parent/B
> 4. install C ( m2 install in subprojects/BC-parent/C)
> C fails here. See attach logs
> however if I do a full install from subprojects or manually install
> subproejcts pom and BC-parent pom ( via m2 install -N) the problem goes away
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
