[
https://jira.codehaus.org/browse/MNG-5678?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=351455#comment-351455
]
Dan Tran commented on MNG-5678:
-------------------------------
related to https://jira.codehaus.org/browse/MNG-5663 ?
> second import within dependencyManagement is not taken from the correct
> repository
> ----------------------------------------------------------------------------------
>
> Key: MNG-5678
> URL: https://jira.codehaus.org/browse/MNG-5678
> Project: Maven
> Issue Type: Bug
> Components: Dependencies
> Affects Versions: 3.2.2
> Environment: Windows 7, jdk 7
> Reporter: Torsten Liermann
> Attachments: pom.xml
>
>
> Resolving of the second import within dependency management goes always on
> maven central (http://repo.maven.apache.org/maven2/) although the correct
> repository is specified.
> This bug is new in maven 3.2.2 The attacht sample works with maven 3.0.5 and
> also with maven 3.1.1
> A similar error occurs when an imported dependency management contains an
> import.
--
This message was sent by Atlassian JIRA
(v6.1.6#6162)
