Bug 865599
Summary: | maven local mode does not seem to resolve first from the m2 cache | ||
---|---|---|---|
Product: | [Fedora] Fedora | Reporter: | Roland Grunberg <rgrunber> |
Component: | maven | Assignee: | Stanislav Ochotnicky <sochotni> |
Status: | CLOSED CURRENTRELEASE | QA Contact: | Fedora Extras Quality Assurance <extras-qa> |
Severity: | high | Docs Contact: | |
Priority: | high | ||
Version: | rawhide | CC: | akurtako, java-sig-commits, mizdebsk, sochotni |
Target Milestone: | --- | ||
Target Release: | --- | ||
Hardware: | All | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2012-11-27 05:08:52 UTC | Type: | Bug |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: | |||
Bug Depends On: | |||
Bug Blocks: | 871788 |
Description
Roland Grunberg
2012-10-11 21:16:25 UTC
There is a workaround available. Assuming you gave artifact FOO:BAR:VER stored in .m2 cache, you can force maven to resolve it by using this custom depmap: <dependency> <maven> <groupId>FOO</groupId> <artifactId>BAR</artifactId> <version>VER</version> </maven> <jpp> <groupId>../../../..</groupId> <artifactId>$(PWD)/.m2/FOO/BAR/VER</artifactId> <version>VER</version> </jpp> </dependency> There's a fix for this in rawhide (http://pkgs.fedoraproject.org/cgit/maven.git/commit/?id=9b93db7e101a6f191a5a63f468de1000204e15e9), and I've confirmed I can build Tycho with it. Artifacts seem to be resolving first from the reactor cache. The workaround seemed pretty neat but didn't work in the case of resolving poms. This is mainly because when looking up the pom path, the groupId's '/' are replaced with '.' which breaks the path. I guess if anyone ever wanted to get this working locally, they could create symlinks to the root in %{_mavenpomdir} as 'foo-' and one in %{_datadir}/maven/repository as 'foo'. From there the gid could be set to 'foo' and the aid could be the path to the pom/jar with the extension omitted. maven-3.0.4-14.fc17 has been submitted as an update for Fedora 17. https://admin.fedoraproject.org/updates/maven-3.0.4-14.fc17 maven-3.0.4-14.fc18 has been submitted as an update for Fedora 18. https://admin.fedoraproject.org/updates/maven-3.0.4-14.fc18 Package maven-3.0.4-14.fc18: * should fix your issue, * was pushed to the Fedora 18 testing repository, * should be available at your local mirror within two days. Update it with: # su -c 'yum update --enablerepo=updates-testing maven-3.0.4-14.fc18' as soon as you are able to. Please go to the following url: https://admin.fedoraproject.org/updates/FEDORA-2012-16797/maven-3.0.4-14.fc18 then log in and leave karma (feedback). maven-3.0.4-21.fc18 has been submitted as an update for Fedora 18. https://admin.fedoraproject.org/updates/maven-3.0.4-21.fc18 maven-3.0.4-21.fc18 has been pushed to the Fedora 18 stable repository. If problems still persist, please make note of it in this bug report. |