[
https://issues.apache.org/jira/browse/MRM-1914?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Olivier Lamy (*$^¨%`£) closed MRM-1914.
---------------------------------------
Resolution: Fixed
Assignee: Olivier Lamy (*$^¨%`£)
Fix Version/s: 2.2.1
Fixed with
https://git-wip-us.apache.org/repos/asf?p=archiva.git;a=commit;h=95077dba05e56f29cc1bf4d69e37fa18cc253582
Thanks for report!
> Maven cannot find dependency
> ----------------------------
>
> Key: MRM-1914
> URL: https://issues.apache.org/jira/browse/MRM-1914
> Project: Archiva
> Issue Type: Bug
> Components: Build
> Affects Versions: 2.2.0
> Environment: Arch Linux, Maven 3.3.9
> Reporter: Jalal Almutawa
> Assignee: Olivier Lamy (*$^¨%`£)
> Fix For: 2.2.1
>
>
> In a fresh installation, the build fails for archiva-consumer-architype
> module, because Maven cannot find spring-context-support 4.1.4.RELEASE
> Searching for the part that declares this dependency, I found that the
> modules defined a local-repo, and a redback-components 2.4 is requiring
> spring 4.1.4.RELEASE whereas the rest of Archiva required 4.2.1.RELEASE
> Maven is looking for 4.1.4.RELEASE in my actual home repo instead of the
> locally defined one in the archiva-consumers-architype module, and this is
> breaking the build.
> Manually changing the dependency in the target folder to 4.2.1.RELEASE or
> manualling having the 4.1.4.RELEASE available in the default m2 repository
> home makes the build pass.
> I can help solving the issue if you tell me which way you prefer solving it.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
